BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL

brittnic · Jul 30, 2012

Started getting random BSOD and crash dump beginning three days ago with the message: DRIVER_IRQL_NOT_LESS_OR_EQUAL. Have not downloaded any programs, music, movies, etc. within that time frame or messed with the registry. Restored from restore point of t-7 days and still am having the same problem. Cannot correlate it to anything I do in particular, but it seems to always happen when I am listening to music or watching a streaming video online, although this could just be a coincidence as I often have music running in the background. I get an error message when I try to run perfmon /report (the interface is unknown).

Also, after this dump Num Lock is always on. I don't know if this is relevant, but it only happens after this BSOD and crash dump. If I did a system shut down and restart, Num Lock will be off. I don't know if that helps. AVG complete virus scan was clean.

Please see attached. Thanks for your help, as I really don't want to do an entire system restore at this point (have a lot of projects ongoing and it would be a huge hassle). Thanks again!

jcgriff2 · Jul 30, 2012

Hi -

Update these drivers -

Code:

[font=lucida console]
iaStor.sys           Thu Jun 04 21:53:40 2009 (4A287AA4) - Intel storage
netw5v64.sys         Thu May 14 11:51:34 2009 (4A0C3E06) - Intel wifi
yk62x64.sys          Mon Feb 23 10:02:27 2009 (49A2BA83) - Marvell Yukon Ethernet
[/font]

http://sysnative.com/drivers/driver.php?id=iaStor.sys
http://sysnative.com/drivers/driver.php?id=netw5v64.sys
http://sysnative.com/drivers/driver.php?id=yk62x64.sys

Remove Daemon Tools/ Alcohol 120 & Elby -

Code:

[font=lucida console]sptd.sys             Sun Oct 11 16:55:14 2009 (4AD24632)
ElbyCDIO.sys         Thu Dec 17 17:25:16 2009 (4B2AAFCC)
[/font]

http://sysnative.com/drivers/driver.php?id=sptd.sys
http://sysnative.com/drivers/driver.php?id=ElbyCDIO.sys

VAIO VGNFW590F3B - http://esupport.sony.com/perl/model-home.pl?mdl=VGN-FW590F3B

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:

