Recurring blue screen caused by ntoskrnl.exe

Toggle sidebar Toggle sidebar
M

Mtspnkch

Prominent
May 4, 2017
2
0
510
Hi all,

I've had the occasional blue screen every now and then for a couple of months but until now they've never repeated after a restart. Today however I've had a recurring blue screen a couple of minutes after I boot up. According to blue screen viewer it's being caused by ntoskrnl.exe but I'm not sure what to do or whether that means its a driver or hardware issue.

Booting into safe mode seems to prevent it, been on for ~30 minutes without a blue screen.

I have uploaded a minidump file here https://ufile.io/ny8x1 and any help or advice would be appreciated. Please let me know if there is any more information I can provide.

Thanks,
 
Solution
J
also if you ran verifier to find driver problems, I see various problems with your system drivers.
you should go to the motherboard vendor site (gigabyte) and update the bios and motherboard drivers
as well as a windows update. looks like you have old or generic windows drivers for your motherboard.
(some that would cause random memory corruption problems)

---------------
here is the stack:
it looks like a file filter is just trying to talk to a windows kernel debugger and waiting for input.
do you have a debug version running?
or someone might have left in some debug code that got triggered when you turned on verifier.

you can turn it off by verifier.exe /reset
wcifs = Windows Container Isolation





: kd> kc
*** Stack trace...
Sort by date Sort by votes
Lutfij

Lutfij

Titan
Moderator
Oct 7, 2009
54,079
4,750
173,390
1| Mind sharing your full system's specs inclusive of your OS?
2| Have you made sure your motherboard BIOS is up to date?
3| If you suspect it to be the memory, you'd need to manually input the timings, frequency and voltage for your ram kit in the BIOS and see if the issue persists.

According to Windows Debugger the error is 3B which when you're looking at overclocking, means you need more vcore but that is just a presumed solution since we're devoid of any further information. It's followup is that of memory corruption. You may want to manually key in the values and see if the issue changes but I'd suggest you run Memtest86 for at least 10 passes and see if the culprit is within the ram or the slots.

That being said, when posting a thread of troubleshooting nature, please include your full system's specs regardless of an attached *.dmp file.
 
Upvote 0 Downvote
M

Mtspnkch

Prominent
May 4, 2017
2
0
510
Oops sorry! I can't believe I forgot to include that, and here I thought I was being helpful with the dump file. I've uploaded a full dxdiag at https://ufile.io/k95uu

Operating System: Windows 10 Home 64-bit (10.0, Build 14393) (14393.rs1_release_sec.170327-1835)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: G1.Sniper B5
BIOS: BIOS Date: 09/16/14 21:17:48 Ver: 04.06.05
Processor: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 CPUs), ~3.6GHz
Memory: 16384MB RAM
Available OS Memory: 16336MB RAM
Page File: 2007MB used, 16760MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.14393.0000 64bit Unicode


Card name: NVIDIA GeForce GTX 970
Manufacturer: NVIDIA
Chip type: GeForce GTX 970
DAC type: Integrated RAMDAC


I thought I had updated the motherboard BIOS but since its giving the date as 2014 that may not be the case.


I've had the computer for about two years without any hardware changes and it is only today that it I've been unable to use it. The blue screens have been occurring since around February or so but usually only once or twice a week.

Thank you for your help!
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
also if you ran verifier to find driver problems, I see various problems with your system drivers.
you should go to the motherboard vendor site (gigabyte) and update the bios and motherboard drivers
as well as a windows update. looks like you have old or generic windows drivers for your motherboard.
(some that would cause random memory corruption problems)

---------------
here is the stack:
it looks like a file filter is just trying to talk to a windows kernel debugger and waiting for input.
do you have a debug version running?
or someone might have left in some debug code that got triggered when you turned on verifier.

you can turn it off by verifier.exe /reset
wcifs = Windows Container Isolation





: kd> kc
*** Stack trace for last set context - .thread/.cxr resets it
# Call Site
00 nt!DebugPrompt
01 nt!DbgPrompt
02 FLTMGR!FltpvPrintErrors
03 FLTMGR!FltpvValidateReadWriteParameters
04 FLTMGR!FltvWriteFile
05 wcifs!WcSetupVolumeInformationHandler
06 wcifs!WcPortMessage
07 FLTMGR!FltpvMessageNotify
08 FLTMGR!FltpFilterMessage
09 FLTMGR!FltpMsgDispatch
0a FLTMGR!FltpDispatch
0b VerifierExt!xdv_IRP_MJ_DEVICE_CONTROL_wrapper
0c nt!IovCallDriver
0d nt!IofCallDriver
0e nt!IopSynchronousServiceTail
0f nt!IopXxxControlFile
10 nt!NtDeviceIoControlFile
11 nt!KiSystemServiceCopyEnd
12 0x0
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom