xr280xr said:When using my CD drives, I frequently get a blue screen o' death with a 0xD1
DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft is able to tell me that
it means there is a bad driver installed. How do I find the driver??
nass said:xr280xr said:When using my CD drives, I frequently get a blue screen o' death with a 0xD1
DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft is able to tell me that
it means there is a bad driver installed. How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand under the
CD-ROM and see if the Device is working or you can uninstall and reboot and
windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error messages(X)
that can shed some lights on the causer by double click on the error you will
get more info and you can copy and paste in your next post.
HTH.
nass
===
www.nasstec.co.uk
Hi, thanks for your response. There are never any other events in the
event
log consistently surrounding the error. It seems like it occurs when
more
than one window or application tries to access the disk drive at one
time.
When you ask for more info on the error, do you mean all of the
binary data
for the error? I would really like to know how to interpret that
data. I will post it when I get home tonight.
nass said:xr280xr said:When using my CD drives, I frequently get a blue screen o' death
with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft
is able to tell me that it means there is a bad driver installed.
How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand
under the CD-ROM and see if the Device is working or you can
uninstall and reboot and windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error
messages(X) that can shed some lights on the causer by double click
on the error you will get more info and you can copy and paste in
your next post.
HTH.
nass
===
www.nasstec.co.uk
Phydeaux said:Read these pages:
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx
and
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx
(watch word-wrap of these long URLs)
In there it will teach you how to download and use WinDBG tool from
Microsoft to find which driver is in conflict.
Hi, thanks for your response. There are never any other events in the
event
log consistently surrounding the error. It seems like it occurs when
more
than one window or application tries to access the disk drive at one
time.
When you ask for more info on the error, do you mean all of the
binary data
for the error? I would really like to know how to interpret that
data. I will post it when I get home tonight.
nass said::
When using my CD drives, I frequently get a blue screen o' death
with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft
is able to tell me that it means there is a bad driver installed.
How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand
under the CD-ROM and see if the Device is working or you can
uninstall and reboot and windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error
messages(X) that can shed some lights on the causer by double click
on the error you will get more info and you can copy and paste in
your next post.
HTH.
nass
===
www.nasstec.co.uk
Phydeaux said:Read these pages:
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx
and
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx
(watch word-wrap of these long URLs)
In there it will teach you how to download and use WinDBG tool from
Microsoft to find which driver is in conflict.
Hi, thanks for your response. There are never any other events in the
event
log consistently surrounding the error. It seems like it occurs when
more
than one window or application tries to access the disk drive at one
time.
When you ask for more info on the error, do you mean all of the
binary data
for the error? I would really like to know how to interpret that
data. I will post it when I get home tonight.
nass said::
When using my CD drives, I frequently get a blue screen o' death
with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft
is able to tell me that it means there is a bad driver installed.
How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand
under the CD-ROM and see if the Device is working or you can
uninstall and reboot and windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error
messages(X) that can shed some lights on the causer by double click
on the error you will get more info and you can copy and paste in
your next post.
HTH.
nass
===
www.nasstec.co.uk
xr280xr said:Wow, that's really cool, thank you. Unfortuneatly it didn't get me any closer
to a solution in this case. I'm not sure how to interpret everything it's
telling me but I don't see anywhere where it's plainly telling me the
culprit. Can anyone help with this debugger output:
Loading Dump File [C:\WINDOWS\Minidump\Mini031807-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Mar 18 15:20:22.703 2007 (GMT-7)
System Uptime: 0 days 3:23:31.383
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {5450018, 2, 1, 7c911713}
Probably caused by : Unknown_Image ( INVALID_CONTEXT )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 05450018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c911713, address which referenced memory
Debugging Details:
------------------
CURRENT_IRQL: 2
FAULTING_IP:
+7c911713
7c911713 66894118 mov word ptr [ecx+18h],ax
PROCESS_NAME: explorer.exe
BUGCHECK_STR: RAISED_IRQL_FAULT
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
SYMBOL_NAME: INVALID_CONTEXT
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
Followup: MachineOwner
---------
0: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
02fbf67c 7c820fd6 000a0000 00000000 01d41b70 0x7c911713
02fbf6ac 7ca0cad5 001147e0 0013e850 00000005 0x7c820fd6
02fbf6d4 7ca0c80b 02fbf6e8 02fbf910 00000000 0x7ca0cad5
02fbf8f4 7ca9af78 02fbf910 02fbf91c 7ca9afd3 0x7ca0c80b
02fbf900 7ca9afd3 0017e65c 02fbf930 00000004 0x7ca9af78
02fbf91c 7cb35518 02fbf930 00000004 02fbf9a0 0x7ca9afd3
02fbf93c 7caa0ea8 000b2998 00000000 00000000 0x7cb35518
02fbf960 7caa0fcc 7c9d86a8 000b2998 00000000 0x7caa0ea8
02fbf97c 7cb1edeb 01dda330 00000000 00000000 0x7caa0fcc
02fbf9ac 7cb219cb 0225f508 0226ba28 0224cdb8 0x7cb1edeb
02fbf9d4 7cb21a7a 00000000 00000000 02fbfb60 0x7cb219cb
02fbf9e4 7ca48d7d 00000000 039efdf8 7c9f75e8 0x7cb21a7a
02fbfb60 7c9f1da1 002300da 000004a8 00000000 0x7ca48d7d
02fbfba4 77d48734 002300da 000004a8 00000000 0x7c9f1da1
02fbfbd0 77d48816 7c9f1d4b 002300da 000004a8 0x77d48734
02fbfc38 77d489cd 000a5418 7c9f1d4b 002300da 0x77d48816
02fbfc98 77d48a10 02fbfcd8 00000000 02fbfcc0 0x77d489cd
02fbfca8 75f9d7c5 02fbfcd8 00000000 01dd70c8 0x77d48a10
02fbfcc0 75fa527a 02fbfcd8 0011ac10 00000000 0x75f9d7c5
02fbff34 80584c8a 86150be8 857ebda8 7ffaf000 0x75fa527a
Phydeaux said:Read these pages:
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx
and
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx
(watch word-wrap of these long URLs)
In there it will teach you how to download and use WinDBG tool from
Microsoft to find which driver is in conflict.
Hi, thanks for your response. There are never any other events in the
event
log consistently surrounding the error. It seems like it occurs when
more
than one window or application tries to access the disk drive at one
time.
When you ask for more info on the error, do you mean all of the
binary data
for the error? I would really like to know how to interpret that
data. I will post it when I get home tonight.
:
:
When using my CD drives, I frequently get a blue screen o' death
with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft
is able to tell me that it means there is a bad driver installed.
How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand
under the CD-ROM and see if the Device is working or you can
uninstall and reboot and windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error
messages(X) that can shed some lights on the causer by double click
on the error you will get more info and you can copy and paste in
your next post.
HTH.
nass
===
www.nasstec.co.uk
xr280xr said:Wow, that's really cool, thank you. Unfortuneatly it didn't get me any closer
to a solution in this case. I'm not sure how to interpret everything it's
telling me but I don't see anywhere where it's plainly telling me the
culprit. Can anyone help with this debugger output:
Loading Dump File [C:\WINDOWS\Minidump\Mini031807-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Mar 18 15:20:22.703 2007 (GMT-7)
System Uptime: 0 days 3:23:31.383
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {5450018, 2, 1, 7c911713}
Probably caused by : Unknown_Image ( INVALID_CONTEXT )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 05450018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c911713, address which referenced memory
Debugging Details:
------------------
CURRENT_IRQL: 2
FAULTING_IP:
+7c911713
7c911713 66894118 mov word ptr [ecx+18h],ax
PROCESS_NAME: explorer.exe
BUGCHECK_STR: RAISED_IRQL_FAULT
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
SYMBOL_NAME: INVALID_CONTEXT
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
Followup: MachineOwner
---------
0: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
02fbf67c 7c820fd6 000a0000 00000000 01d41b70 0x7c911713
02fbf6ac 7ca0cad5 001147e0 0013e850 00000005 0x7c820fd6
02fbf6d4 7ca0c80b 02fbf6e8 02fbf910 00000000 0x7ca0cad5
02fbf8f4 7ca9af78 02fbf910 02fbf91c 7ca9afd3 0x7ca0c80b
02fbf900 7ca9afd3 0017e65c 02fbf930 00000004 0x7ca9af78
02fbf91c 7cb35518 02fbf930 00000004 02fbf9a0 0x7ca9afd3
02fbf93c 7caa0ea8 000b2998 00000000 00000000 0x7cb35518
02fbf960 7caa0fcc 7c9d86a8 000b2998 00000000 0x7caa0ea8
02fbf97c 7cb1edeb 01dda330 00000000 00000000 0x7caa0fcc
02fbf9ac 7cb219cb 0225f508 0226ba28 0224cdb8 0x7cb1edeb
02fbf9d4 7cb21a7a 00000000 00000000 02fbfb60 0x7cb219cb
02fbf9e4 7ca48d7d 00000000 039efdf8 7c9f75e8 0x7cb21a7a
02fbfb60 7c9f1da1 002300da 000004a8 00000000 0x7ca48d7d
02fbfba4 77d48734 002300da 000004a8 00000000 0x7c9f1da1
02fbfbd0 77d48816 7c9f1d4b 002300da 000004a8 0x77d48734
02fbfc38 77d489cd 000a5418 7c9f1d4b 002300da 0x77d48816
02fbfc98 77d48a10 02fbfcd8 00000000 02fbfcc0 0x77d489cd
02fbfca8 75f9d7c5 02fbfcd8 00000000 01dd70c8 0x77d48a10
02fbfcc0 75fa527a 02fbfcd8 0011ac10 00000000 0x75f9d7c5
02fbff34 80584c8a 86150be8 857ebda8 7ffaf000 0x75fa527a
Phydeaux said:Read these pages:
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx
and
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx
(watch word-wrap of these long URLs)
In there it will teach you how to download and use WinDBG tool from
Microsoft to find which driver is in conflict.
Hi, thanks for your response. There are never any other events in the
event
log consistently surrounding the error. It seems like it occurs when
more
than one window or application tries to access the disk drive at one
time.
When you ask for more info on the error, do you mean all of the
binary data
for the error? I would really like to know how to interpret that
data. I will post it when I get home tonight.
:
:
When using my CD drives, I frequently get a blue screen o' death
with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft
is able to tell me that it means there is a bad driver installed.
How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand
under the CD-ROM and see if the Device is working or you can
uninstall and reboot and windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error
messages(X) that can shed some lights on the causer by double click
on the error you will get more info and you can copy and paste in
your next post.
HTH.
nass
===
www.nasstec.co.uk
nass said:First try this for the Error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
"STOP:0xD1" Error Message When You Start Your Windows XP-Based Computer
http://support.microsoft.com/kb/316208
You receive a STOP 0xD1 error message when you start your Windows XP-based
computer
http://support.microsoft.com/kb/839876
Then the Dump file is the Firewall outpost, what Anti-Virus are you using
and Firewall?.
Open a run command and type in:
verifier.exe click [OK] and see unsigned Driver and what they are.
Does this new installation, if it it did you install the Motherboard Drivers
and updated to the latest ones?.
Also what mouse and Video card are you using check what IRQ both they Use by
going to the Device Manager and Right click Them and select properties then
Drive details.
MS Mouse:
http://support.microsoft.com/kb/82382
Video Cards Using S3 Chip Set May Cause Hardware Conflicts
http://support.microsoft.com/kb/104400
HTH.
Let us know.
nass
xr280xr said:Wow, that's really cool, thank you. Unfortuneatly it didn't get me any closer
to a solution in this case. I'm not sure how to interpret everything it's
telling me but I don't see anywhere where it's plainly telling me the
culprit. Can anyone help with this debugger output:
Loading Dump File [C:\WINDOWS\Minidump\Mini031807-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Mar 18 15:20:22.703 2007 (GMT-7)
System Uptime: 0 days 3:23:31.383
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {5450018, 2, 1, 7c911713}
Probably caused by : Unknown_Image ( INVALID_CONTEXT )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 05450018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c911713, address which referenced memory
Debugging Details:
------------------
CURRENT_IRQL: 2
FAULTING_IP:
+7c911713
7c911713 66894118 mov word ptr [ecx+18h],ax
PROCESS_NAME: explorer.exe
BUGCHECK_STR: RAISED_IRQL_FAULT
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
SYMBOL_NAME: INVALID_CONTEXT
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
Followup: MachineOwner
---------
0: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
02fbf67c 7c820fd6 000a0000 00000000 01d41b70 0x7c911713
02fbf6ac 7ca0cad5 001147e0 0013e850 00000005 0x7c820fd6
02fbf6d4 7ca0c80b 02fbf6e8 02fbf910 00000000 0x7ca0cad5
02fbf8f4 7ca9af78 02fbf910 02fbf91c 7ca9afd3 0x7ca0c80b
02fbf900 7ca9afd3 0017e65c 02fbf930 00000004 0x7ca9af78
02fbf91c 7cb35518 02fbf930 00000004 02fbf9a0 0x7ca9afd3
02fbf93c 7caa0ea8 000b2998 00000000 00000000 0x7cb35518
02fbf960 7caa0fcc 7c9d86a8 000b2998 00000000 0x7caa0ea8
02fbf97c 7cb1edeb 01dda330 00000000 00000000 0x7caa0fcc
02fbf9ac 7cb219cb 0225f508 0226ba28 0224cdb8 0x7cb1edeb
02fbf9d4 7cb21a7a 00000000 00000000 02fbfb60 0x7cb219cb
02fbf9e4 7ca48d7d 00000000 039efdf8 7c9f75e8 0x7cb21a7a
02fbfb60 7c9f1da1 002300da 000004a8 00000000 0x7ca48d7d
02fbfba4 77d48734 002300da 000004a8 00000000 0x7c9f1da1
02fbfbd0 77d48816 7c9f1d4b 002300da 000004a8 0x77d48734
02fbfc38 77d489cd 000a5418 7c9f1d4b 002300da 0x77d48816
02fbfc98 77d48a10 02fbfcd8 00000000 02fbfcc0 0x77d489cd
02fbfca8 75f9d7c5 02fbfcd8 00000000 01dd70c8 0x77d48a10
02fbfcc0 75fa527a 02fbfcd8 0011ac10 00000000 0x75f9d7c5
02fbff34 80584c8a 86150be8 857ebda8 7ffaf000 0x75fa527a
Phydeaux said:Read these pages:
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx
and
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx
(watch word-wrap of these long URLs)
In there it will teach you how to download and use WinDBG tool from
Microsoft to find which driver is in conflict.
xr280xr wrote:
Hi, thanks for your response. There are never any other events in the
event
log consistently surrounding the error. It seems like it occurs when
more
than one window or application tries to access the disk drive at one
time.
When you ask for more info on the error, do you mean all of the
binary data
for the error? I would really like to know how to interpret that
data. I will post it when I get home tonight.
:
:
When using my CD drives, I frequently get a blue screen o' death
with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft
is able to tell me that it means there is a bad driver installed.
How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand
under the CD-ROM and see if the Device is working or you can
uninstall and reboot and windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error
messages(X) that can shed some lights on the causer by double click
on the error you will get more info and you can copy and paste in
your next post.
HTH.
nass
===
www.nasstec.co.uk
xr280xr said:Ok, I've finally found the time to troubleshoot this thing. I'll go through
your post top to bottom. None of the windows patches quite matched my
symptoms. I had previously tried installing the one that most closely matched
but it did not solve the issue.
What does "Firewall outpost" mean? How could you tell from the dump. I was
not aware of it but my McAfee enterprise edition 7 has a small firewall
component (it defines a few port blocking rules). Here are the results from
verifier.exe:
cdawdm.sys Far Stone SCSI Miniport
entdrv51.sys EntDrv
This driver part of Soyo dragon Motherboard, make sure all the drivers forfshook.sys <unknown>
Try to clean all traces for this app if uninstalled it.<-----Motherboard (ECS - Elite Group)
mvstdi5x.sys Anti-Virus Mini-Firewall Driver
McAfee
mxlw2k.sys MusicMatch Access Layer KMD
McAfee Filternaiavf5x.sys Anti-Virus File System Filter Driver
part of SafeDisc CD protection scheme, some games use it.secdrv.sys <unkown>
<-----Macrovision SECURITY Driver
ucdnt.sys Xirlink USB Camera Driver
The Dump file saying this if you look to it, because you have the McAfeeusbvm31b.sys Video streaming and Capture Device Driver
I'm curious as to how you narrowed down the info to the firewall.
1=> secdrv.sys <unkown>unknown drivers above looked suspicious to me.
xr280xr said:Ok, I've finally found the time to troubleshoot this thing. I'll go through
your post top to bottom. None of the windows patches quite matched my
symptoms. I had previously tried installing the one that most closely matched
but it did not solve the issue.
What does "Firewall outpost" mean? How could you tell from the dump. I was
not aware of it but my McAfee enterprise edition 7 has a small firewall
component (it defines a few port blocking rules). Here are the results from
verifier.exe:
cdawdm.sys Far Stone SCSI Miniport
entdrv51.sys EntDrv
on to post, my computer crashed and restarted... Microsoft was actually able
to identify that it was the music match driver. I was using an old version of
music match because they had a free wav -> mp3 converter that I use
frequently, but I uninstalled that. The original issue is probably still
present though.
My device manager swears I'm using a logitech mouse (Logitech USB
First/Pilot Mouse+) even though the mouse has hewlett-packard written all
over it. My video card is an ATi Radeon 9800. It looks like my video card is
on IRQ 16 and the USB controller is on 21 (although I could've sworn right
after my computer POSTs, it lists IRQs and shows USB and video as 11).
Thanks!!
nass said:First try this for the Error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
"STOP:0xD1" Error Message When You Start Your Windows XP-Based Computer
http://support.microsoft.com/kb/316208
You receive a STOP 0xD1 error message when you start your Windows XP-based
computer
http://support.microsoft.com/kb/839876
Then the Dump file is the Firewall outpost, what Anti-Virus are you using
and Firewall?.
Open a run command and type in:
verifier.exe click [OK] and see unsigned Driver and what they are.
Does this new installation, if it it did you install the Motherboard Drivers
and updated to the latest ones?.
Also what mouse and Video card are you using check what IRQ both they Use by
going to the Device Manager and Right click Them and select properties then
Drive details.
MS Mouse:
http://support.microsoft.com/kb/82382
Video Cards Using S3 Chip Set May Cause Hardware Conflicts
http://support.microsoft.com/kb/104400
HTH.
Let us know.
nass
xr280xr said:Wow, that's really cool, thank you. Unfortuneatly it didn't get me any closer
to a solution in this case. I'm not sure how to interpret everything it's
telling me but I don't see anywhere where it's plainly telling me the
culprit. Can anyone help with this debugger output:
Loading Dump File [C:\WINDOWS\Minidump\Mini031807-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Mar 18 15:20:22.703 2007 (GMT-7)
System Uptime: 0 days 3:23:31.383
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {5450018, 2, 1, 7c911713}
Probably caused by : Unknown_Image ( INVALID_CONTEXT )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 05450018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c911713, address which referenced memory
Debugging Details:
------------------
CURRENT_IRQL: 2
FAULTING_IP:
+7c911713
7c911713 66894118 mov word ptr [ecx+18h],ax
PROCESS_NAME: explorer.exe
BUGCHECK_STR: RAISED_IRQL_FAULT
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
SYMBOL_NAME: INVALID_CONTEXT
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
BUCKET_ID: RAISED_IRQL_FAULT_explorer.exe_INVALID_CONTEXT
Followup: MachineOwner
---------
0: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
02fbf67c 7c820fd6 000a0000 00000000 01d41b70 0x7c911713
02fbf6ac 7ca0cad5 001147e0 0013e850 00000005 0x7c820fd6
02fbf6d4 7ca0c80b 02fbf6e8 02fbf910 00000000 0x7ca0cad5
02fbf8f4 7ca9af78 02fbf910 02fbf91c 7ca9afd3 0x7ca0c80b
02fbf900 7ca9afd3 0017e65c 02fbf930 00000004 0x7ca9af78
02fbf91c 7cb35518 02fbf930 00000004 02fbf9a0 0x7ca9afd3
02fbf93c 7caa0ea8 000b2998 00000000 00000000 0x7cb35518
02fbf960 7caa0fcc 7c9d86a8 000b2998 00000000 0x7caa0ea8
02fbf97c 7cb1edeb 01dda330 00000000 00000000 0x7caa0fcc
02fbf9ac 7cb219cb 0225f508 0226ba28 0224cdb8 0x7cb1edeb
02fbf9d4 7cb21a7a 00000000 00000000 02fbfb60 0x7cb219cb
02fbf9e4 7ca48d7d 00000000 039efdf8 7c9f75e8 0x7cb21a7a
02fbfb60 7c9f1da1 002300da 000004a8 00000000 0x7ca48d7d
02fbfba4 77d48734 002300da 000004a8 00000000 0x7c9f1da1
02fbfbd0 77d48816 7c9f1d4b 002300da 000004a8 0x77d48734
02fbfc38 77d489cd 000a5418 7c9f1d4b 002300da 0x77d48816
02fbfc98 77d48a10 02fbfcd8 00000000 02fbfcc0 0x77d489cd
02fbfca8 75f9d7c5 02fbfcd8 00000000 01dd70c8 0x77d48a10
02fbfcc0 75fa527a 02fbfcd8 0011ac10 00000000 0x75f9d7c5
02fbff34 80584c8a 86150be8 857ebda8 7ffaf000 0x75fa527a
:
Read these pages:
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx
and
http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx
(watch word-wrap of these long URLs)
In there it will teach you how to download and use WinDBG tool from
Microsoft to find which driver is in conflict.
xr280xr wrote:
Hi, thanks for your response. There are never any other events in the
event
log consistently surrounding the error. It seems like it occurs when
more
than one window or application tries to access the disk drive at one
time.
When you ask for more info on the error, do you mean all of the
binary data
for the error? I would really like to know how to interpret that
data. I will post it when I get home tonight.
:
:
When using my CD drives, I frequently get a blue screen o' death
with a 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL stop message. Microsoft
is able to tell me that it means there is a bad driver installed.
How do I find the driver??
Two things to check:
1.... Your Device Manager, by Right clicking MY Computer and select
Properties, then click Hardware and click Device Manager, expand
under the CD-ROM and see if the Device is working or you can
uninstall and reboot and windows will install it for you.
2... Open a run command and type in :
eventvwr.msc click [OK], on Event Viewer look for any Error
messages(X) that can shed some lights on the causer by double click
on the error you will get more info and you can copy and paste in
your next post.
HTH.
nass
===
www.nasstec.co.uk