Ok, My Turn to Ask for Help, Take a Look Please

I am sporadically getting Windows Error Reporting popping up on boot.

"System has Recovered from a Serious Error"


Looking in Event Viewer, I found these in conjunction (with the latest):



Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 1/26/2004
Time: 10:38:48 AM
User: N/A
Computer: ADRYNALYNE
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x86427532 (0x000001db, 0x00000002, 0x00000003, 0x0000000b). A dump was saved in: C:\WINDOWS\Minidump\Mini012604-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.







Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 1/26/2004
Time: 10:39:17 AM
User: N/A
Computer: ADRYNALYNE
Description:
Error code 86427532, parameter1 000001db, parameter2 00000002, parameter3 00000003, parameter4 0000000b.

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 38 36 34 32 37 35 33 8642753
0020: 32 20 20 50 61 72 61 6d 2 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 31 64 62 2c 20 0001db,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 33 2c 20 30 30 30 30 03, 0000
0050: 30 30 30 62 000b



I only get this when I reboot.

This is a clean install.

I've not seen any stop errors, but only because my dumb arse forgot to turn off automatically restart after I clean installed this.


Can someone give me some ideas on what the problem is?


I'll include what info I can (that is relevant).













Default Running Processes (mostly)




Image Name PID Session Name Session# Mem Usage
========================= ====== ================ ======== ============
System Idle Process 0 Console 0 20 K
System 4 Console 0 216 K
smss.exe 596 Console 0 472 K
csrss.exe 644 Console 0 3,432 K
winlogon.exe 668 Console 0 1,496 K
services.exe 716 Console 0 3,156 K
lsass.exe 752 Console 0 5,740 K
ati2evxx.exe 900 Console 0 1,940 K
svchost.exe 928 Console 0 2,820 K
svchost.exe 1028 Console 0 18,448 K
svchost.exe 1196 Console 0 1,944 K
svchost.exe 1256 Console 0 4,480 K
spoolsv.exe 1396 Console 0 3,884 K
CachemanXP.exe 1536 Console 0 1,212 K
Pavsrv51.exe 1612 Console 0 4,128 K
svchost.exe 1660 Console 0 2,912 K
Avengine.exe 1724 Console 0 12,076 K
ati2evxx.exe 404 Console 0 1,868 K
explorer.exe 488 Console 0 19,012 K
Apvxdwin.exe 528 Console 0 2,136 K
sstray.exe 348 Console 0 2,356 K
atiptaxx.exe 616 Console 0 3,664 K
msnmsgr.exe 648 Console 0 13,656 K
Pavproxy.exe 956 Console 0 2,844 K
notepad.exe 3748 Console 0 324 K
cmd.exe 3056 Console 0 1,412 K
wmiprvse.exe 3152 Console 0 4,156 K
tasklist.exe 3136 Console 0 2,932 K


Dxdiag report is attached:

 

Sigverif results, all are HP network print drivers, monitor driver, and theme dll:

 

Thid party services:

 

Startup items:

 

Aida32 Quick Report (the Full one is too big):

 

I think I've made this into a manageable post. Sorry for those that got the post from hell (the first one). I wasn't thinking clearly

 

when I see dumps that have no particular item to refer to, I immediately think memory..
did this happen before or after cacheman?

 

Thanks for the replies so far. I suspected ram too.

I ran Docmemory 2.1b (b for beta )

It ran 5 passes on the burn in test over several hours. It locked up when I stopped it though (I'm guessing a glitch)

No failures. All pass.

Cacheman and Aida32 are the only new programs I have, bseides the fact this is a new motherboard and as such has new chipset drivers. I've since uninstalled cacheman and aida32, to see what happens.

I also installed the Nvidia IDE driver, hoping it wouldn't bite me back (its the only way my ATA133 drive would show up as such in XP, it was only going to UDMA 5).

All updates are performed, all latest drivers. One bios revision behind, which addresses memory chip compatibility (hmmmm), but only for certain brands, incidently, not mine.

 

Halo:

Yup, clean install

 

I would try the bios update my friend.. you never know if they didn't know about those modules or not.
A good place to start anyway.

You could also try one stick at a time too..

 

Ok, I'll start there Anyone know where I can get the BIOS updater than runs in Windows (Asus)? I don't see it on their site, for my motherboard. I bought this board used, and don't have it.

Thanks for the help friends

 

yeah the only reference i can find with that error is faulty or incompatible hardware
you didnt try Memtest then ive always found that most reliable

but these asus boards can be picky with ram it may work perfectly fine in another machine

anyway hope you get it sorted

 

I'll try memtest today when I leave for work, then report back at lunch.

 

http://www.asus.com/support/download/item.aspx?ModelName=Tools

I have just sacrificed 2 kittens to the Gods.. with pleasure

 

LOL, kill them kitties!

One more thing to add.

My games do NOT crash so far. I've only tried two though, Dark Age of Camelot and Unreal2.

 

Hmmph! Well, some of us got so tired out from reading THAT version that we had to take a nap afterward, and now everybody else has done the consulting.

Hope this all pans out and the problem disappears, friend.

(I ALMOST answered right after you put up "the post from hell" -- and before you fixed it -- that I was going after you, Kodo, and the poster, if anybody QUOTED that post in a REPLY! KITTENS? Fuggeddit! Major crimes deserve major victims! My guess is that for length, that original post might have made Guiness.)

 

I would have cried if someone had quoted that.

It took me 10 seconds to post nothing but text, that was the first indicator that maybe it was too long

 

I'm guessing here, but since its pops up on boot, it could be a shutdown issue.
Is there a way to confirm all programs closed properly?

Or maybe its hardware - I've heard of problems that pop up after the computer cooled. Try making sure memory and cards are seated properly

 

I would think if something wasn't seated correctly like ram, I wouldnt be able to play games?

I don't doubt its happening at shutdown.

Im just not sure whats doing it.

 

Edit: I am certain i seated everything snugly. I took extra time with rebuilding this computer and made sure.

 

In all honesty I haven't tried that. I certainly will though. The reasonw hy I didnt really go through that is when i've seen that problem, its usually every boot it comes up.

Know what I fear?

That I damaged something. I was playing with my CPU (found out is unlocked, woohoo). I booted at 200mhz x11 to see if it would.

It did. I tried booting at 200mhz x 10 too, just to see. It did.

I then rebooted and set the default clock back. Its an Athlon XP 2500+

Then I tried agressive ram timings for a boot. I installed Prime95. I ran it for about 5 minutes then decided it was too much effort and cancelled it.

On reboot, I saw this error for the first time. Well, the Error Reporting for it anyway.


I've set the timing back to optimal.


But I tested ram yesterday with docmemory. Ran burn in test for several hours. It passed. Im going to try memtest tonight.

I've played games since.

Maybe I am just paranoid, because that was the first time I've dabbled with overclocking.

Today was the second time I've seen it. So its so far happened twice over 3 days.

BTW, I leave my PC running 24/7. It hasnt locked up or anything. Although Panda failed to intialize one boot. Rebooting fixed that though.

 

True, true. You guys are giving some great suggestions. Keep em coming.

I still haven't updated bios and such, and a certain somebody interrupted my plans to run memtest while at work

*Points at computer screen*


You know who you are!

 

Ok, here is what I've done so far. I'll bump this thread if my problem occurs. Thanks everyone.


Ran memtest86.

No errors, 12 passes. Oddly enough in the information, it said my L2 cache was unknown??

Cleared system restore points on all drives.

Removed pagefile.sys.

Updated to 1007 bios, which in turn reinstalled the Nvidia memory controller.

Removed cacheman XP.

Removed Aida32.