[font=lucida console][SIZE=1]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\073012-53165-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 30 20:34:42.313 2012 (GMT-4)
System Uptime: 0 days 1:11:14.373
BugCheck D1, {0, 2, 8, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  FlashPlayerPlu
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000
BiosVersion = R4070Y0
BiosReleaseDate = 09/04/2009
SystemManufacturer = Sony Corporation
SystemProductName = VGNFW590F3B
MaxSpeed:     2200
CurrentSpeed: 2194
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\073012-42151-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul 30 19:22:50.342 2012 (GMT-4)
System Uptime: 0 days 19:57:41.965
BugCheck FC, {fffff88001ea5c97, 8000000137e00121, fffff8800b5d93b0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+438fc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+438fc
Bugcheck code 000000FC
Arguments fffff880`01ea5c97 80000001`37e00121 fffff880`0b5d93b0 00000000`00000000
BiosVersion = R4070Y0
BiosReleaseDate = 09/04/2009
SystemManufacturer = Sony Corporation
SystemProductName = VGNFW590F3B
MaxSpeed:     2200
CurrentSpeed: 2193
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071812-45567-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 18 15:11:52.772 2012 (GMT-4)
System Uptime: 5 days 10:45:51.520
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 9087, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : iaStor.sys ( iaStor+4aa73 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9087
PROCESS_NAME:  IAANTmon.exe
FAILURE_BUCKET_ID:  X64_0x9087_iaStor+4aa73
Bugcheck code 00009087
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = R4070Y0
BiosReleaseDate = 09/04/2009
SystemManufacturer = Sony Corporation
SystemProductName = VGNFW590F3B
MaxSpeed:     2200
CurrentSpeed: 2194
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\071012-31465-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jul 10 14:16:35.280 2012 (GMT-4)
System Uptime: 0 days 20:15:30.028
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
BugCheck 9087, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : iaStor.sys ( iaStor+4aa73 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9087
PROCESS_NAME:  IAANTmon.exe
FAILURE_BUCKET_ID:  X64_0x9087_iaStor+4aa73
Bugcheck code 00009087
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = R4070Y0
BiosReleaseDate = 09/04/2009
SystemManufacturer = Sony Corporation
SystemProductName = VGNFW590F3B
MaxSpeed:     2200
CurrentSpeed: 2194
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


	    
             
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/SIZE]  
[/font]

writhziden · Jul 31, 2012

To supplement the already excellent advice given, here are the best steps to update the Intel storage controller drivers that are being blamed both directly and indirectly in your crashes:

Go to Intel® Driver Update Utility,
run the utility,
click on the link for Chipset Family,
Scroll down and select Standard Version or Intel Rapid Storage Technology (not the Enterprise version).
There is a page that loads with information on other Intel drivers for your system including Intel storage drivers. You may have to let it load for 10-15 seconds before it displays your particular storage drivers link.
Go to that link, download the drivers, and install them.

brittnic · Aug 5, 2012

The utility is telling me my storage drive is up to date. I am still getting the crashes though. Is there a direct link to the correct driver? I have followed the other suggestions. Thanks for your help.

writhziden said:
To supplement the already excellent advice given, here are the best steps to update the Intel storage controller drivers that are being blamed both directly and indirectly in your crashes:

Go to Intel® Driver Update Utility,

run the utility,

click on the link for Chipset Family,

Scroll down and select Standard Version or Intel Rapid Storage Technology (not the Enterprise version).

There is a page that loads with information on other Intel drivers for your system including Intel storage drivers. You may have to let it load for 10-15 seconds before it displays your particular storage drivers link.

Go to that link, download the drivers, and install them.

writhziden · Aug 5, 2012

Intel® ICH9M-E/M SATA AHCI Driver

To fully re-install a driver, use the following steps.

First, download the latest driver. Then do the next steps.
Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Find the device you are trying to uninstall by expanding the appropriate set of devices
Right click the device
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer only if Windows asks you to.
Install the latest driver for the device.

Alternatively:

Login as an adminstrative user.
First, download the latest driver. Then do the next steps.
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Find the device you are trying to uninstall by expanding the appropriate set of devices
Right click the device
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer only if Windows asks you to.
Install the latest driver for the device.

You can find the Intel AHCI driver under IDE ATA/ATAPI controllers in device manager.

Also, please upload the latest crash reports by following the Blue Screen of Death (BSOD) Posting Instructions - Windows 8, 7 & Vista.

brittnic · Aug 19, 2012

Hey guys, thanks for your help so far. I apologize for the delay, I got to the point where I didn't have time to fix anything -- it would each crash or go black and restart. I gave it a rest for a week or so and did a system repair and restore to a previous date. I've been on it for about an hour and no crashes yet. Have attached the latest BSOD report. Thanks again for all of your assistance so far.

jcgriff2 · Aug 20, 2012

Hi -

There are no new BSODs.

Install the Intel driver per writhziden's instructions.

No udated drivers at Sony - http://esupport.sony.com/US/p/model...te_id=1&region_id=1&tab=download#/downloadTab

Regards. . .

jcgriff2

brittnic · Aug 21, 2012

I installed the driver per the instructions above. Had two more BSODs yesterday (attached) and a SYSTEM_SERVICE_EXCEPTION. Not sure what the problem is. Installed the latest Windows Update, then got the latest BSOD. The SYSTEM_SERVICE_EXCEPTION is not included in this attachment, as I didn't know if I would have time to do another scan, so I just transferred the previous ZIP to my thumb drive and shut down. AVG scan is still negative and no new downloads or anything. Thanks.

writhziden · Aug 21, 2012

The latest crash blamed Catalyst Control Center as a possible cause. I recommend that you install your AMD drivers without the Catalyst Control Center/Vision Engine Control Center software. Download the version of ATI drivers that you want to install, and then do the following steps.

Start the installation program to install your drivers and ATI software. When you get to the option to Express/Custom install, cancel the installation. Your drivers should now exist in C:\AMD\Support\xx-x_vista_win7_64_dd_ccc where the x's replace your version number of the driver software.
Uninstall all AMD software related to your graphics card by uninstalling AMD Catalyst Install Manager in Start Menu -> Control Panel -> Uninstall a program
If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Expand Display adapters
6. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Alternatively:
1. Login as an adminstrative user
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer.
Re-install your drivers from the C:\AMD\Support\xx-x_vista_win7_64_dd_ccc folder. See You cannot install a device driver by using its installation program in Windows Vista (or Windows 7) and scroll down to

To locate the .inf file and manually install the driver

Click to expand...

for steps to manually install the driver.

brittnic · Aug 21, 2012

Quickly.

writhziden · Aug 21, 2012

Recommendations:

Still see Catalyst Control Center installed. Have you tried running without it yet? The most recent crashes are all display card driver related, so I still suspect Catalyst Control Center.

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

**************************Tue Aug 21 21:11:26.432 2012 (GMT-6)**************************
[COLOR=RED][B]SFEP.sys                    Thu Aug  2 23:35:53 2007 (46B2BEB9)[/B][/COLOR]
btwl2cap.sys                Fri Apr  3 18:28:45 2009 (49D6A9BD)
GEARAspiWDM.sys             Mon May 18 06:17:04 2009 (4A1151C0)
ArcSoftKsUFilter.sys        Mon May 25 02:27:31 2009 (4A1A5673)
iaStor.sys                  Thu Jun  4 19:53:40 2009 (4A287AA4)
rimssn64.sys                Wed Jun 10 20:22:31 2009 (4A306A67)
risdsn64.sys                Thu Jun 11 21:49:37 2009 (4A31D051)
Apfiltr.sys                 Tue Jun 16 16:09:26 2009 (4A381816)
btwavdt.sys                 Wed Jun 24 23:50:13 2009 (4A431015)
btwrchid.sys                Wed Jun 24 23:51:37 2009 (4A431069)
btwaudio.sys                Wed Jul  1 07:54:56 2009 (4A4B6AB0)
RTKVHD64.sys                Thu Jul  2 03:42:36 2009 (4A4C810C)
atikmdag.sys                Fri Jul 10 10:34:38 2009 (4A576D9E)
intelppm.sys                Mon Jul 13 17:19:25 2009 (4A5BC0FD)
RtHDMIVX.sys                Thu Jul 16 21:52:36 2009 (4A5FF584)
VClone.sys                  Sun Aug  9 15:25:45 2009 (4A7F3ED9)
PxHlpa64.sys                Tue Oct 20 12:08:42 2009 (4ADDFCAA)
ElbyCDIO.sys                Thu Dec 17 15:25:16 2009 (4B2AAFCC)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
yk62x64.sys                 Thu Sep  8 01:34:54 2011 (4E68701E)
avgmfx64.sys                Fri Dec 23 05:08:12 2011 (4EF46F2C)
NETwNs64.sys                Mon Jan 23 15:44:07 2012 (4F1DE2B7)
avgrkx64.sys                Mon Jan 30 20:11:41 2012 (4F275BED)
avgldx64.sys                Tue Feb 21 20:57:53 2012 (4F4467C1)
avgtdia.sys                 Sun Mar 18 21:53:32 2012 (4F66ADBC)
avgidsha.sys                Wed Apr 18 20:19:15 2012 (4F8F7623)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 21 21:03:49.577 2012 (GMT-6)**************************
[COLOR=RED][B]regi.sys                    Mon Apr 16 09:19:10 2007 (462393EE)[/B][/COLOR]
avgidsdrivera.sys           Fri Dec 23 05:05:21 2011 (4EF46E81)
avgidsfiltera.sys           Fri Dec 23 05:05:40 2011 (4EF46E94)

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

**************************Tue Aug 21 21:11:26.432 2012 (GMT-6)**************************
Loading Dump File [D:\Kingston\BSODDmpFiles\brittnic\082112-77282-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:01:22.180[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff8000337dc10, fffff880027610d0, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+40 )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME: [B]services.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!ObReferenceObjectByHandleWithTag+40[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed:[B]2194[/B]
  BIOS Version                  R4070Y0
  BIOS Release Date             09/04/2009
  Manufacturer                  Sony Corporation
  Product Name                  VGNFW590F3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug 21 21:03:49.577 2012 (GMT-6)**************************
Loading Dump File [D:\Kingston\BSODDmpFiles\brittnic\082112-78343-01.dmp]
Loading Dump File [D:\Kingston\BSODDmpFiles\brittnic\082112-74802-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:04:08.325[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff80003084eba, fffff88002c27140, 0}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!NtSetInformationWorkerFactory+1f7 )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME: [B]svchost.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!NtSetInformationWorkerFactory+1f7[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed:[B]2193[/B]
  BIOS Version                  R4070Y0
  BIOS Release Date             09/04/2009
  Manufacturer                  Sony Corporation
  Product Name                  VGNFW590F3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 20 22:27:58.039 2012 (GMT-6)**************************
Loading Dump File [D:\Kingston\BSODDmpFiles\brittnic\082012-56940-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:07:17.787[/B]
BugCheck Code: [B]BugCheck 3B, {c000001d, fffff960000d8a01, fffff88007b8bc00, 0}[/B]
Probably caused by :[B]hardware ( win32k!xxxMouseActivate+2b1 )[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME: [B]firefox.exe[/B]
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed:[B]2194[/B]
  BIOS Version                  R4070Y0
  BIOS Release Date             09/04/2009
  Manufacturer                  Sony Corporation
  Product Name                  VGNFW590F3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

brittnic · Aug 25, 2012

writhziden said:
Recommendations:
Still see Catalyst Control Center installed. Have you tried running without it yet? The most recent crashes are all display card driver related, so I still suspect Catalyst Control Center.

I apologize, I had another BSOD while I was downloading the driver from the AMD website and thought the additional crash data might be useful. I was successful in updating the driver and things seem to be going alright for now (been running about 2 hours).

brittnic · Aug 25, 2012

brittnic said:
writhziden said:

Recommendations:
Still see Catalyst Control Center installed. Have you tried running without it yet? The most recent crashes are all display card driver related, so I still suspect Catalyst Control Center.

Click to expand...

I apologize, I had another BSOD while I was downloading the driver from the AMD website and thought the additional crash data might be useful. I was successful in updating the driver and things seem to be going alright for now (been running about 2 hours).

That didn't last long. Had first BSOD while typing an e-mail. As it was rebooting, had multiple BSOD, including during system repair. Also BSOD in safe mode. Will hopefully work long enough to get the latest report, but I feel like we are chasing our tail here. I keep this computer in good shape, not very many programs installed. I use Revo Uninstaller quite often to uninstall things I don't use, as well as CCleaner. Virus scan everyday and don't download very often. Could this possibly be a hardware problem?

It seems it is always a string of BSOD at this point. I get one, then it restarts. I get another during restart. Then another, then another... Will keep updated. Thanks again for all the help so far.

brittnic · Aug 25, 2012

brittnic said:
brittnic said:

writhziden said:

Recommendations:
Still see Catalyst Control Center installed. Have you tried running without it yet? The most recent crashes are all display card driver related, so I still suspect Catalyst Control Center.

Click to expand...

I apologize, I had another BSOD while I was downloading the driver from the AMD website and thought the additional crash data might be useful. I was successful in updating the driver and things seem to be going alright for now (been running about 2 hours).

Click to expand...

That didn't last long. Had first BSOD while typing an e-mail. As it was rebooting, had multiple BSOD, including during system repair. Also BSOD in safe mode. Will hopefully work long enough to get the latest report, but I feel like we are chasing our tail here. I keep this computer in good shape, not very many programs installed. I use Revo Uninstaller quite often to uninstall things I don't use, as well as CCleaner. Virus scan everyday and don't download very often. Could this possibly be a hardware problem?

It seems it is always a string of BSOD at this point. I get one, then it restarts. I get another during restart. Then another, then another... Will keep updated. Thanks again for all the help so far.

Latest attached. Thanks.

Corrine · Aug 25, 2012

brittnic said:
I use Revo Uninstaller quite often to uninstall things I don't use, as well as CCleaner. Virus scan everyday and don't download very often.

It really isn't necessary to use Revo Uninstaller unless no other method works for removing a program. I've heard of too many instances where Revo has removed more than necessary. If you are using the registry cleaner portion of CCleaner, that too isn't necessary with Windows 7 unless you are having a problem caused by a left-over registry entry. The reason is that Windows is a closed source system. Developers of registry cleaners do not have the core code of Windows 7 and are not working on definitive information, but rather they are going on past knowledge and experience. Automatic cleaners will usually have to do some guesswork.

Modifying registry keys incorrectly can cause Windows instability, or make Windows unbootable. No registry cleaner is completely safe and the potential is ever present to cause more problems than they claim to fix. Registry cleaners cannot distinguish between good and bad. If you run a registry cleaner, it will delete all those keys which are obsolete and sitting idle; but in reality, those keys may well be needed by some programs or windows at a later time.

Windows 7 is much more efficient at managing the registry than previous Windows versions. Even if you are very knowledgeable of the registry, the few keys left over when uninstalling programs will not make 1 millisecond's difference in performance.

Forget all the "wisdom" you learned about XP. Windows 7 is not XP and does not manage the registry the same as XP.

brittnic · Aug 25, 2012

Corrine said:
brittnic said:

I use Revo Uninstaller quite often to uninstall things I don't use, as well as CCleaner. Virus scan everyday and don't download very often.

Click to expand...

It really isn't necessary to use Revo Uninstaller unless no other method works for removing a program. I've heard of too many instances where Revo has removed more than necessary. If you are using the registry cleaner portion of CCleaner, that too isn't necessary with Windows 7 unless you are having a problem caused by a left-over registry entry. The reason is that Windows is a closed source system. Developers of registry cleaners do not have the core code of Windows 7 and are not working on definitive information, but rather they are going on past knowledge and experience. Automatic cleaners will usually have to do some guesswork.

Modifying registry keys incorrectly can cause Windows instability, or make Windows unbootable. No registry cleaner is completely safe and the potential is ever present to cause more problems than they claim to fix. Registry cleaners cannot distinguish between good and bad. If you run a registry cleaner, it will delete all those keys which are obsolete and sitting idle; but in reality, those keys may well be needed by some programs or windows at a later time.

Windows 7 is much more efficient at managing the registry than previous Windows versions. Even if you are very knowledgeable of the registry, the few keys left over when uninstalling programs will not make 1 millisecond's difference in performance.

Forget all the "wisdom" you learned about XP. Windows 7 is not XP and does not manage the registry the same as XP.

Are you suggesting Revo or CCleaner are to blame for my current problems? I have used Revo successfully on other computers and had no problems using it with this one up until this point. I only installed CCleaner today after my latest resolution at the recommendation of a family member. I also uninstalled a Photoshop CS6 trial that had expired using Revo Uninstaller. I can try to system restore to a point prior to these actions, but given the fact that these problems precede its usage, I don't anticipate that to make a difference. Also, given that I get crashes in startup repair, safe mode, etc., loading a restore point may be an optimistic goal at this point.

Corrine · Aug 25, 2012

Hi, brittnic.

I just wanted to point out that it generally isn't necessary to use Revo when uninstalling software programs or the registry cleaner portion of CCleaner.

writhziden · Aug 26, 2012

Recommendations:

Since many of your crashes have been DirectX/graphics card related, proceed with the following: DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

If you are overclocking any hardware, please stop.
Run a system file check to check Windows for corruption:
1. Click Start Menu
2. Click All Programs
3. Click Accessories
4. Right click Command Prompt
5. Click Run as administrator
6. Type
  Code:
```
sfc /scannow
```
  and press Enter
7. Once it is complete, make note of the message. If it says Windows Resource Protection did not find any integrity violations., restart your computer and post back
8. If the message does not say Windows Resource Protection did not find any integrity violations., restart your computer and do steps 1-6 again.
9. You may need to do steps 1-6 up to three times with a restart in between each run to resolve all corrupted files.
10. If you still have corrupted files after a fourth run, post back here with the following:
  - Click Start Menu
  - Click Computer
  - Open your C: drive
  - Open Windows
  - Open Logs
  - Open CBS
  - Copy and paste CBS.log or CBS (it may not have the log extension) to a location you will remember.
  - Compress (zip) the CBS file and attach the .zip file to your next post.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

Download the drivers you want for your display card(s)
Click Start Menu
Click Control Panel
Click Uninstall a program
For NVIDIA:
- Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
- Restart your computer
- Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
- If any remain of the above, uninstall one at a time
- If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
For AMD:
- Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
- If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Expand Display adapters
  6. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  Alternatively:
  1. Login as an adminstrative user
  2. Click Start Menu
  3. Click Control Panel
  4. Click Hardware and Sound
  5. Click Device Manager (the last link under Devices and Printers)
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
    - Right click the adapter
    - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.

I would also recommend that you run some hardware checks:

If you are overclocking any hardware, please stop.
Run all but the advanced tests with SeaTools for HDDs.
SeaTools for Windows
SeaTools for DOS
FurMark Display Card Stress Test Steps:
1. First, download and install the latest version of FurMark from FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net.
2. Run FurMark as an administrator
3. Find your display resolution by right clicking the Desktop and clicking Screen resolution and enter it into FurMark's options:
4. Change FurMark's settings as in the image. You want to run it for 20 minutes or until it reaches the alarm temperature you set up. 90 is a good number for AMD display cards, 80 or 85 is probably best for NVIDIA cards. The best method to set the temperature alarm is the maximum temperature of your card minus 10 C. If you do not know the maximum temperature, and you cannot find it through a Google search, ask the people helping you to find it for you.
5. Run the Benchmark with user's settings and stop it once the temperature reaches a constant temperature, once the card reaches the alarm temperature, or once the video shows artifacts or strange colors.
Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
Prime95 Hardware Stress Testing Steps:
1. Download Prime95.
2. Navigate to where you saved the Prime95 files and unzip the files.
3. Open Prime95 from the list, and then click Run in the dialog box that opens.
4. Click Just Stress Testing
5. Run Small FFTs, In-place large FFTs, and Blend for a few hours each. Report back if CPU temperatures reach dangerous levels, if the system crashes, or if hardware errors are discovered by the diagnostics.
Run the boot version of Memtest86+. Let it run for at least 7-10 passes (preferably more) or until errors show up.

If you see even one error, stop the test and do the following:
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

Click to expand...
1. Shut down and turn off your computer.
2. Unplug all power sources to the system: unplug the power from the outlet/surge protector or PSU (then remove the battery if it is a laptop).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing (or remove the RAM panel if it is a laptop).
5. Remove all but one memory module making sure you are grounded while doing so.
  Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
6. Replace the casing (or replace the RAM panel if it is a laptop) and put the remaining memory module(s) in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).
Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.
Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. You may want to run both Memtest86+ and the Windows Memory Diagnostics Tool overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. Any drivers in red should be updated/replaced/removed. You can find links to the driver information and where to update the drivers in the section after the code box:

Code:

**************************Sat Aug 25 13:23:58.750 2012 (UTC - 6:00)**************************
regi.sys                    Mon Apr 16 09:19:10 2007 (462393EE)
[COLOR=RED][B]SFEP.sys                    Thu Aug  2 23:35:53 2007 (46B2BEB9)[/B][/COLOR]
yk62x64.sys                 Mon Feb 23 08:02:27 2009 (49A2BA83)
btwl2cap.sys                Fri Apr  3 18:28:45 2009 (49D6A9BD)
GEARAspiWDM.sys             Mon May 18 06:17:04 2009 (4A1151C0)
ArcSoftKsUFilter.sys        Mon May 25 02:27:31 2009 (4A1A5673)
iaStor.sys                  Thu Jun  4 19:53:40 2009 (4A287AA4)
rimssn64.sys                Wed Jun 10 20:22:31 2009 (4A306A67)
risdsn64.sys                Thu Jun 11 21:49:37 2009 (4A31D051)
Apfiltr.sys                 Tue Jun 16 16:09:26 2009 (4A381816)
btwavdt.sys                 Wed Jun 24 23:50:13 2009 (4A431015)
btwrchid.sys                Wed Jun 24 23:51:37 2009 (4A431069)
btwaudio.sys                Wed Jul  1 07:54:56 2009 (4A4B6AB0)
RTKVHD64.sys                Thu Jul  2 03:42:36 2009 (4A4C810C)
intelppm.sys                Mon Jul 13 17:19:25 2009 (4A5BC0FD)
RtHDMIVX.sys                Thu Jul 16 21:52:36 2009 (4A5FF584)
sptd.sys                    Sun Oct 11 14:55:14 2009 (4AD24632)
PxHlpa64.sys                Tue Oct 20 12:08:42 2009 (4ADDFCAA)
amdxata.sys                 Fri Mar 19 10:18:18 2010 (4BA3A3CA)
avgidsdrivera.sys           Fri Dec 23 05:05:21 2011 (4EF46E81)
avgidsfiltera.sys           Fri Dec 23 05:05:40 2011 (4EF46E94)
avgmfx64.sys                Fri Dec 23 05:08:12 2011 (4EF46F2C)
NETwNs64.sys                Mon Jan 23 15:44:07 2012 (4F1DE2B7)
avgrkx64.sys                Mon Jan 30 20:11:41 2012 (4F275BED)
avgldx64.sys                Tue Feb 21 20:57:53 2012 (4F4467C1)
avgtdia.sys                 Sun Mar 18 21:53:32 2012 (4F66ADBC)
avgidsha.sys                Wed Apr 18 20:19:15 2012 (4F8F7623)
atikmpag.sys                Tue Jul  3 23:10:55 2012 (4FF3D05F)
atikmdag.sys                Tue Jul  3 23:16:13 2012 (4FF3D19D)

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

**************************Sat Aug 25 13:23:58.750 2012 (UTC - 6:00)**************************
Loading Dump File [C:\Users\BSODAnalyst\Downloads\brittnic\082512-37097-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:01:28.498[/B]
BugCheck Code: [B]BugCheck FC, {fffff88001002a14, 8000000003c27121, fffff88008c973e0, 2}[/B]
Probably caused by :[B]hardware ( BATTC!BatteryClassStatusNotify+1a0c )[/B]
BugCheck Info: [B]ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME: [B]WerFault.exe[/B]
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED_BATTC.SYS[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed:[B]2193[/B]
  BIOS Version                  R4070Y0
  BIOS Release Date             09/04/2009
  Manufacturer                  Sony Corporation
  Product Name                  VGNFW590F3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 25 13:15:37.133 2012 (UTC - 6:00)**************************
Loading Dump File [C:\Users\BSODAnalyst\Downloads\brittnic\082512-53523-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:01:22.789[/B]
BugCheck Code: [B]BugCheck 1E, {ffffffffc0000005, fffff88001da7ac9, 0, 4920344c}[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]hardware ( rdyboost!SmdStoreReadCompletion+161 )[/B]
BugCheck Info: [B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B]
BUGCHECK_STR:  0x1e_c0000005
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED_rdyboost.sys[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed:[B]2194[/B]
  BIOS Version                  R4070Y0
  BIOS Release Date             09/04/2009
  Manufacturer                  Sony Corporation
  Product Name                  VGNFW590F3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Aug 25 13:07:12.985 2012 (UTC - 6:00)**************************
Loading Dump File [C:\Users\BSODAnalyst\Downloads\brittnic\082512-35100-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 3:32:00.045[/B]
BugCheck Code: [B]BugCheck 50, {fffff3000e20f2e8, 1, fffff88003e238e5, 7}[/B]
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::xWaitOnDMAReferences+5 )[/B]
BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME: [B]dwm.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_dxgmms1!VIDMM_GLOBAL::xWaitOnDMAReferences+5[/B]
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz"
MaxSpeed:     2200
CurrentSpeed:[B]2194[/B]
  BIOS Version                  R4070Y0
  BIOS Release Date             09/04/2009
  Manufacturer                  Sony Corporation
  Product Name                  VGNFW590F3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Member

Attachments

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Administrator, .NET/UWP Developer

Member

Administrator, .NET/UWP Developer

Member

Attachments

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Attachments

Administrator, .NET/UWP Developer

Member

Attachments

Administrator, .NET/UWP Developer

Member

Member

Member

Attachments

Administrator, Microsoft MVP, Security Analyst

Member

Administrator, Microsoft MVP, Security Analyst

Administrator, .NET/UWP Developer

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Administrator,
Microsoft MVP,
Security Analyst

Administrator,
Microsoft MVP,
Security Analyst