Please help me with this

I have the attachments necessary to find out what caused this blue screen.

Thanks for the help, it's greatly appreciated.


Fantastic Member
Microsoft Community Contributor
Please ensure that you check to see if you have all Windows Updates.

MSINFO32 shows memory dumps blaming iaStor.sys and some video.
The one uploaded memory dump doesn't show any conclusive evidence of a faulting driver

As such, I suspect that this is a hardware problem.
Please start with these free, bootable diagnostics: Initial Hardware Diagnostics
If they don't find anything, then continue with these (also free): Additional Hardware Diagnostics

There is a possiblility that this is a driver issue though (STOP 0xA errors are mostly driver related), so please run Driver Verifier according to these instructions:

Good luck!

The following is for informational purposes only.
[FONT=lucida console]**************************Sun Dec  2 11:47:37.327 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120212-29484-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 1:58:46.029[/B]
Probably caused by :[B]memory_corruption ( nt!MmPurgeSection+4eb )[/B]
BugCheck [B]A, {68003247c60, 2, 1, fffff800034982fb}[/B]
BugCheck Info: [URL=""]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
Arg1: 0000068003247c60, 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: fffff800034982fb, address which referenced memory
PROCESS_NAME: [B]chrome.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_nt!MmPurgeSection+4eb[/B]
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3510[/B]
  BIOS Version                  1206
  BIOS Release Date             06/05/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
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.
[FONT=lucida console]**************************Sun Dec  2 11:47:37.327 2012 (UTC - 5:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
CLBUDF.SYS                  Thu Jul 15 06:05:36 2010 (4C3EDD70)
CLBStor.sys                 Thu Jul 15 06:05:41 2010 (4C3EDD75)
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
ICCWDT.sys                  Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys                    Mon Aug 23 21:53:02 2010 (4C7325FE)
rikvm_38F51D56.sys          Fri Oct 29 06:52:09 2010 (4CCAA759)
bcmvwl64.sys                Mon Nov 22 08:58:19 2010 (4CEA76FB)
btwl2cap.sys                Fri Feb 11 20:06:04 2011 (4D55DCFC)
btwdpan.sys                 Mon May 16 10:58:06 2011 (4DD13B7E)
CORSGKB.sys                 Mon Jun 20 22:38:24 2011 (4E000420)
btwavdt.sys                 Thu Jun 23 10:53:33 2011 (4E03536D)
btwrchid.sys                Thu Jun 23 10:56:51 2011 (4E035433)
btwaudio.sys                Wed Jul  6 18:39:13 2011 (4E14E411)
BCM42RLY.sys                Tue Jul 19 23:22:48 2011 (4E264A08)
nusb3hub.sys                Wed Jul 27 20:20:04 2011 (4E30AB34)
nusb3xhc.sys                Wed Jul 27 20:20:06 2011 (4E30AB36)
btwampfl.sys                Tue Sep 20 13:14:26 2011 (4E78C9F2)
Rt64win7.sys                Tue Sep 27 10:50:33 2011 (4E81E2B9)
PxHlpa64.sys                Mon Oct 17 10:29:34 2011 (4E9C3BCE)
bcbtums.sys                 Tue Oct 18 14:37:25 2011 (4E9DC765)
bcmwl664.sys                Wed Oct 26 22:45:09 2011 (4EA8C5B5)
asmtxhci.sys                Wed Nov  2 23:00:22 2011 (4EB203C6)
asmthub3.sys                Wed Nov  2 23:00:32 2011 (4EB203D0)
mv91cons.sys                Mon Nov  7 03:51:20 2011 (4EB79C08)
mvxxmm.sys                  Mon Nov  7 03:58:34 2011 (4EB79DBA)
mvs91xx.sys                 Mon Nov  7 03:58:49 2011 (4EB79DC9)
avgidsdrivera.sys           Fri Dec 23 07:05:21 2011 (4EF46E81)
avgidsfiltera.sys           Fri Dec 23 07:05:40 2011 (4EF46E94)
avgmfx64.sys                Fri Dec 23 07:08:12 2011 (4EF46F2C)
asahci64.sys                Thu Jan  5 00:08:19 2012 (4F053043)
iusb3hub.sys                Thu Jan  5 06:54:43 2012 (4F058F83)
iusb3xhc.sys                Thu Jan  5 06:54:45 2012 (4F058F85)
iusb3hcs.sys                Thu Jan  5 06:56:40 2012 (4F058FF8)
avgrkx64.sys                Mon Jan 30 22:11:41 2012 (4F275BED)
iaStor.sys                  Wed Feb  1 19:15:24 2012 (4F29D59C)
LGSHidFilt.Sys              Tue Feb  7 08:12:39 2012 (4F312347)
cbfs3.sys                   Mon Apr  9 09:21:46 2012 (4F82E26A)
avgidsha.sys                Wed Apr 18 22:19:15 2012 (4F8F7623)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
RTKVHD64.sys                Tue Jun 19 04:50:56 2012 (4FE03D70)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
avgldx64.sys                Wed Jul 25 20:56:48 2012 (501095D0)
e1c62x64.sys                Fri Aug 10 18:44:15 2012 (50258EBF)
avgtdia.sys                 Fri Aug 24 09:20:13 2012 (50377F8D)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)

Last edited:
I did all the stress tests just like the website said to, and everything came out good.
It can't be drivers since all the drivers are installed and up to date, and so is windows.
Could it be my hard drive, or did windows have a dodgy installation.
It may be my motherboard, since there aren't that many things that could be causing it.
My hard drive is a WD Black 1TB.
My Motherboard: Asus P8Z77-V Deluxe

Please respond.

Thank you very much.



Fantastic Member
Microsoft Community Contributor
If you've completed all the stress/hardware tests, then that rules out a lot of hardware - but not all of it.
If you've completed all the stress/hardware tests, then the hard drive isn't a likely problem as it was the first test that was suggested. What hard drive test did you use, and what results did you get?

It can be drivers since not all of the drivers are up to date (see the dates on the drivers in the previous post)
But, it's not just older drivers that are a problem - drivers can become corrupted and can cause problems.
Please run Driver Verifier as I requested - and it may just confirm that this isn't a 3rd party driver problem.

With memory dumps we fix things in this order (from most likely to least likely)
- 3rd party (non-Windows) drivers (most likely)
- hardware
- Windows drivers (least likely)

Also, it's very difficult to draw conclusions from just one memory dump. It usually takes me 4 or 5 memory dumps before I'll commit to calling an error a hardware error (and only after fixing all 3rd party driver suspects).

And "hardware errors" are usually one of the following types of errors:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

Please note that these "hardware" issues are, in some cases, actually caused by drivers. That further complicates the analysis! :(

The hardware stress tests/diagnostics aren't 100% accurate either. But after running the tests we suspect that the hard drive, the memory (RAM, mobo, and CPU), the video card(s), and the CPU are OK, and that the system is malware free - and we operate on that assumption until other evidence either confirms or refutes that conclusion.

Further hardware troubleshooting revolves around removing the parts that we haven't tested. And, if the parts are essential, then you'll have to find replacements that are known to be good in order to test those components. If you don't have similar hardware laying around to test with, then this can get rather expensive (I usually suggest buying stuff from a shop that will take returns)!

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.