Constant BSODs in XP... 0xd1 most often. 3

[brianlisk]

I get at least 3 BSOD's daily. Most of them are 0xd1, but I also have gotten 0x1000008e, 0x0a, 0x7f, 0x50, 0xd9, 0x76, and 0x24. I tried to troubleshoot it by checking out this page,

http://aumha.org/win5/kbestop.htm,

but nothing I found in the links helps. They all pretty much in one way or another reference memory or paging file. I have cleared the paging file and reinitiated it, like they told me to, but that didn't help. I've also swapped the memory for known good memory, and ran hardware diagnostics (everything comes up fine). When I swap the memory, I continue to get the blue screens. I had this problem from December to May, but I found that I had a bad memory module. I swapped that, and it was working fine until about 2 weeks ago. NOTHING has been added or removed. My antivirus is up to date, and there is no viruses on my PC. I run Spybot Search and Destroy weekly, and that is clean, too. I defrag every other week. I try to take good care of my PC, but NOTHING seems to be helping.

Since everything was referencing memory, and my memory is good (as far as I can tell) could it be my motherboard? Perhaps one of the memory bays is disfunctioning.

PLEASE... if you have ANY suggestions, I need to have my PC working. I'm surprised it hasn't blue screened in the time it took me to type this.

Thanks,

Brian Lisk

 

[bcastner]

Start, Run, eventvwr.msc

What is red flagged in the System log? Post a few examples here in detail.

 

[brianlisk]

By Red Flags, I assume you mean Errors, these are some examples of what is listed:

Source: DCOM
The server {520CCA63-51A5-11D3-9144-00104BA11C5E} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

