asked on
DRIVER IRQL NOT LESS OR EQUAL Problem
DRIVER IRQL NOT LESS OR EQUL Problem
I have been getting an increased number of "Blue Screen of Deaths". I will be working and all of a sudden it pops up. There doesn't seem to by any pattern. A few programs open usually for web development; Flash, Dreameaver, Photoshop, ect. So far it only seems to pop up when things are open. I can't duplicate the problem, it's random. A dump file is created when this happens and they are dated:
4/6/07
4/11/07
5/7/07
5/23/07
5/29/07
5/30/07
I have ran the microsoft RAM test but to no avail.
This is what my dump file looks like.
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini0
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
**************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
**************************
Executable search path is:
**************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
Unable to load image \WINDOWS\system32\ntoskrnl
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed May 30 12:01:54.531 2007 (GMT-4)
System Uptime: 0 days 3:18:03.262
**************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
Unable to load image \WINDOWS\system32\ntoskrnl
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..........................
Loading User Symbols
Loading unloaded module list
...............
ERROR: FindPlugIns 8007007b
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4, 2, 0, 880393dc}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntoskrnl.exe ( nt+9aac )
Followup: MachineOwner
---------
I need to figure out this problem. Any help would be greatly appreciated.
I'm using Windows XP Pro
2 gigs of ram/4 512s
Multiple HDs
To my knowledge everything is up to date.
If you need more information please let me know.
I have been getting an increased number of "Blue Screen of Deaths". I will be working and all of a sudden it pops up. There doesn't seem to by any pattern. A few programs open usually for web development; Flash, Dreameaver, Photoshop, ect. So far it only seems to pop up when things are open. I can't duplicate the problem, it's random. A dump file is created when this happens and they are dated:
4/6/07
4/11/07
5/7/07
5/23/07
5/29/07
5/30/07
I have ran the microsoft RAM test but to no avail.
This is what my dump file looks like.
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini0
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
**************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
**************************
Executable search path is:
**************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
Unable to load image \WINDOWS\system32\ntoskrnl
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed May 30 12:01:54.531 2007 (GMT-4)
System Uptime: 0 days 3:18:03.262
**************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
Unable to load image \WINDOWS\system32\ntoskrnl
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..........................
Loading User Symbols
Loading unloaded module list
...............
ERROR: FindPlugIns 8007007b
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4, 2, 0, 880393dc}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntoskrnl.exe ( nt+9aac )
Followup: MachineOwner
---------
I need to figure out this problem. Any help would be greatly appreciated.
I'm using Windows XP Pro
2 gigs of ram/4 512s
Multiple HDs
To my knowledge everything is up to date.
If you need more information please let me know.
Microsoft Legacy OSWindows XPWindows OS
Last Comment
johnb6767
Can you upload the dump files from c:\windows\minidump for us to look at?
Http://www.ee-stuff.com is a free upload site for us....
Http://www.ee-stuff.com is a free upload site for us....
ASKER
Thanks for the comments thus far.
SysExpert- I ran the Microsoft Ram test. I'm not sure what other hardware tests I should try running.
You can download my hijackthis v2 log file at http://www.allstateplastics.com/hijackthis.zip
I don't think it is a Malaware/Virus issue I run multiple scans on a weekly basis.
Spybot/Avast/Ad-Aware
john6767 you can download the dump file at http://www.allstateplastics.com/Mini053007-01.zip
SysExpert- I ran the Microsoft Ram test. I'm not sure what other hardware tests I should try running.
You can download my hijackthis v2 log file at http://www.allstateplastics.com/hijackthis.zip
I don't think it is a Malaware/Virus issue I run multiple scans on a weekly basis.
Spybot/Avast/Ad-Aware
john6767 you can download the dump file at http://www.allstateplastics.com/Mini053007-01.zip
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Oh, and it should be in c:\windows\system32\driver
Any place else and it *could be* malicious....
Any place else and it *could be* malicious....
ASKER
The blue screen of death happened again today.
johnb6767 I think you're right and SB live is the culprit.
I had reinstalled the driver but I did it through the XP ala cart installation method because I was getting a "Setup could not detect any Sound Blaster Audio card on your system." You know where you manually select the driver? Since that didn't work hence the blue screen I found this article
http://www.tweaksforgeeks.com/Install_Sound_Blaster_Web_Drivers.html
Here is an exerpt incase it gets deleted.
Anyway, before I did the CD install, I figured out how to make the downloaded drivers work. You will need to download WinZip and then open the Sound Blaster driver Uni-Pack with it (Right click and hit Extract to ...). Extract the files to a temporary directory, and then go into the device manager. Under audio devices, select the Sound Blaster (it'll be the one called Multimedia Audio Device and have a yellow ! next to it) and open it's properties. Click the Driver tab and then click Update Driver. Browse for the path that you extracted the Uni-Pack to, and open the Audio\Drivers\WhateverYour
This installation seemed to go much smoother. Hopefully no more blue screen. If I can go 3 weeks without the blue screen from today 6/07/07 I will award you the points for leading me in the right direction.
Thanks Again.
johnb6767 I think you're right and SB live is the culprit.
I had reinstalled the driver but I did it through the XP ala cart installation method because I was getting a "Setup could not detect any Sound Blaster Audio card on your system." You know where you manually select the driver? Since that didn't work hence the blue screen I found this article
http://www.tweaksforgeeks.com/Install_Sound_Blaster_Web_Drivers.html
Here is an exerpt incase it gets deleted.
Anyway, before I did the CD install, I figured out how to make the downloaded drivers work. You will need to download WinZip and then open the Sound Blaster driver Uni-Pack with it (Right click and hit Extract to ...). Extract the files to a temporary directory, and then go into the device manager. Under audio devices, select the Sound Blaster (it'll be the one called Multimedia Audio Device and have a yellow ! next to it) and open it's properties. Click the Driver tab and then click Update Driver. Browse for the path that you extracted the Uni-Pack to, and open the Audio\Drivers\WhateverYour
This installation seemed to go much smoother. Hopefully no more blue screen. If I can go 3 weeks without the blue screen from today 6/07/07 I will award you the points for leading me in the right direction.
Thanks Again.
Your welcome!!
2) Run any other hardware diagnostics
3) Check for Malware - Hijackthis ver 2 is good for this.
I hope this helps !