Windows 10: BSOD every cold start

Hi,

I'm getting BSOD every cold start of my PC every day. After rebooting everything runs fine.
The system is new (it was built a week ago). memtest86 showed no errors and clean windows reinstall didn't help as well.
Yesterday I updated all drivers/BIOS via MSI live update, and today I've got a new error - this time it was DPC_WATCHDOG_VIOLATION (I have never seen this error before).

Let me know if you need any additional information (tests, system info etc.)

Here is my system spec:
Computer type: PC/Desktop
OS :Windows 10
CPU: Intel Core i7 6700
Motherboard: MSI Z170A Gaming M7
Memory: Corsair Vengeance LPX 16GB 2400MHz (2x8GB)
Graphics Card(s): NVidia GeForce GTX970

dm_log_collector results: Attachment 69945
CPU-Z results: Attachment 69947

Thank you,
Yurii

:)

 

Windows 10 - BSOD: KMODE EXCEPTION NOT HANDLED

I've had the same problem. After upgrade to Windows 10 I got BSOD on every cold start of my notebook.

Here are my minidumps: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Thank you.

 

DPC_WATCHDOG_VIOLATION

I updated my Bios driver to latest.

I could no longer boot, "BootMgr is missing". After searching the boards and troubleshooting, the bios had changed the hard drive to boot from. I was able to successfully boot up into Win10.

Cold start continued to produce BSOD, as before.

Following Team ZigZag suggestions, rename Pnp680.sys to *.bak, resolved BSOD and now cold start and warm start smoothly into Win10.

Many thanks to your quick responses.

Very helpful and much appreciated!

 

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling system and other used stuff. PSU, cooling system and other used stuff are not mentioned in the tool!How to fill in your system specs:

 

Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling system and other used stuff. PSU, cooling system and other used stuff are not mentioned in the tool!How to fill in your system specs:





Hey Axe0 how come you haven't even responded to my thread in over 15 hours? I need your help, linked a new dump and am telling you that I am having problems with the BSOD. I am surprised.

 

@Mikey5Aces

Solved BSOD randomly browsing internet; ntoskrnl.exe - Page 6 - Windows 10 Forums

 

Oh didn't know that and I am sorry. It's just I have seen you skip over my thread and answer others for a lot of hours now. I am frustrated and even put up a new dump file. The BSOD keeps happening every time I play a game and quit. Within 3 minutes the Driver Power State Failure BSOD appears and restarts my computer. Could you please quickly look at my new dump file and give your thoughts? Thx

 

I've skipped many threads, some because I forgot, others due to the amount of new threads that are frequently created, but all OP's have kindly reminded me about it in the way I asked for in my signature *Smile

 

So would you mind quickly looking at my thread and new dump file and give me your latest suggestions?? Thx. I am sitting here right now with a barely functioning laptop any time I play a game.

 

Hi, thank you for a quick reply.
Today I've got a new BSOD - this time MEMORY_MANAGEMENT. Updated dm_log_collector results: Attachment 70164
I'm currently running Driver Verifier, if there will be any new details I will post them as soon as possible.
Also I updated my specification.

Thank you once again!*Smile

 

It is best to wait until verifier crashes your system, or not, before another suggestion is being made.

 

Hi again,

I was running Driver Verifier over 48 hours and had no crash. I still have BSOD each cold start (BAD_POOL_HEADER) but I noticed quite strange behavior - on Monday I passed memtest with no errors, but yesterday I got like 60 or so. Could this be due to CPU and memory incompatibility? I have non-K i7 (stupid decision, but "oh well...") and 2400MHz memory. BIOS shows that it runs on 2133MHz as it should by default. Once just after finishing my build I enabled XMP profile and it was running at 2400MHz, but then I disabled it. Today I will try to clear cmos just to eliminate any possible issues due to my curly hands*Smile

Maybe you have any other ideas regarding what might be wrong?

Thank you,
Yurii

 

Possibly the memory too low in voltage so yes memory not compatible.
Attachment 70917
Attachment 70918
Intel Core™ i7-6700 Processor (8M Cache, up to 4.00 GHz) Specifications
Vengeance® LPX 16GB (2x8GB) DDR4 DRAM 2400MHz C14 Memory Kit - Black (CMK16GX4M2A2400C14)

 

I had the same problem with Win 7 but never solved it, however when I moved to Win 10, I again had the same problem but managed to solve it by switching off "Fast Startup" which is configured by default in Windows 10.
This apparently is similar to Hibernate and saves a copy of your system settings and Kernal image,
When you start the computer again, Windows does not have to reload the kernel, drivers, and system state individually. Instead, it just refreshes your RAM with the loaded image from the hibernation file and delivers you to the login screen, or in my case Crashes !!!
I guess if you have slow ram (when Cold) this could be causing the problem, coincidentally I always had similar problems with hibernate on Windows 7.
This link expalains Fast Startup in more detail and explains how to disable it.
The Pros and Cons of Windows 10’s “Fast Startup” Mode

 

Hi Steven, thank you for your reply. I replaced my RAM with different kit (this time I was reading motherboard specification carefully and selected memory from compatibility matrix - HyperX 2133 kit) and it solved my problem. Will try to find someone with different motherboard to test my first kit and find out whether it works fine or not.
Regardign your idea - it looks quite sensible, but unfortunately I'm not qualified specialist in this area, so I can't say anything for sure. But, again, now with 2133 kit everything works perfectly fine.