Getting a BSOD related to ntoskrnl.exe fairly often

[Reyjakai]

I've been getting this BSOD for about a month now, maybe a bit longer. Some days it's fine, other days it'll crash several times per day. I'm not sure if this is related, but recently I've been getting lag time on my restart. It'll take ~15 seconds after windows 7 starts up where it will hang on a black screen before letting me do anything. Normally this is instantaneous.

I've noticed it most when I'm playing video games, specifically on the BYOND engine, but I'm not sure that's the cause. I'm not terribly opposed to doing an OSRI, but I'd like to avoid it if at all possible.

I should mention that I recently upgraded my video card, motherboard, and graphics card, all of which shouldn't be causing problems. These problem didn't happen at all prior to the upgrade, though, so it could be a problem with the new drivers. Not 100% sure. Thanks.

 

[Laith]

Hiya and welcome to SevenForums!rb:

BugCheck 3B, {c0000005, fffff80002dfc9cc, fffff8800aaa8ed0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption

BugCheck 1E, {ffffffffc0000005, fffff88003044fb0, 0, 0}

Unable to load image bflwfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bflwfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
Probably caused by : bflwfx64.sys ( bflwfx64+f4eb )

BugCheck 3B, {c0000005, 20802068, fffff8800a1f7ba0, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1e1d55 )

BugCheck 18, {fffffa800c767f30, fffffa801068eb50, 1, 1000000000000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4874a )

BugCheck 1E, {0, 0, 0, 0}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )

BugCheck 3B, {c0000005, fffff880016343dd, fffff8800bc378b0, 0}

Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+24f )

BugCheck 50, {fffff260c0ac58f0, 0, fffff960000cde00, 7}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption

BugCheck 3B, {c0000005, fffff80002c6cf37, fffff8800975bc10, 0}

Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+2c7 )

BugCheck 3B, {c0000005, fffff9600016e912, fffff8800d470080, 0}

Probably caused by : win32k.sys ( win32k!DWP_GetEnabledPopup+3e )

Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html


Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run MemTest86+, it must be MemTest86+ for 8 passes. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Update your DirectX drivers.

Update your Bigfoot Networks Bandwidth Control Wireless NDIS Light Weight Filter driver.

 

[Reyjakai]

Alrighty, I used DDU to uninstall my video card drivers and reinstalled them, ran system file checker and chkdsk, both of which were fine. I ran memtest86+ for 8 passes, roughly 16 hours, couldn't update my directx drivers as they're already up to date, and I installed the Killer network suite, which should fix the Bigfoot Networks Bandwidth Control Wireless NDIS Lightweight Filter driver issue. Time to see if this works.

 

[Laith]

Okay.

 

[Reyjakai]

Just got another one today.

Edit: Make that two within an hour.

 

[Laith]

Hmm,

BugCheck 3B, {c0000005, fffff960001053f1, fffff8800a261f50, 0}

Probably caused by : win32k.sys ( win32k!GreGetBounds+6d )

BugCheck 3B, {c0000005, fffff80002cce416, fffff8800cbfee50, 0}

Probably caused by : memory_corruption

Followup: memory_corruption

Still memory corruption, did MemTest86+ pass?

 

[Reyjakai]

Yeah, I ran it for 8 passes without any errors.

 

[Laith]

Was it MemTest86+ or MemTest86?

 

[Reyjakai]

It was Memtest86+. Version 5.01, the one from Memtest86+ - Advanced Memory Diagnostic Tool.

 

[Laith]

Hmm, did any CD:s come with your 60GB SSD?

 

[Reyjakai]

Not that I'm aware of. I can double check on their website, though. I'm going to be upgrading my hard drive to a solid state 500 GB drive in a week or two, so that would definitely let me know if the hard drive is the problem.

 

[Laith]

That sounds reallllllllly fancy. We'll wait until then.

 

[Reyjakai]

Well, just got my new hard drive, installed it, and bam. Bluescreen.

 

[Laith]

Hmm,

BugCheck A, {fffff80003e12310, 2, 1, fffff80002c7956a}

Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+20a )

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Reyjakai]

Updates done, ran system file checker and checkdisk - Still bluescreened with a different error this time. Should I be thinking it's my ram, even though it ran for 8 passes without a problem last time? New bluescreen attached.

 

[Laith]

Hmm,

BugCheck 24, {1904fb, fffff8800c7a1f68, fffff8800c7a17c0, fffff80002d0580b}

Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )

Run MemTest86+ again.

 

[Reyjakai]

Passed again with flying colors.

 

[Laith]

Hmm, run SeaTools on the HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[Reyjakai]

Ran all the tests, every one passed, even the long one.

https://gyazo.com/0b2c21912a3890bbf9ba6dc9d6025c85

 

[Laith]

Run Furmark, if the temps goes too high stop the test. http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html