PC shuts down or reboots spontaneously (MSI Eclipse SLI)

S

Smoke

New member
SERGEANT
Joined
Apr 5, 2009
Messages
34
Starting a new thread to avoid totally hijacking another thread talking about almost the same symptoms here.

My original post:

Smoke said:
I get this same situation.. except the event viewer doesnt state anything.

The system is not bluescreening.. it just hardware powers down and reboots.

I get the same message as the original poster as well, it is very annoying as it often happens in the middle of doing something.

I wonder if it could be thermal related to the high IOH temps on the board (often 80-85C, but not sure what happens to them in the middle of playing a game)? Is there any way to log the temperatures to a file so I can check what they were at the time of the crash?

I get this issue whether I change the default bios settings or not. Ive got a 920 on my eclipse board, my CPU temps are below 30C under load. System temp is about 27C.

What can I do?
Click to expand...

The following replies:

AaronYuri said:
That's way too high, even for 100% load.  Reinstall the heatsink.
Click to expand...

Smoke said:
It is? I found another thread on this forum where it was mentioned that intel and msi said the IOH runs hot and to expect temps up to 100C. How do I go about changing the manufacturers heatsink on a board? Ive never done that before and cant find any procedural help thru google...

Ive been able to replicate the issue by running ram up to high usage. When I get above 98% ram allocation, I spontaneously reboot. So It could be a ram issue as well. Of would that be something possible IOH related as well?
Click to expand...

NovJoe said:
smoke,

Can you list out your full system spec and PSU spec?
Click to expand...

System Spec:
Core i7 920 w/ TRUE 120
MSI eclipse SLI (bios 1.4)
6x 1gb corsair 1866mhz rated ram sticks (TR3X3G1866C9DF)
1500w thermaltake psu
galaxy gtx295 in the primary x16 pci-e slot
MSI eclipse soundcard in the 1st pci-e x1 slot
4x 1tb samsung 'UJ' hdd (raid 5)
O/S (= old winxp 32 bit until I get hold of a 64 bit os) running on 128gb PQI SSD
lg bluray burner

All the drives are sata2 and running on the ICHIOR ports.

For bios settings Ive got the optimised defaults with spread spectrum off and turbo boost on. Once its table then I will OC, but for now its not stable at the baseline yet.

Temp info:

IOH temps are as I said, around 80 at startup but rise to at least 87 under load, but not really much further that Ive seen.

CPU temps are very low with the dual-fan TRUE 120 heatsink. I havet seen it go above 35C with a reasonably heavy processing load. Usually sits about 0-2C above ambient at most when idle.

System temps get to about 40 under load, or around 27-35 under regular usage, but Im not quite sure what thats measuring the temp of on the board.

The issue is very frustrating but somewhat intermittent - I can go two days without a crash but then get several in a row. I wasnt previously paying attention to my usage at the time tho so I dont remember what I was doing when it crashed that I wasnt doing when it was fine. I have been able to replicate the crash/reboot/shutdown symptom by running multiple memory intensive apps and loading the ram up to just on the 2.99gb mark (the most winxp 32 bit will 'see') and it goes down. No blue screen though.. its a hardware issue not software I am pretty sure.

[edit] Updated the ram part number to be correct.
 
Sort by date Sort by votes
Yes, but will not isolate an issue specifically to RAM.  He can run Memtest86+ test#5 5 or 20x and test#7 the same number of times and should be reliable for testing the RAM.

Try the test that Aaron recommends, but I would also run Tests 5 and 7 of Memtest.
 
Upvote 0 Downvote
Smoke, here is what many of us have done to get that IOH temp down, hope it helps.

Reply #1; https://forum-en.msi.com/index.php?topic=125496.0
Reply #3; https://forum-en.msi.com/index.php?topic=125786.0
 
Upvote 0 Downvote
Ive been able to reproduce the shutdown by loading the ram beyond 2.8gb which is about 95% on winxp-32bit. This is just through running multiple of programs. Ive got a g15 and it has a monitor process showing me my ram and cpu loading (which show identical values to task manager).

the IOH temp doesnt seem to be related to the ram load and I cant figure out how to replicate the crashes with temp issues. IOH temps also appear uncorrelated with the reboots.

