BSOD, Fine in safe mode - Driver?

PatZ1989

PatZ1989

PatZ1989

Associate
Joined
4 Mar 2010
Posts
1,304
Hello, I posted initially in memory as I thought it was the cause of my constant BSOD, however after booting into safe mode this evening windows is perfectly fine, leading me to suspect a driver?

I haven't had to diagnose anything like this for many years now and was just wondering if there is any advice on the best route to go down for getting to the bottom of it?
 
Sorry, hardware is;
MSI Z170A M7 motherboard
Kingston HyperX DDR4 Memory
Intel i6-6700k
Crucial M4 SSD

OS is Windows 8.1

Using bluescreenview it suggests the address causing it is ntoskrnl.exe and volmgr.sys
 
1a can be a bad stick of ram or not enough ram voltage.

1e can be not enough vcore.

Not sure if the old list still applies with Skylake though.
 
Interesting, somebody before mentioned about voltage - all the hardware is running as stock though nothing has been changed in the motherboard, seems odd for it to be low on power when i havent made any power changes?

I have a 1000w coolermaster psu is there any reason to suspect this might be the problem?
 
I have four from today,

ntoskrnl.exe with bug check 0x1e
ntoskrnl.exe with bug check 0x1a
ntkrnlmp.exe with bug check 0x3b
ntoskrnl.exe with bug check 0x3B

Mean anything to anyone heh? googling it as well for answers
 
3b bugchecks are likely to be memory related. Last time I had repeated 3b BSODs, it was faulty RAM to blame for them. It may be worth running memtest and seeing if it picks anything up.
 
lot of things im looking at keep coming back to memory, it was my initial thought but with windows running fine in safe mode i dismissed that? wrong decision?
 
Never knew about whocrashed. Have always used windbg myself :). You just tell it to analyse the dump file and off it goes.

You're a bit stuck currently. Ntoskrnl is going to be loaded whether you are in safe mode or not, like you ram. So if it's not happening in safe mode it's probably something interacting badly, and it's not recording it.

Is it seemingly random or does it follow a pattern? Like always a few mins after logging in?

And your output from crash view hasn't helped :(. Look in eventvwr and see what was loaded just before the crash.

Alternatively used msconfig to disable everything non-Microsoft and restart, see if it crashes then enable one thing (or divide and conqueror method) at a time until you find the problem.

Nox
 
You must log in or register to reply here.
Back
Top Bottom