Navigation section

Windows 7 Troubleshooting BSOD: IRQL_NOT_LESS_OR_EQUAL (0x0000000a) on Unexpected Shutdown

ParalysedBeaver

ParalysedBeaver

New Member
Joined
Feb 6, 2013
Messages
36
Not sure what was running as I wasn't at the PC at the time. When I came back, I found it had recovered from an unexpected shutdown. Bluescreenview confirmed it was a BSOD IRQL_NOT_LESS_OR_EQUAL 0x0000000a. I have attached the files as requested.

Link Removed
 

Solution
usasma
You can uninstall the wireless receiver's programs from Control Panel...Programs and Features...Uninstall a program.

If your chipset drivers are a problem, you'll see errors in Device Manager (devmgmt.msc)
Alternatively, you can run MSINFO32.exe and check the Components...Problem Devices category

Just FYI - your chipset is: AMD® 770 and SB710 Chipset
Downloads are available here: Link Removed
It won't hurt if you update them, but hold off until we see if the BSOD's recur.
Sort by date Sort by votes
Don't worry about it for now. It may become an issue if the BSOD's continue - but I suspect that the MSI Afterburner is the true cause. I only suspect the wireless driver because it is older.
 

Upvote 0 Downvote
Still getting blue screens. I've included the latest 2 dmp files (IRQL_NOT_LESS_OR_EQUAL and BAD_POOL_CALLER). I ran the SeaTools for DOS long test, no errors. Memtest 86+ on each of my 2 sticks individually in both slots for 4 passes, no errors. Furmark Burn-in test on default settings 1024x576 for 20 mins, it rose to around 80 then hovered around 80 - 85.Link Removed
 

Upvote 0 Downvote
This one blames video. Please follow these instructions to update the video driver only: ATI video cards - DRIVER ONLY installation procedure

Once that's done - if the BSOD's recur, please run Driver Verifier according to these instructions: Link Removed


Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

bcmwl664.sys Tue Jul 7 20:45:04 2009 (4A53EC10)
Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card
Link Removed



