• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New build randomly reboots

I

Incramus

Limp Gawd
Joined
Oct 28, 2007
Messages
325
I just built a new system for a friend and he says that its randomly rebooted on him 3 times in the last week once was while playing LOL and another time was when watching a youtube video.

Here are the specs:

Thermaltake case
AMD FX 4100 Black Edition 3.6GHz
GIGABYTE Mother Board (GA-78LMT)
8 gigs of Ram Kingston HyperX blu
SAPPHIRE Radeon HD 6850 Vid Card
OCZ ModXStream Pro 600W Modular Power Supply
Sony CD/DVD burner
250 gig 7200 rpm Hard Drive (used drive I had sitting around history not known)
Windows 7

I was thinking it was maybe bad ram so I ran memtest in windows & from boot disc and both times no errors were found... The video card and PSU were both bought used on CL but and the guy I bought them from said he they were 4 months old and he was upgrading.

I have my system that I can pull "test" parts out of but I'm not sure where to look next?
 
what would be a good test for those? I've ran 3dmark a few times trying to get the system to crash with no luck.
 
[Testing the Hard Drive]
Download the CD image of Hitachi Drive Fitness Test, burn the ISO file to a CD, and then boot from it, just like you would do with the XP/Vista install CD. Test the hard drive and see if any problems are found. DFT will run on most manufacturers' hard drives. Alternatively, you can use Seagate's SeaTools for DOS to test a Seagate or Maxtor drive. For a Western Digital drive, you could use Data Lifeguard Tools for DOS to test a Western Digital drive. For a Samsung drive, you could use Samsung's ES-Tool.

[Testing the CPU]
Use Prime 95, OCCT, Orthos or Intel Burn Tool to stress test the CPU.

[Testing the GPU]
Use Furmark, OCCT, or ATI Tool to stress test the GPU. If you see any artifacts or any other graphical glitches, the GPU could be overheating, too overclocked, or faulty.
 
So far we have:

*memtest in windows & from boot disc both times no errors found
*Hitachi Drive Fitness Test ran in quick & and advanced mode, no errors found on either
*Furmark for 15 mins with no problems found

Does Furmark also stress the PSU??

Guess the only thing left to run is prime...
 
Incramus said:
*Furmark for 15 mins with no problems found.
Click to expand...
Test a little longer than that. Like a few hours.
Incramus said:
Does Furmark also stress the PSU??
Click to expand...
Not directly. It loads the video card which then makes that card draw more power from the PSU. But no software in the world can properly test a PSU. Even PSU voltages can't be trusted from software.

Incramus said:
Guess the only thing left to run is prime...
Click to expand...
Check the event viewer and see if anything shows up there.
 
Danny Bui said:
Not directly. It loads the video card which then makes that card draw more power from the PSU. But no software in the world can properly test a PSU. Even PSU voltages can't be trusted from software.
Click to expand...


Cool. That's what I was thinking, just wanted to make sure it was adding some stress to the PSU.

Anyways I didn't get a chance to finish testing because he was in a hurry to get it back to game last night... but before I started all the testing I did swapped the ram sticks around so maybe that did something? he did mention that two of the 3 times it crashed on him he was watching youtube, doesn't seem that youtube should add much stress to anything?

If it reboots on him again, I'll have him run prime...
 
Is it generating a memory dump when he crashes? Could be software related, even if it is a new computer. Either way, if there's crash logs being made, use a program like whocrashed to analyze the memory dumps, sometimes they contain driver names or other clues that can help pinpoint what the problem is.
 
So My friend said that the system I build for him is still crashing at random... I had him run whocrashed (Thanks for the info Pylor ) and this is what it came back with:

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 3/18/2012 5:03:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031812-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007EC28F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 3/15/2012 8:19:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031512-15631-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80079A88F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 3/8/2012 6:55:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-14632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA0 (0xB, 0x17FE2A000, 0x3, 0x24297000)
Error: INTERNAL_POWER_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 3/8/2012 6:55:11 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalHandleMcheck+0x256)
Bugcheck code: 0xA0 (0xB, 0x17FE2A000, 0x3, 0x24297000)
Error: INTERNAL_POWER_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 3/8/2012 11:31:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-13868-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007A0E8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 3/2/2012 8:23:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-16629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800798D8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 3/1/2012 9:17:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030112-19000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80079E18F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