Running your Linpack test, if I run it on 1/4 or 1/2 load it runs fine, but as soon as I run max load (which says it attempts to use all ram) the pc reboots within a half second or so of starting the test. I guess while the program attempts to allocate the ram?

This doesnt mean I wont be taking steps to remedy the high IOH temps - thanks for the help with that - but I'll be solving this ram issue first (I dont think they are related given the new test results and the lack of temp correlation to periods of LOOOONG stability and then when crashes occur).

For the person who asked, I use both the MSI greenpower2 or overclockcenter temperature displays in windows or the hardware-monitor if I am in bios to watch the IOH temps. They also show system and cpu temps as well which is where I am getting those temps from too. I could use CPUID, but the temps it shows are identical to the ones the MSI utilities show me. I dont actually change anything using those two msi utilities tho. My DLED2 temp probe is monitoring the air temp in the case where I think there is a dead zone.

Ive also found (previously) that I cant use anything but the JDEC specification on the ram, XMP wont work at all even with the added voltage the ram asks for (rated for 1.65v at 9-9-9-24 @1866). I figure this is related too but maybe not so I only mention it in passing. I had crash symptoms before I ever touched the voltage or xmp settings and aside from the crashes and an inability to overclock the system appears to run fine so long as the ram load stays below a level approx 95-98% usage.

I dont know if the issue is with a ram stick or with the mobo. I figure the next step is to try memtest86 which runs outside the OS and should not have any 32-bit OS limitations on accessing the ram sticks.. if I get crashes then I'll pull ram sticks and try to isolate it to a ram stick which will hopefully help...

