katherine502
August 19th, 2004, 08:16 PM
W2KPro SP3
AMD Athlon 1 ghtz
768 megs ram
80 gig C drive/76 gigs free
40 gig D drive/34 gigs free
Since recovering from a C drive failure, I have gotten the blue screen with W2K Stop Error (bugcheck) 0x000000d1 on three occassions. An EventID.com comment says this event can be caused by a faulty device driver.
The first time it happened, I don't recall what I had just done. The second time, I was rebooting after installing new software. Yesterday, it happend when rebooting after Norton Antivirus updated its virus definitions.
Following are the two events listed in Event Viewer:
FROM SYSTEM LOG:
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/18/2004
Time: 6:41:34 PM
User: N/A
Computer: KAY1
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000001e, 0x00000002, 0x00000000, 0xbfedcc15). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini081804-01.dmp.
FROM APPLICATION LOG:
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 61
Date: 8/18/2004
Time: 6:43:14 PM
User: N/A
Computer: KAY1
Description:
WMI ADAP was unable to process the PerfDisk performance library due to a time violation in the open function
FOLLOWING IS EVERYTHING THE BLUE SCREEN SAID (the first 2 or 3 letters on the left are cut off on my monitor for some reason, so the question marks are mine):
??Stop: 0x000000D1, (Ox00000002, Ox00000000, OxBFEDCC15)
??Address BFEDCC15 base at BFEC5000, DateStemp 3cdaee06-NDIS.sys
??nning dump of physical memory
Is there anyone here who has the ability and would be willing to look at my
dmp file and tell me what driver is causing this? If I am on the wrong track in my thinking or you have other ideas about what is wrong, please let me know.
TIA,
Katherine
AMD Athlon 1 ghtz
768 megs ram
80 gig C drive/76 gigs free
40 gig D drive/34 gigs free
Since recovering from a C drive failure, I have gotten the blue screen with W2K Stop Error (bugcheck) 0x000000d1 on three occassions. An EventID.com comment says this event can be caused by a faulty device driver.
The first time it happened, I don't recall what I had just done. The second time, I was rebooting after installing new software. Yesterday, it happend when rebooting after Norton Antivirus updated its virus definitions.
Following are the two events listed in Event Viewer:
FROM SYSTEM LOG:
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/18/2004
Time: 6:41:34 PM
User: N/A
Computer: KAY1
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000001e, 0x00000002, 0x00000000, 0xbfedcc15). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini081804-01.dmp.
FROM APPLICATION LOG:
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 61
Date: 8/18/2004
Time: 6:43:14 PM
User: N/A
Computer: KAY1
Description:
WMI ADAP was unable to process the PerfDisk performance library due to a time violation in the open function
FOLLOWING IS EVERYTHING THE BLUE SCREEN SAID (the first 2 or 3 letters on the left are cut off on my monitor for some reason, so the question marks are mine):
??Stop: 0x000000D1, (Ox00000002, Ox00000000, OxBFEDCC15)
??Address BFEDCC15 base at BFEC5000, DateStemp 3cdaee06-NDIS.sys
??nning dump of physical memory
Is there anyone here who has the ability and would be willing to look at my
dmp file and tell me what driver is causing this? If I am on the wrong track in my thinking or you have other ideas about what is wrong, please let me know.
TIA,
Katherine