10 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
This link might help:
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

[Testing the RAM]
Download Memtest86+ v4.20 or whatever the latest version is, unzip it, burn the ISO file to a CD, and then boot from it, just like you would do with the XP/Vista install CD. Let Memtest+ run for at least 15 passes with ZERO errors on each stick of RAM separately as well as test the RAM all together. Go for a full 24 hours if you want to be completely sure that the RAM is not a problem. If you start seeing errors, than your RAM is defective or you have incorrect settings for the RAM.
 
I've ran Memtest86 from a boot disc, but I didn't test the sticks separate or for 24hrs... maybe I'll have him do that.
 
He ran windows update and found that there were 83 updates found and the last update was never. So fingers crossed that was the problem.
 
Last time I had error codes like that it turned out to either be a bad motherboard or not enough CPU voltage (I just bought a new one because the nforce one was crap). How are things in his bios set, does he have them set to manual or automatic? What do the temperatures look like?

Is there any commonality to when these are occurring? For example, does he blue screen a lot when in games or does it sometimes happen when he's just sitting on his desktop typing a word document. Those internal power ones, did that happen when he was coming back from hibernate?

Prime 95 would be a good one to run, just keep an eye on your temps when you do it. I'd also check video card temperatures if it's happening mostly when he's gaming or watching something else that uses the GPU, though my money is on either a bad bios setting or a motherboard issue. I highly doubt windows updates will fix a blue screen problem, but it's always worth a shot. Also might try upgrading his drivers directly from the chip manufacturers.
 
Pylor said:
Last time I had error codes like that it turned out to either be a bad motherboard or not enough CPU voltage (I just bought a new one because the nforce one was crap). How are things in his bios set, does he have them set to manual or automatic? What do the temperatures look like?

Is there any commonality to when these are occurring? For example, does he blue screen a lot when in games or does it sometimes happen when he's just sitting on his desktop typing a word document. Those internal power ones, did that happen when he was coming back from hibernate?

Prime 95 would be a good one to run, just keep an eye on your temps when you do it. I'd also check video card temperatures if it's happening mostly when he's gaming or watching something else that uses the GPU, though my money is on either a bad bios setting or a motherboard issue. I highly doubt windows updates will fix a blue screen problem, but it's always worth a shot. Also might try upgrading his drivers directly from the chip manufacturers.
Click to expand...

Well he's never got a blue screen, the system just loses sound & video then reboots. its happen a number of times just when watching youtube videos, once while gaming and even crashed on the desktop with nothing running.

Bios are set to automatic, and the temps on everything look good even while gaming. Ran Prime 95 with no problems.
 
1. Identify exact Motherboard BIOS version, either from BIOS boot screen, or from CPUZ screen
2. Identify exact GA-78LMT which model and revision.
3. Use HDAT2 or MHDD to low-level scan the hard disk. (Identify exact brand and model of 250GByte hard disk. Use vendor specific disk diagnostic tool if you prefer.)
3.1 Microsoft suggests disk could be problem as well.
4. Update system drivers and Windows update patches (I understand you mentioned 83 updates)
5. After Windows update, try Microsoft Security Essential and latest update.
 
Incramus said:
Well he's never got a blue screen, the system just loses sound & video then reboots. its happen a number of times just when watching youtube videos, once while gaming and even crashed on the desktop with nothing running.

Bios are set to automatic, and the temps on everything look good even while gaming. Ran Prime 95 with no problems.
Click to expand...

He's blue screening, he just doesn't see it because he has it set in the system->advanced options to reboot instantly.

Sounds like it's happening all the time randomly. I'd suggest updating everything, bios, drivers, to the newest that you can find. How long did prime95 run for?

Can always try taking bios settings to manual, that can help a lot sometimes.
 
Pylor said:
He's blue screening, he just doesn't see it because he has it set in the system->advanced options to reboot instantly.

Sounds like it's happening all the time randomly. I'd suggest updating everything, bios, drivers, to the newest that you can find. How long did prime95 run for?

