PC Reboots randomly. I have an event dump.

[CidCaldensfey]

Hey all. I was just playing World of Warcraft when this occured. I couldn't actually see the message itself, but I think I know whats going on. I had this problem before and I reformated my computer, but now I'm getting it again...And this was just a downward spiral.

I think it's something wrong my drivers, but I don't know which one. Here are three logs starting from most recent to the latest.


Most Recent-

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/16/2006
Time: 7:06:05 AM
User: N/A
Computer: CADIA
Description:
Error code 10000050, parameter1 f48133dc, parameter2 00000001, parameter3 bf80a678, parameter4 00000002.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 66 34 eters f4
0030: 38 31 33 33 64 63 2c 20 8133dc,
0038: 30 30 30 30 30 30 30 31 00000001
0040: 2c 20 62 66 38 30 61 36 , bf80a6
0048: 37 38 2c 20 30 30 30 30 78, 0000
0050: 30 30 30 32 0002


One from a few days ago-

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2006
Time: 4:21:50 AM
User: N/A
Computer: CADIA
Description:
Error code 1000008e, parameter1 c0000005, parameter2 00000000, parameter3 b51c6b80, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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 30 35 2c 20 000005,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 62 35 31 63 36 62 , b51c6b
0048: 38 30 2c 20 30 30 30 30 80, 0000
0050: 30 30 30 30 0000


One from some time ago-

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/10/2006
Time: 1:40:40 AM
User: N/A
Computer: CADIA
Description:
Error code 10000050, parameter1 f7089d9c, parameter2 00000001, parameter3 bf80a678, parameter4 00000002.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
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 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 66 37 eters f7
0030: 30 38 39 64 39 63 2c 20 089d9c,
0038: 30 30 30 30 30 30 30 31 00000001
0040: 2c 20 62 66 38 30 61 36 , bf80a6
0048: 37 38 2c 20 30 30 30 30 78, 0000
0050: 30 30 30 32 0002

Once again, any help is greatly appreciated. So far to make sure my hardware is okay, I stress tested my computer with Memtest86 for about eight hours overnight and it reported no errors nor did it crash. Just to ensure I was running the program right, I ran it on a different computer which I know had hardware problems, and not even two minutes into the test it crashed.

So I doubt it is my RAM causing the problems. I should also mention that World of Warcraft, as of late, has been extremely buggy. Many people have reported, including myself, 123 Errors. I won't post any of those here for now, but if you are curious to see what those say, if it helps to track the problem down, I can post those as well.

Thanks.

My system, btw, is the following:

Windows XP - Service Pack 2
Asus A7N8XE Deluxe
AMD3200XP
2048MB
BFG Tech 6800GT OC
Sound Blaster Audigy 2

 

[TimeParadoX]

Hmm... What is the Max Watt of your PSU?

Open the side of your case and on the sticker it should have abunch of numbers like 12v and all that stuff then at the bottom it says Max Watt then has a number with a w at the end

Also buy a compressed air can from Bestbuy or any other computer store and clean out all the slots including RAM and make sure there is no build up from dust, Try switch the RAM sticks around

Hope I helped

( After trying all this stuff tell me if it helped any )

 

[CidCaldensfey]

Bump. I still need help with this problem.

 

[CidCaldensfey]

Bump again :/

 

[cpc2004]

Refer this document. Zip 5 to 6 minidumps and attach the zip file here.

 

[CidCaldensfey]

I just recently reformatted my computer. I don't have more than three crash logs.

I've already tried all of that prior to actually reformatting my computer. I had to reformat because of these problems. Originally I changed my virtual memory to 1024 and kept it after I upgraded my ram (which didn't fix the problem).

Also, I already ran Memtest56+ on a bootable CD for 24 hours per memory stick and each one passed with flying colors. I ran all memory sticks together (2048 total) for six hours while I was sleeping and it recorded no errors/didn't crash at all.

The only thing left to check is overheating, but I already replaced my heatsink with a silent cooler thermaltake heatsink. My CPU stays below 50C and my graphics card stays below 65C.

I've done almost everything I can do to make my computer stable but I'm getting really frustraited with the fact that even after I've done this, I'm still getting errors and they only occured after I updated World of Warcraft to version 2.0. I don't know why, but this is just how it is and I'm getting very mad.

Because I've done most of the possible, or most of the tier one troubleshooting, thats why I came here and posted on this forum for help because I don't know what else I could do. I've already checked my minidumps with windows debugging tools.

