Asus P5N32-SLI system shutdowns

jhayann1

Distinguished
Dec 13, 2007
3
0
18,510
I have an Asus P5N32-SLI MOBO that shuts down on its own, or gives me a BSOD before it shuts down. When I'm lucky enough to get a STOP error or BSOD, I had started writing them all down, except the errors given were never the same! It's as if the PC's just pulling it out its...!

Anyways, I'd like to get some stability on this thing instead of shying away from gaming because I'm afraid of it crashing. I'm new to the forum, but if there's a way to attach the CPUID hardware monitor log and/or Asus' Probe II log so you can have more details, pls. let me know. It's a lot of info to post in 1 msg. It seems that the CPU starts to get hot, then cools down. I haven't been doing anything on the PC except checking email (Thunderbird) and surfing the web (Firefox) because of all the shutdowns, so it's not like I'm doing anything extremely tasking, nor do I overclock. What gives??

PC specs are shown below. Thanks!

----------

Motherboard: Asus P5N32-SLI Deluxe, AMI BIOS 405

Processor: Intel Pentium 4 550, 3.40GHz, HT, 1MB Cache, 800FSB, LGA775 > Thermaltake's mini-typhoon 92mm fan w/ copper heatsink

Video: XFX GeForce 7600 GT, 256MB GDDR3, PCIe, Dual DVI, HDTV | Forceware 162.18 | DirectX 9.0c

Memory: OCZ EL Dual Channel 2GB (2x 1024MB) PC5400 DDR2 667MHz w/ copper heatspreaders

Power Supply: Ultra's X-Finity 600-Watt ATX, Dual 80mm Fan, SATA-Ready, SLI Ready

PC Case: Power Up 2531 Black ATX Mid-Tower Case with Clear Side Panel & LEDs > 1 large intake fan in front, 1 small exhaust fan on side panel, 1 large exhaust fan in rear

Win XP Pro SP2

--------------------

Update: I noticed when the PC crashes, seesm to be a pattern. Once the PC's been able to stay on for maybe half an hour without crashing, it seems to maintain stability. So it seems to be the most unstable within 30min of/after winXP Pro desktop is loaded. I let it sit idle for a few minutes yesterday, then my son played warhammer on it for over an hour without it crashing. Today, as soon as I logged into WinXP and got to the desktop, I got a BSOD and had to restart the PC. Now it's been on/running for maybe 2hrs and it hasn't crashed yet. *fingers crossed* Weird huh? I noticed that when I check email or open a new tab in the web browser, the CPU temp sometimes spikes to the high 60s, but then it drops down to 50 degrees C a few seconds later. The PC doesn't crash from the temp spike as far as I know. I don't have the temp monitor running when the PC first loads the desktop, which is when the crashes most frequently occurs.
 

timaahhh

Distinguished
Nov 5, 2007
279
0
18,790
Get the info from the stop error and post it. You can see the stop error in the event viewer in Admin tools in control pannel. Post the event number.

BTW I have that same board I hate it alot... I has been very unstable. Need to get a ATX to EPS converter just to run it.
 

jhayann1

Distinguished
Dec 13, 2007
3
0
18,510
In case you need this as well:

Win XP Pro SP2
McAfee Internet Security 2007


There's tons of errors in the log, but it looks like the following are the repetitious culprits:


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Description:
The Human Interface Device Access service terminated with the following error:
The specified module could not be found.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 100000d1, parameter1 00000014, parameter2 00000002, parameter3 00000000, parameter4 b9898b10.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 31 34 2c 20 000014,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 62 39 38 39 00, b989
0050: 38 62 31 30 8b10

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Description:
The server {C7E39D60-7A9F-42BF-ABB1-03DC0FA4F493} did not register with DCOM within the required timeout.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000008e, parameter1 c000001d, parameter2 bf80109e, parameter3 b5d4dcdc, parameter4 00000000.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 31 64 2c 20 00001d,
0038: 62 66 38 30 31 30 39 65 bf80109e
0040: 2c 20 62 35 64 34 64 63 , b5d4dc
0048: 64 63 2c 20 30 30 30 30 dc, 0000
0050: 30 30 30 30 0000

---------

I noticed the HID device was in there quite a bit. The only thing I have that may fall under HID would be my Logitech Media keyboard elite and maybe the logitech optical trackman wheel mouse, both of which are plugged into USB ports in the rear. I used to have one of them plugged in as a PS/2 but I had so many probs that way so I went to USB instead.
 

timaahhh

Distinguished
Nov 5, 2007
279
0
18,790
Sorry about the late reply. The first and Last error 10010 you should be able to ignore. The 1003 is the most interesting errors. It seems unfortunatly mean driver or hardware failures with a very large range.

Start by updating your video drivers, grease your processor with thermal paste to make sure its not overheating (if you don't know how ask), run memtest86 if you don't know how to get that ask. If none of those work and you have an extra graphics card lying about unistall your current one and switch to your extra card.