I am half expecting that memtest86 will reboot the machine as soon as it attempts to allocate ram above 2.8gb since Im guessing (And its just a guess mind you) that the issue may be a mobo problem with the ram slots for the 2nd triple-set. Im thinking the worst case problem I can reasonably expect and hoping for a nice surprise at a simple solution. I do not look forward to disassembling the entire machine to RMA the mobo... :(
 
Upvote 0 Downvote
If your now running XP SP3 32 bit, & waiting for a 64 bit OS, unless I missed it, are all the slots filled with the 1G sticks, or are you just using slots A0, B0, & C0?

Also, doesn't XP 32 bit have recognition issues with over 1T HDD's?

Added: Another quick question. Was the OS on the 128G PQI SSD a fresh windows XP install & was it at least an SP2?
 
Upvote 0 Downvote
Yes I am currently running winxp 32-bit waiting to see whether I waste money on vista or wait for windows 7. Got a recommendation?

yes I currently have all 6 ram slots filled with 1gb ram sticks each. I havent seen or heard of this causing hardware crashes though... because these are 100% definitely not windows blue-screen crashes (I got one of those early on with a bad driver and I've set the system to halt on a blue screen).

The largest drives I have on this box are 1TB each. winxp has no trouble recognising the drives or using them. I dont think Id get more usable space per drive under vista, but 970 usable GB per drive isnt bad for a temporary solution (Ive got 4 wired up but only use 1 of them and only as a storage drive. 99% of my drive usage is loading os or programs off from my 128gb ssd).

[edit] And Ive added my current system spec to my .sig for easier reference.
 
Upvote 0 Downvote
I added a question in Reply #9 about which XP & Service Pack was installed.

Give it a try with just the Black A0, B0, & C0 slots filled, & 'Enable' Auto Disable DRAM/PCI Freq. since only 3 slots will be used.

Added: Windows 7
 
Upvote 0 Downvote
Use one memory stick and try the IntelBurnTest again.  Monitor the IOH temperatures while doing so.

This could be a lack of juice getting to the uncore, the IOH overheating, a general IMC problem, or a memory problem.  Too many possibilities to call this one just yet.

Try running your memory at 1066 MHz, and auto timings, too.
 
Upvote 0 Downvote
HU16E said:
I added a question in Reply #9 about which XP & Service Pack was installed.
Click to expand...

XP professional, service pack 3 w/ all further updates applied. On installation, Its was a fresh install of XP on the ssd. Ive only got an XP sp1 install disk and I updated to sp3 thru windows update. SP1 didnt seem to have any trouble installing on the ssd though.
 
Upvote 0 Downvote
AaronYuri said:
chaos, try to keep on topic.

<hr>

But, to answer your question, I would guess CPUID's HWmonitor.
Click to expand...

That is on topic bro.? Dude said "I wonder if it could be thermal related to the high IOH temps on the board (often 80-85C, but not sure what happens to them in the middle of playing a game)? Is there any way to log the temperatures to a file so I can check what they were at the time of the crash?"

Ok, so I want to know how the hell he knows it is over heating? I have seen dudes post stuff like this and it turns out they were just putting their fingers on the cooling pip and it felt warm.?

SO that is why i was asking the "OP" what he was using to tell that it was in fact over heating.

 
Upvote 0 Downvote
OK dude this could be in LEFT field and if it is im sorry.

What video card are you running?? What temp is it running at?? My IOH dropped 15c when I used an software UTIL to turn my video card fan on MAX.? Card is right over the bridge and I think that was adding to my heat also some as well.? The fan is NOT blowing any cool air on the board cooling unit, but It is no longer radiating heat on top of the heat sink either.

Could be worth looking into?

ALSO to the poster saying that people with this problem solved it by removing the copper cooling unit and re app cooling compound... is there any negative to this?  If this doesn't resolve the Op's problem, then would it void his warranty and chances for an RMA??  If so, then smoke may want to think twice about that before his RMA goes poof.
 
Upvote 0 Downvote
Thanks Mr Chaos. My video card is specced in my sig now. Its a galaxy nvidia gtx295. No idea how hot it runs as I dont believe I have any programs that tell me that. Any suggestions?

Back to the memory though... I downloaded memtest86+ and burnt the cd last night. Ran it for almost 4 hours straight - about a dozen passes of all tests except the bit-fade test and not one single error, crash or problem. All 6gb was accessible and seemed fine. IOH temps cant have been any lower during that than when Ive caused the hardware to crash when loading the ram up in windows without heavy cpu or IO usage....

So now I really am kinda stumped. Is it a 32-bit windows issue? Id have thought that wouldnt cause the hardware to reboot it'd just blue screen....?
 
Upvote 0 Downvote
Last straw here, try installing XP or Vista on any other SATA drives except for the SSD and connect to the port which the SSD is connected to, and remove the SSD temporary. Test and see from here if the system runs fine without BSOD.
 
Upvote 0 Downvote
mrchaos101 said:
That is on topic bro.  Dude said "I wonder if it could be thermal related to the high IOH temps on the board (often 80-85C, but not sure what happens to them in the middle of playing a game)? Is there any way to log the temperatures to a file so I can check what they were at the time of the crash?"

Ok, so I want to know how the hell he knows it is over heating? I have seen dudes post stuff like this and it turns out they were just putting their fingers on the cooling pip and it felt warm. 

SO that is why i was asking the "OP" what he was using to tell that it was in fact over heating.
Click to expand...

My apologies, chaos, I thought you were just curious which program he was using... :biggthumbsup:

Smoke, RivaTuner and GPU-Z can tell you your card temperatures.  I recommend GPU-Z, as it gives more than just GPU and memory temperatures.
 
Upvote 0 Downvote
Thanks Aaron (hey, that's my name too!).

I'll grab gpu-z tonight when I get home and post what it gives me. I'll also start using cpu-z again as well.

I'll also be checking out trying to source a 64-bit OS (windows 7 beta or RC probably - but maybe linux?) to check my theory that the crash is related to the 32-bit ram limit and some unexpected hardware conflict.

reading the overclocking area of this forum, there are multiple comments that the overclockingcenter program may be unstable as well, so I'll probably uninstall that too (not that I was using it when the crashes occured though). Im finding this problem quite annoying since I want to try overclocking but Im not risking the system when its already showing problems. Im holding back though...

I can install xp on one of the currently unused 1tb sata drives like novjoe suggests and try to replicate the issue again when I have time.

Oh on the ssd Ive now set write cache off and set the swap file to 4096 permenantly. Ive seen a slight increase in responsiveness and fewer pauses from the ssd but it didnt stop the system rebooting when I ran the intelburntest program again - or when I load ram too high.
 
Upvote 0 Downvote
You must log in or register to reply.
Back
Top