Analysis:
The following is for informational purposes only.
Code: 
[FONT=lucida console]**************************Sat Mar  2 11:07:52.516 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030213-18205-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:13:44.687[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )[/B]
BugCheck [B]A, {0, 2, 1, fffff80002e81830}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e81830, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  SABnzbd.exe
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiProcessExpiredTimerList+110[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Mar  1 12:29:39.575 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030113-18844-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:20:09.120[/B]
Probably caused by :[B]dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+b6 )[/B]
BugCheck [B]C2, {7, 109b, 40e95e0, fffffa8006e831f0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 00000000040e95e0, Memory contents of the pool block
Arg4: fffffa8006e831f0, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: [B]X64_0xc2_7_dxgmms1!DXGFASTMUTEX::_scalar_deleting_destructor_+b6[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: 
[FONT=lucida console]**************************Sat Mar  2 11:07:52.516 2013 (UTC - 5:00)**************************
[B]bcmwl664.sys                Tue Jul  7 20:45:04 2009 (4A53EC10)[/B]
AtiPcie64.sys               Wed Mar 10 09:33:45 2010 (4B97ADC9)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nusb3hub.sys                Thu Feb 10 00:52:32 2011 (4D537D20)
nusb3xhc.sys                Thu Feb 10 00:52:33 2011 (4D537D21)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
Rt64win7.sys                Tue Jun 12 10:00:29 2012 (4FD74B7D)
mbam.sys                    Mon Aug 20 12:49:41 2012 (50326AA5)
MpFilter.sys                Wed Oct 31 18:43:06 2012 (5091A97A)
RTKVHD64.sys                Tue Dec  4 08:28:37 2012 (50BDFA85)
atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
[/FONT]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 

Upvote 0 Downvote
I think I've finally removed all traces of the CCC, as there was a setting in there that was to do with overscan, and filled the picture to the edge of my monitor through HDMI. Now, that's gone, there is a one inch black border around it all that I can't seem to get rid of.
 

Upvote 0 Downvote
I'd suggest temporarily leaving the black border alone. Once we see if that fixes the problems, then we can work on fixing the black border thing.

In most cases I suggest waiting a week to see if the BSOD's have stopped before thinking that it's "fixed".
Then I suggest waiting another week before deciding that it's "fixed".
 

Upvote 0 Downvote
No luck, blue screened again. Tried running driver verifier. It crashed 3 times to the screen I showed before.Link Removed
 

Upvote 0 Downvote
Yes, that would be the best thing at this point.
I'm starting to wonder about hardware issues/compatibility issues at this point (but these most recent errors tend to point to software/drivers).
Start by running these free hardware diagnostics: Link Removed

Analysis:
The following is for informational purposes only.
Code: 
[font=lucida console]**************************Mon Mar  4 12:26:15.795 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030413-19718-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:01:57.341[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiDeliverApc+126 )[/B]
BugCheck [B]3B, {c0000005, fffff80002e6d5b6, fffff88002726050, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e6d5b6, Address of the instruction which caused the bugcheck
Arg3: fffff88002726050, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  steam.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!KiDeliverApc+126[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar  4 12:23:38.224 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030413-20046-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:23:17.395[/B]
Probably caused by :[B]win32k.sys ( win32k!memset+70cf )[/B]
BugCheck [B]3B, {c0000005, fffff960000fcadf, fffff88008af71c0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000fcadf, Address of the instruction which caused the bugcheck
Arg3: fffff88008af71c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  steam.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_win32k!memset+70cf[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: 
[font=lucida console]**************************Mon Mar  4 12:26:15.795 2013 (UTC - 5:00)**************************
[B]bcmwl664.sys                Tue Jul  7 20:45:04 2009 (4A53EC10)[/B]
AtiPcie64.sys               Wed Mar 10 09:33:45 2010 (4B97ADC9)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nusb3hub.sys                Thu Feb 10 00:52:32 2011 (4D537D20)
nusb3xhc.sys                Thu Feb 10 00:52:33 2011 (4D537D21)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
Rt64win7.sys                Tue Jun 12 10:00:29 2012 (4FD74B7D)
mbam.sys                    Mon Aug 20 12:49:41 2012 (50326AA5)
MpFilter.sys                Wed Oct 31 18:43:06 2012 (5091A97A)
RTKVHD64.sys                Tue Dec  4 08:28:37 2012 (50BDFA85)
atikmpag.sys                Tue Feb 26 12:58:05 2013 (512CF7AD)
atikmdag.sys                Tue Feb 26 14:11:23 2013 (512D08DB)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 

Upvote 0 Downvote
I just finished running the Prime95 test. I did the blend test with 4 torture test threads. The CPU started at around 40 and finished 1 test in a minute but was pushing 85 degrees so I stopped it.
 

Upvote 0 Downvote
Time to look at the cooling solution for your CPU. Use anti-static precautions before touching anything inside the case!
Check to make sure that:
- there's thermal compound between the cooler and the CPU
- that the cooler is clear of dust/dirt/hairballs
- that the fan is working
- that there is plenty of room for cooler air to get at the CPU cooler
 

Upvote 0 Downvote
Think you might be right. My brother has the same CPU and MB as me, but an aftermarket CPU cooler. I got him to run the same test. Started at around 30 and the hovered at 50, going no higher.
 

Upvote 0 Downvote
I have reseated the cpu with a fresh application of thermal paste. When I took the cpu cooler off, there was hardly any left on the cpu and a lot on the heatsink. Cleaned it off the two of them, and reapplied it. A blob in the center.
Since I'm running low on space for attachments here, I uploaded today's crashes to an offsite hoster. Link Removed
 

Upvote 0 Downvote
I'm assuming that the potential hardware problems were fixed by the application of thermal paste. Did you perform another stress test with Prime95?

Since I assumed that the hardware problems were fixed by the thermal paste - yet you're still having BSOD's.
And the BSOD's are of a type that usually responds well to the user of Driver Verifier - Please run Driver Verifier according to these instructions again: Link Removed If possible, let Driver Verifier crash the system at least 3 times.

Possible results:
- No BSOD - probably a hardware problem, but Windows drivers are also a possible cause..
- BSOD's that blame one thing (a 3rd party driver) - most likely the cause
- BSOD's that blame one thing (not a 3rd party driver) - - probably a hardware problem, but Windows drivers are also a possible cause.
- BSOD's that blame several things- probably a hardware problem.


Analysis:
The following is for informational purposes only.
Code: 
[font=lucida console]**************************Tue Mar  5 15:41:17.654 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-24336-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 1:14:09.200[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff80002ec12bb, fffff88003316908, fffff88003316160}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ec12bb, The address that the exception occurred at
Arg3: fffff88003316908, Exception Record Address
Arg4: fffff88003316160, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]X64_0x7E_nt!ExpScanGeneralLookasideList+a0[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 14:26:33.963 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-18080-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 1:53:34.134[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiDeliverApc+187 )[/B]
BugCheck [B]A, {1280, 2, 1, fffff80002ec1617}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000001280, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ec1617, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiDeliverApc+187[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 02:22:48.941 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-29983-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 6:19:37.486[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!IoCancelIrp+5a )[/B]
BugCheck [B]A, {2c, 2, 0, fffff80002e2869a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 000000000000002c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e2869a, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID: [B]X64_0xA_nt!IoCancelIrp+5a[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar  4 20:02:37.432 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-32588-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:03:59.977[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiDeliverApc+129 )[/B]
BugCheck [B]A, {7000000008, 2, 1, fffff80002ec15b9}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000007000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ec15b9, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  SABnzbd.exe
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiDeliverApc+129[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar  4 19:27:45.458 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-22417-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:03:25.003[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!CcFlushCache+15d )[/B]
BugCheck [B]A, {18, 2, 0, fffff80002eb941d}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002eb941d, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xA_nt!CcFlushCache+15d[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar  4 19:23:43.820 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-18158-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 0:18:19.366[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+36c0e )[/B]
BugCheck [B]A, {1b5200000008, 6, 1, fffff80002eb6ee6}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00001b5200000008, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002eb6ee6, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xA_atikmdag+36c0e[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar  4 19:04:49.892 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-17799-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 1:51:26.437[/B]
Probably caused by :[B]USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+86f )[/B]
BugCheck [B]A, {fffff68030803400, 2, 1, fffff80002e95109}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff68030803400, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e95109, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID: [B]X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+86f[/B]
  BIOS Version                  V17.7
  BIOS Release Date             09/09/2010
  Manufacturer                  MSI
  Product Name                  MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code: 
[font=lucida console]**************************Tue Mar  5 15:41:17.654 2013 (UTC - 5:00)**************************
AtiPcie64.sys               Wed Mar 10 09:33:45 2010 (4B97ADC9)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
[B]nusb3hub.sys                Thu Feb 10 00:52:32 2011 (4D537D20)[/B]
[B]nusb3xhc.sys                Thu Feb 10 00:52:33 2011 (4D537D21)[/B]
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
Rt64win7.sys                Tue Jun 12 10:00:29 2012 (4FD74B7D)
mbam.sys                    Mon Aug 20 12:49:41 2012 (50326AA5)
MpFilter.sys                Wed Oct 31 18:43:06 2012 (5091A97A)
RTKVHD64.sys                Tue Dec  4 08:28:37 2012 (50BDFA85)
atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Mar  5 02:22:48.941 2013 (UTC - 5:00)**************************
[B]bcmwl664.sys                Tue Jul  7 20:45:04 2009 (4A53EC10)[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar  4 19:27:45.458 2013 (UTC - 5:00)**************************
atikmpag.sys                Tue Feb 26 12:58:05 2013 (512CF7AD)
atikmdag.sys                Tue Feb 26 14:11:23 2013 (512D08DB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Mar  4 19:23:43.820 2013 (UTC - 5:00)**************************
cpuz136_x64.sys             Sat Oct 27 13:24:41 2012 (508C18D9)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 

Last edited:
Upvote 0 Downvote
It's been 3 days since the last BSOD, so I haven't run driver verifier yet. If I do blue screen again though, I will run it.
 

Upvote 0 Downvote
No BSOD's in a week.
 

Upvote 0 Downvote
Glad to hear it! Give it another week and it's probably fixed!
 

Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

ChatGPT
  • Featured
  • Article Article
July 2025 Windows Server 2025 Update Crashes AMD EPYC DL325 with IRQL_NOT_LESS_OR_EQUAL
Replies
0
Views
260
ChatGPT
ChatGPT
ChatGPT
  • Featured
  • Article Article
Ultimate Guide to Troubleshooting Windows Unexpected Restarts & BSOD Errors
Replies
0
Views
310
ChatGPT
ChatGPT
T
  • Solved
Windows 7 Resolving BSOD: IRQL_NOT_LESS_OR_EQUAL Caused by halmacpi.dll on Lenovo X240
Replies
7
Views
5K
kemical
kemical
V
  • Solved
Windows 7 BSOD IRQL_NOT_LESS_OR_EQUAL, iTunes the Problem?
Replies
1
Views
3K
usasma
usasma
W
  • Solved
Windows 8 2 identical PCs, 1 is unstable (IRQL_NOT_LESS_OR_EQUAL)
Replies
15
Views
6K
Winterseed
W
Back
Top