The latest crash, the first I posted, returned with: 10000050, {f48133dc, 1, bf80a678, 2}

Also, it says 'Could not read faulting driver name'
Problem caused by: win32k.sys ( win32k!DC::bSetDefaultRegion+ef )

Thats why I keep on trying to tell people I really believe my computer has something wrong as far as drivers go, but I don't know whats causing these crashes or which driver. One of the original reasons which popped up before I reformatted was pool_corruption, which was also caused by faulty drivers.

I really need help with this. I'm not dumb and I have tried everything that would normally be caused by a hardware failure. But I know for a fact that this is not caused by hardware. I've already spent $500 purchasing new components and am beginning to get really, really aggitated.

Actually nevermind. I quit. I'm just going to get another job and buy a new computer entirely.

 

[cpc2004]

Hi,

If you attach the minidumps here, I can help you.

 

[CidCaldensfey]

I'm sorry theres not more but if you want I could try using the driver verifier to try to get my computer to crash more to produce more minidumps. This really means a lot to me and I really appreciate you taking the time to check them over. I tried fixing this myself but I'm totally clueless as to why this is continueing.

If it helps, World of Warcraft seems to crash a lot due to some error called a #132 error. Each time it crashes, it produces it's own log in a notepad and you might be able to find whats causing these crashes through that. I'll attach that too so that you have more content to go over. The #132 Error is caused by quite a few things, such as Asus boards with old drivers, or even bad RAM. So it's really worth taking time to look at if you need more information.

Once again, I really thank you for taking your time to help me. This really means a lot to me.

My computer just crashed again so I attached the latest dump.

I'm going to run driver verifier later tonight to see if maybe I can get a more accurate dump.

 

[cpc2004]

Hi,

Your version of nVidia Display Card Driver is unstable and causes blue screen. Upgrade or downlevel the video card driver may resolve blue screen problem.

Mini121206-01.dmp BugCheck 1000008E, {c0000005, 0, b51c6b80, 0}
Probably caused by : nv4_disp.dll ( nv4_disp+6668 ) <-- nVidia Display Card Driver

 

[CidCaldensfey]

Okay thanks. I'll install the latest drivers and see if that changes anything. Was that error apparent in all the crash logs or just that one? I'm wondering this because I'm already using older drivers as a precaution after either the first or second crash.

Also, I had one of my memory sticks in the wrong slot. I just recently purchased a 1GB stick to go with my two 512 sticks but the 1GB stick says 'B1' on the label and I didn't actually read it. Would having the stick in the wrong slot cause read/write memory errors?

Note: I was receiving BSODs of this nature before I even purchased the memory stick. Also, my ATI 9800 Pro was an AGP slot card and it got busted somehow (just instantly caused artifacts and ever since that it was damaged for good). Could it be possible that memory read/write errors are also being caused because of a damaged AGP slot?

Thanks.

UPDATE! ! !

Okay, I think I found something. After I switched slots for the 1GB stick, I moved it to B1 btw, I ran Memtest86+. On test 5, it says it found 36 errors so I guess the problem is RAM after all.

I removed the stick and now I'm testing the two originals (the two 512s) to see if I can just narrow this problem further. Maybe it's just the RAM slot and not the RAM itself? We'll see. I'm running the sticks now in A1 and A2. The thing is though, I tested B1 by itself and it passed the test. I'll poke around more and run more tests to find out.

The A1 and A2 test ran just fine and I just did a A1 and B1 test...that passed as well. It does make sense though that it would have problems because it was 512 in A1 with a 1GB stick in B1. They're supposed to be the same, right?

I don't get it though. I was getting these BSOD's before I bought the 1GB stick. The reasons why it kept occuring though was because of something called pool_corruption. I googled it and it turned out to be caused by driver problems...

Ah well. Would running the 1GB stick in any other slot cause problems? I really do like to have 2GBs. So far I've been running it in A2 while the two 512s ran in A1 and B1. When I ran Memtest86+ with that setup, it passed with no problems.

 

[Adriode]

Ram timings ok?

Hey,

as an avid WoW player I must suggest making sure your RAM timings and voltage settings are 100% correct. WoW seems to be the most sensitive application to ram ever, and I was experiencing lots of crashes (error #132 AND lockups as you described) until I upped my ram voltage from 2.6v to 2.7. That's it - that fixed the problem.

Might be worth a shot