Constant BSOD Crashes Win 8.1 x64


Posts: 6   +0
So I have been getting pretty constant crashes on my Windows 8 Desktop. It is a custom build AMD FX-8320E 8-Core. AMD R9 270x Video Card and 6gb ram. All component listed are new as of Feb 2015. My HDDs are older but still in good working order according to the diagnostics I have run on them via HDTune and WinDFT. MemTest 86+ shows no errors on a repeating overnight scan as well.

I have enabled driver verifier and trying to analyze my .dmp files is proving fruitless as I get notice of a generic driver and nothing specific.

I have gone as far as doing a complete deep format of my HDDs and a fresh install of windows 8(I did reinstall when I upgraded the Mobo and Processor in Feb without a full wipe).

Now on to the crashes. I can leave the PC running all day for days at a time with no issues. I only get crashes when playing games. I primarily play Final Fantasy 14 but it happens in all games from Skyrim to Call of Duty. I will be playing and all of a sudden the system will freeze and hard lock or it will just reboot. Occasionally it will BSOD and generate a DMP stating IRQ not less than or equal listing the game I am playing as the offending process. I enabled driver verifier under advice from a friend and now the dmp files state as follows.

* *
* Bugcheck Analysis *
* *

The IO manager has caught a misbehaving driver.
Arg1: 000000000000021f, A driver has not filled out a dispatch routine for a required IRP major function.
Arg2: fffff8008aa9b934, The address in the driver's code where the error was detected.
Arg3: ffffcf801c9ecdc0, IRP address.
Arg4: 0000000000000000

Debugging Details:

BUGCHECK_STR: 0xc9_21f


fffff800`8aa9b934 4883ec38 sub rsp,38h

fffff800`8aa9b934 4883ec38 sub rsp,38h

IRP_ADDRESS: ffffcf801c9ecdc0

DEVICE_OBJECT: ffffe0006a182040

DRIVER_OBJECT: ffffe00069c301a0

IMAGE_NAME: ntkrnlmp.exe


MODULE_NAME: ntkrnlmp

FAULTING_MODULE: 0000000000000000




ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LOCK_ADDRESS: fffff8008a6ea220 -- (!locks fffff8008a6ea220)

Resource @ nt!PiEngineLock (0xfffff8008a6ea220) Exclusively owned
Contention Count = 1
NumberOfExclusiveWaiters = 1
Threads: ffffe00068a1e880-01<*>
Threads Waiting On Exclusive Access:

1 total locks, 1 locks currently held

Lock address : 0xfffff8008a6ea220
Thread Count : 1
Thread address: 0xffffe00068a1e880
Thread wait : 0x34b

LAST_CONTROL_TRANSFER: from fffff8008aa8b6b0 to fffff8008a556ca0