Can always try taking bios settings to manual, that can help a lot sometimes.
Click to expand...

Oh, Gotcha.


Well he did run prime overnight for about 8 hours and it came up with no errors. and Hasn't rebooted on him since the 83 updates but that doesn't mean we are in the clear yet.
 
Well it did reboot after the 83 updates...

Next step I flashed the BIOS on the mobo on 3-23-12 and it hasn't crashed yet... and its been about two weeks without a crash (but since I'm posting this it'll prolly crash..lol)

Funny thing is that originally after the system was built I updated the BIOS using the update utility that connects to the sever and downloads/updates the BIOS BUT this time around I went to the site and downloaded the updated bios for the version of the mobo then updated using that file.

Could the update utility have updated the wrong version from the server?
 
You never specifically mentioned what the motherboard is. GA-78LMT is an incomplete part number.
Gigabyte lists GA-78LMT-S2PT and GA-78LMT-S2P on their website.
The S2P is the one commonly sold at Micro Center so my guess is that you got that one.
There are many revisions of the S2P and all the latest revisions only support up to a 95W cpu.
If you overclock the FX-4100, which you didn't mention one way or the other, you are pushing the 95W boards a bit and it may reboot or bluescreen or just plain die on you.

Of course this could have all been an old bios issue which has been solved by now too. hard to tell without all the info
 
Well yesterday was exactly 3 weeks since I updated the bios and I asked my friend if he's had any system crashes since and he said "no, I think we're in the clear." sure enough he sends me a text later saying it crashed.... I feel like had I not asked him, it wouldn't have crashed....LOL



pgaster said:
You never specifically mentioned what the motherboard is. GA-78LMT is an incomplete part number.
Gigabyte lists GA-78LMT-S2PT and GA-78LMT-S2P on their website.
The S2P is the one commonly sold at Micro Center so my guess is that you got that one.
There are many revisions of the S2P and all the latest revisions only support up to a 95W cpu.
If you overclock the FX-4100, which you didn't mention one way or the other, you are pushing the 95W boards a bit and it may reboot or bluescreen or just plain die on you.

Of course this could have all been an old bios issue which has been solved by now too. hard to tell without all the info
Click to expand...

Yes it is the GA-78LMT-S2P MB and the chip is not overclocked, I'd rather get it without crashes before doing any overclocking.


Think its worth reformatting and starting with a fresh install of programs and such?? My other option is to take the mobo/chip back as defective but I'm not sure how MC is on their returns of mobo/chips.
 
**********************UPDATE****************************

I took the Mobo/chip back to MC and my friend had some extra cash and wanted to upgrade to the FX-8120 & ASUS M5A97 Mobo http://www.microcenter.com/single_product_results.phtml?product_id=0382961 (wasn't our first choice, just what they had in stock)

Its only been a few days but no reboots. But he now feels like he paid for a downgrade because his FF benchmark score has gone down from the FX-4100, I told him the extra cores weren't going to do anything for what he was doing but he wanted to be able to say "Yeah I have an 8 core" LOL so now we are going to get a 212 cooler and OC a bit. I just hope the rebooting is issue is now gone...
 
So it crashed again.... same type of crash but this time with the new mobo/chip.

I'm starting to lean towards the PSU
 
It is an OCZ PSU. Though did you replace the RAM as well?
 
Yeah it was even a used PSU, I take it OCZ's are bad?? Yes the RAM was replaced and I even added 8 more gigs.

I'm thinking about taking his OCZ and swapping it out for my SeaSonic and letting him use it was a test. (my rig is not being used much right now)
 
Well I'd rather have my system crashing than the customers so we'll see how the swap goes. I hope his doesn't crash and mine DOES after the swap that way I can just order a PSU and be done with this whole ordeal.
 
Today I took the PSU to a local computer shop to have it tested and when the power source to the PSU was cut off the 5 & 12 rail were still holding for 3-5 seconds. The guy at the shop thought that was odd, he said usually everything dies out at the same time but it could just be the OCZ band ?
 
Still crashing... but my friend says he can now pin-point/re-create the crashes. It seems to be linked to him using Google chrome while playing LOL.
 
You must log in or register to reply here.
Back
Top