----------------------
Source: MRxSmb
The master browser has received a server announcement from the computer LISK3 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{79D40C40-4BC6-44F2-A0A. The master browser is stopping or an election is being forced.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

----------------------
Source: NTFS
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

----------------------
For that last one, that only happened for 2 days. I just ran chkdsk, and this is the result:

The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
Windows has checked the file system and found no problems.

61440560 KB total disk space.
25411848 KB in 54673 files.
20124 KB in 4588 indexes.
0 KB in bad sectors.
127160 KB in use by the system.
65536 KB occupied by the log file.
35881428 KB available on disk.

4096 bytes in each allocation unit.
15360140 total allocation units on disk.
8970357 allocation units available on disk.


I got this many errors:
3 Dhcp (not listed)
7 DCOM
1 MRxSmb
2 Service Control Manager (not listed)
12 NTFS

 

[bcastner]

Boot from the XP CD and select the first R(epair) option you face.

This will bring you into the Recovery Console.

chkdsk /r

This may take a while depending on the drive.

Quick summary of your stop/error codes.

The Master Browser issue is more informative than anything else. If you are on a mix with Win9x clients on the LAN, you might consider disable your Computer Browser service.

DCOM is a little troublesome, but it is a cranky service. If your network seems OK leave it be for now.

DHCP is a little troublesome. If your internet and LAN connections work without serious issues, leave it alone for now.

0xd1 stop errors are almost always bad drivers. If you get one again, write down all four sets of numbers that follow, and see if it specifies a particular driver.

The 0x50, 0x79, 0xd9, and 0x24 are indicative of drive problems. If I had to guess it was a SCSI drive with bad drivers and/or a failing controller.

Do the chkdsk /r from Recovery Console and see how much of the problem it sorts.

 

[linney]

Try the RAM diagnostics again see what they say.

http://www.memtest86.com

http://oca.microsoft.com/en/windiag.asp

 

[brianlisk]

Thanks for the replies.

Master Browser: I am running on a network of 3 XP PCs, 2 Pros, 1 Home.

DCOM: Everything appears to be OK with the network... I haven't had any noticeable connection issues.

DHCP: Again... I haven't noticed any connection issues... I wonder why it failed to get an address...

0xd1: This was the latest 0xd1 from last night:
0x000000d1 (0x0000eb28, 0x00000002, 0x00000000, 0x0000eb28)
I don't know how I would find out which driver it is tho.

Other 0x's: I don't have SCSI in my PC. 1 Maxtor 80 gig hdd, 1 Sony CD Rom, 1 Sony CDRW, 1 Floppy. I have taken out all the expansion cards, to see if that helped, but it didn't... as far as I could tell.

Linney, I ran the Microsoft RAM test overnight. It did 78 passes with no errors.

Thank you all for your relplies!!!

Brian

 

[bcastner]

From MS:

"Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools."

What bothers me is that 0eb28 looks like a port read. This would be most likely on your network adapter card.

If you can swap NICs and test again it would help.

 

[brianlisk]

I will do that AS SOON as I get home.

Thanks!!

 

[brianlisk]

I lied. I didn't try it as soon as I got home. I didn't have another NIC. I got a 3C905B to try now. I will try that when I get home.

 

[brianlisk]

OK. I have more info, and I am 80% sure the mobo is bad.

During an XP Repair from the CD setup, I got a BSOD every time. I let it boot to the CD, it asked to install a new copy, or repair. I repaired, it asked the XP installation to repair, I hit 1, being the only XP installation on my PC. It asked me for the admin password, I typed it in, and then 8/10 times, it BSOD'd right there. The other 2 times, it let me at least type in chkdsk d: /r, and THEN it BSOD'd. Here are the BSODs that came up:

0x50 (0xffffff8b, 0x01, 0x801909b8, 0x00) - This happened 3 times.
0xc5 (0xaf458f00, 0x02, 0x00, 0x8082b245) - This happened once.
0x8e (automatically rebooted... but I caught 0x8e) - Happened twice.
0x7f (0x0d, 0x00, 0x00, 0x00) - Happened once
0x0a (0xc2c903c4, 0x02, 0x00, 0x801909ab) - Happened three times.

At

http://aumha.org/win5/kbestop.htm,

they pretty much all say that it is bad RAM. The ram has been tested several times, and it has come back good each time. The 0x7f suggest that it could be RAM or a faulty motherboard.

It did mention a Windows driver verifier program during the 0xc5 BSOD. I haven't heard of this. Is there such a program? Thanks.

You guys have been great! Any more ideas? Buy a new Mobo and see if that fixes it?

Brian

 

[bcastner]

See this to verify drivers:

http://support.microsoft.com/defaul...port/kb/articles/q308/5/14.asp&NoWebContent=1

 

[brianlisk]

Thank you.

I checked the unsigned driver list. It is attached. I know what some of them are. I have seen problems with nv4_mini.sys before... that has been referenced in a Blue screen. I believe that is NVidia drivers... I could be wrong, tho. The Papy drivers are for a video game... and then the obvious... navxxx... Norton Anti-virus. Please let me know if you see anything that sticks out. I believe all the drivers that I listed above are up to date. Should I google search the rest of them and find possible updates?? Thanks again for all your help!!! You guys are awesome!


********************************

Microsoft Signature Verification

Log file generated on 8/19/2003 at 1:08 AM
OS Platform: Windows 2000 (x86), Version: 5.1, Build: 2600, CSDVersion:
Scan Results: Total Files: 234, Signed: 198, Unsigned: 36, Not Scanned: 0

User-specified search path: *.*
User-specified search pattern: C:\WINDOWS\system32\drivers

File Modified Version Status Catalog Signed By
------------------ ------------ ----------- ------------ ----------- -------------------
[c:\windows\system32\drivers]
aslm75.sys 4/22/1997 None Not Signed N/A
asyncmac.sys 8/23/2001 2:5.1 Signed NT5.CAT Microsoft Windows XP Publisher
blackdrv.sys 10/11/2001 3.0.53.0 Not Signed N/A
cdac11ba.exe 2/6/2003 4.16.50.0 Not Signed N/A
cdac15ba.sys 2/6/2003 None Not Signed N/A
cdant.sys 7/18/2002 3.25.10.0 Not Signed N/A
cdantsrv.exe 7/18/2002 3.25.10.0 Not Signed N/A
cdr4_2k.sys 2/10/2003 2.5.0.98 Not Signed N/A
cdr4_xp.sys 2/10/2003 5.3.2.34 Not Signed N/A
cdralw2k.sys 2/10/2003 5.3.2.34 Not Signed N/A
cdudf.sys 2/10/2003 4.3.5.210 Not Signed N/A
cdudf_xp.sys 2/10/2003 5.3.2.34 Not Signed N/A
cvirta.sys 4/10/2003 4.0.0.64 Not Signed N/A
cvpndrva.sys 4/10/2003 0.0.0.0 Not Signed N/A
dvd_2k.sys 2/10/2003 5.3.2.34 Not Signed N/A
gt891xd.sys 4/27/2001 5.0.2195.1 Not Signed N/A
mmc_2k.sys 2/10/2003 5.3.2.34 Not Signed N/A
navap.sys 12/8/2001 8.0.0.0 Not Signed N/A
nv4_mini.old 11/18/2002 6.13.10.4109 Not Signed N/A
nv4_mini.sys 5/2/2003 6.14.10.4403 Not Signed N/A
ousb2hub.sys 8/1/2002 2.0.6.0 Not Signed N/A
ousbehci.sys 8/1/2002 2.0.6.0 Not Signed N/A
papycpu.sys 10/6/1998 None Not Signed N/A
papycpu2.sys 1/20/2002 None Not Signed N/A
papyjoy.sys 1/20/2002 None Not Signed N/A
pnp680.sys 3/15/2002 1.0.0.12 Not Signed N/A
pqntdrv.sys 9/16/2002 8.0.0.0 Not Signed N/A
pwd_2k.sys 2/10/2003 5.3.2.34 Not Signed N/A
scopex0.sys 11/4/2001 4.10.0.1998 Not Signed N/A
scopex1.sys 8/5/2001 5.0.2031.1 Not Signed N/A
secdrv.sys 6/30/2003 3.18.0.0 Not Signed N/A
sisagp.sys 12/26/2001 6.1.2091.0 Not Signed N/A
symredir.cat 5/31/2002 None Not Signed N/A
symredir.inf 5/31/2002 None Not Signed N/A
tmbi.sys 2/5/2003 None Not Signed N/A
udfreadr.sys 2/10/2003 1.0.3.117 Not Signed N/A
udfreadr_xp.sys 2/10/2003 5.3.2.34 Not Signed N/A

 

[bcastner]

Do you have an on-board video adapter builtin to the motherboard?

If so, use Device Manager to disable the device. If you uninstall it you will have a world of trouble unless there is a jumper on the motherboard itself to disable the device.

After disabling the device, go to the BIOS and leave it enabled but reduce its memory model to the lowest possible.
Do not disable it in BIOS unless you have a motherboard jumper for disabling the device.

 

[brianlisk]

No. No onboard video. The only thing onboard is audio.

I've got an A7S333 -

http://usa.asus.com/products/mb/socketa/a7s333/overview.htm

Thanks for the quick reply!

 

[linney]

What CD Burning Software do you have installed? What is using the Udfreadr files?

Can you run the Compatibility Checking program from the XP CD and see if that is picking up any problems.

 

[brianlisk]

I use a legit version of EZ CD Creator 5.

I have not run the Compatiblity Checking program from the CD. Can you point me in the direction of where to find that? Do I need to boot from the CD, or just run it from the CD in XP? Thank you VERY much!!

 

[linney]

Just run it from the CD in XP. The option is on the first screen. You also have an option to check out specific hardware and software with the latest compatibility lists at Microsoft as you proceed through the screens. Run the program as an Administrator.

 

[brianlisk]

I will do that. I am burning a couple CDs now, but I wanted to tell you that I just got a strange BSOD... one I haven't seen before. It had the general BS, but then there was this line:
A kernel thread terminated while holding a mutex.
The stop code was as follows:
0x4000008a (0x81e52c60, 0x81fe1030, 0x00, 0x00)

Just wanted to let you know.

linney and bcastner, you have NO idea how much I appreciate you help. It may be useless now... I bought a new motherboard today. It is in the mail. It is a ASUS A7N8X-Deluxe (nForce2). It SHOULD be here Friday. I am convinced that this is the problem for the sole reason that it gave me BSODs during setup. That should definately be hardware, right, since none of the drivers are even loaded yet??

Thank you both VERY much!!!

 

[linney]

Good luck with the new motherboard.