ffffd000`47119128 fffff800`8aa8b6b0 : 00000000`000000c9 00000000`0000021f fffff800`8aa9b934 ffffcf80`1c9ecdc0 : nt!KeBugCheckEx
ffffd000`47119130 fffff800`8aa8e171 : fffff800`8aa7e470 fffff800`8aa9b934 ffffcf80`1c9ecdc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`47119170 fffff800`8aa9772e : ffffcf80`1c9ecdc0 00000000`0000021f fffff800`8aa9b934 00000000`00000000 : nt!ViErrorFinishReport+0x10d
ffffd000`471191d0 fffff800`8aa8dc6b : ffffd000`471192d8 ffffe000`6a182040 ffffe000`69c3c1c8 ffffe000`6a15b5f0 : nt!VfWmiVerifyIrpStackDownward+0xfe
ffffd000`47119270 fffff800`8aa847dd : ffffe000`6a15b5f0 ffffd000`471193d0 ffffcf80`1c9ecdc0 ffffe000`69c3c1c8 : nt!VfMajorVerifyIrpStackDownward+0x83
ffffd000`471192d0 fffff800`8aa8ad59 : ffffcf80`1c9ecdc0 00000000`00000000 ffffe000`6a15b5f0 ffffe000`69f4cf40 : nt!IovpCallDriver1+0x5e5
ffffd000`47119420 fffff800`8aa7f88c : ffffcf80`1c9ecdc0 00000000`00000002 00000000`00000000 00000000`00000000 : nt!VfBeforeCallDriver+0x165
ffffd000`47119450 fffff800`8aa9bec9 : ffffcf80`1c9ecdc0 ffffe000`6a182040 00000000`00000002 ffffe000`69f4cf40 : nt!IovCallDriver+0x348
ffffd000`471194a0 fffff800`8aa7f911 : ffffe000`6a182190 ffffcf80`1c9ecdc0 00000000`00000000 fffff800`8aa8b471 : nt!ViFilterDispatchGeneric+0xd1
ffffd000`471194e0 fffff800`8aa8b3d6 : ffffcf80`1c9ecdc0 ffffe000`6a182040 00000000`00000000 ffffe000`69f98f40 : nt!IovCallDriver+0x3cd
ffffd000`47119530 fffff800`8aa97626 : ffffe000`67a5c680 ffffd000`471196e9 00000000`00000001 ffffe000`67a5c680 : nt!VfIrpSendSynchronousIrp+0x11e
ffffd000`471195a0 fffff800`8aa8db56 : 00000000`00000000 ffffd000`471196e9 00000000`00000001 ffffe000`67a5c680 : nt!VfWmiTestStartedPdoStack+0x5a
ffffd000`47119640 fffff800`8a876ea8 : 00000000`00000000 ffffd000`471196e9 00000000`00000001 ffffd000`471196e9 : nt!VfMajorTestStartedPdoStack+0x56
ffffd000`47119670 fffff800`8a7f4e53 : ffffe000`67a5c350 ffffd000`00000001 00000000`00000000 00000000`00000000 : nt!PipProcessStartPhase3+0xb8
ffffd000`47119750 fffff800`8a91ed9f : 00000000`00000000 00000000`00000001 00000000`00000000 fffff800`8a7f9bd6 : nt!PipProcessDevNodeTree+0x377
ffffd000`471199d0 fffff800`8a4e2ba8 : 00000001`00000003 00000000`00000000 ffffe000`68a1e880 ffffe000`68a1e9c0 : nt!PiProcessStartSystemDevices+0x87
ffffd000`47119a20 fffff800`8a4b36bc : fffff800`8a4e27ec fffff800`8a6e8c40 ffffe000`68a1e880 fffff800`0000001a : nt!PnpDeviceActionWorker+0x3bc
ffffd000`47119ad0 fffff800`8a50636c : ffffd000`4697c3c0 ffffe000`68a1e880 00000000`00000080 ffffe000`68a1e880 : nt!ExpWorkerThread+0x28c
ffffd000`47119b80 fffff800`8a55d2c6 : ffffd000`46970180 ffffe000`68a1e880 ffffd000`4697c3c0 00400032`00012844 : nt!PspSystemThreadStartup+0x58
ffffd000`47119be0 00000000`00000000 : ffffd000`4711a000 ffffd000`47113000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16




FAILURE_BUCKET_ID: 0xc9_21f_VRF_IMAGE_ntkrnlmp.exe

BUCKET_ID: 0xc9_21f_VRF_IMAGE_ntkrnlmp.exe


FAILURE_ID_HASH_STRING: km:0xc9_21f_vrf_image_ntkrnlmp.exe

FAILURE_ID_HASH: {5a228496-4783-786f-0c91-da54c2fb2ecf}

Followup: MachineOwner

I am having a hard time finding the offending driver. Any advice or tips would be greatly appreciated as I am at my wits end with this computer.


Posts: 17,233   +234
Lets see if the actual minidumps show us anything more. Go to C:\Windows\minidump and select all the .dmp files. Right-click sending these .dmp files to a compressed(zipped)folder. Upload this folder as a file here...


Posts: 6   +0
Here is the entire folder zipped, do you need memory.dmp as well? I have the most recent one still.


  • minidump
    113.2 KB · Views: 2


Posts: 17,233   +234
The minidumps and what you posted here are pointing to a boot drive problem. What is the C drive's make and model?


Posts: 6   +0
It is a Western Digital 160gb
WDC WD1600bevs-08vat2

I also have a couple other drives as well, another western digital 600gb and a hitachi 1tb


Posts: 17,233   +234
What color is the 160's label? Green, blue? This drive may be just about full, not to mention old. How much free space is left?


Posts: 6   +0
It is a Western Digital Scorpio Blue. Free space is listed at 68.1gb free out of 149 available. The label shows it's manufacture date is October 22, 2009 so almost 6 years old now.


Posts: 17,233   +234
I would suggest that you replace it with one of the other drives as it could be the cause of all this...


Posts: 6   +0
I can do that, my other 2 drives have plenty of space available on them, should I use an imaging software clone my drive, or just a fresh install of windows? If so what software would you recommend.


Posts: 17,233   +234
You could partition another drive that contains some data already and use that partition to install Windows fresh


Posts: 6   +0
Alright thanks for all your help. I will get that done this evening and I will buy a New HDD as well seeing as all of mine are fairly old to try and prevent this in the future. Thanks again.