New Computer, Random Restarts

JustinSane

2[H]4U
Joined
Jun 29, 2005
Messages
2,425
My friend put together a new machine and it keeps restarting on him at random times. Mostly it restarts during Modern Warfare 2, but he had it restart when opened IE once. Any ideas on what could be causing it? Here are the system specs:

AMD Phenom II X4 940 Black Edition Deneb 3.0GHz
Dynatron A5JG 77mm cpu cooler
GIGABYTE GA-MA785G-UD3H
XFX 4870
2x2 G.Skill DDR2 1066
OCZ 700 GamerXStream
Windows XP 32

No overclock on the cpu or gpu yet.
 
1. Go to Start -> Control Panel -> System
2. Go to Advanced
3. Under the Startup and Recovery section, click Settings...
4. Under System Failure un-check "Automatically restart"

Post BSOD error code
 
Heat issues? Test RAM and HDD maybe, he may not be getting a BSOD on restart, just a forced shutdown.
 
This is the BSOD code:
BCCode=1000008e&BCP1=C0000005&BCP2=805B5D03&BCP3=A108DC24&BCP4=00000000
 
He got this a few mins ago:

BCCode=1000000a&BCP1=F000E2C6&BCP2=0000001C&BCP3=00000000&BCP4=804F9D83

Any ideas?
 
I googled around with these error codes and it is looking like RAM issues. He's gonna run memtest86 and see if his sticks are alright. Thanks for the help MrsOldMX and ProfessorKaos64.
 
check the voltage of the memory, what the BIOS has the memory at and what the memory specs say.

I have 2 friends that had random crashing during game play and both need to set the memory voltage.

example

G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066

was set to 1.8 volts in BIOS, specs called for 2.0-2.1

once changed in BIOS to 2.1 volts no more crashing
 
You may need to manually set the RAM settings, instead of using AUTO. An easy test for this would be to run memtest for around 8 passes or so.

http://www.aumha.org/a/stop.php
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
 
Back
Top