Windows 10 BSOD - intelppm.sys frequently - Often from gaming

Hi @LittleDansonGuy.

Most of your recent issues are 0x7F with EXCEPTION_DOUBLE_FAULT; and there is a 0x5C (HAL_INITIALIZATION_FAILED).
So there is a fair chance that some hardware element is causing the issue there.

The first suspect is your Razer DeathAdder keyboard/Mouse.

Code:

ffffd000`5a0ab198  fffff801`0c4911a4Unable to load image VKbms.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VKbms.sys
*** ERROR: Module load completed but symbols could not be loaded for VKbms.sys
 VKbms+0x11a4

How old those are? The indication is there that they are too old to work with Windows 10 properly.

Code:

    Image name: VKbms.sys
    Timestamp:        Thu Sep 30 21:46:33 2010 (4CA4B7E1)

The driver is too old for Windows 10. Search for any possible update. Razer Support
Let us know what you get.

The OnBoard LAN driver is also failing.

Code:

ffffd000`5a0a9e48  fffff801`0e0a8c4cUnable to load image rt640x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
 rt640x64+0x18c4c
--------------------------------------------------------------
    Image name: rt640x64.sys
    Timestamp:        Wed Oct 07 20:33:55 2015 (5615345B)

Update it to 10.8.311.2016 dated 2016-06-16. Support For Z170-A PRO | MSI Global | Motherboard - The world leader in motherboard design

Let us know how these two goes. We may need to go for further troubleshooting if situation demands.

Looks like I got another HAL error. I have included that newest dump (dated 07/02) in the new debug folder. I made the changes noted in your previous post. Looks like we'll have to dig deeper here...

If I failed to mention, this is also a new occurrence. Everything worked fine for a good week and a half. I also can't System Restore. It always gives me an error saying it couldn't roll back.

I will mention again that this is strictly only occurring during video gaming, if that is any strong indicator. I have also run the Intel Processor Test and that passed. I also ran 6 passes of Memtest86 with no errors for my 16GB RAM. Any extra help would be appreciated.

--07/03--
Editing this post to include yet another crash. This time I looked at BlueScreenViewer and saw that this new BSOD could have been a result of a storport.sys. I'll leave the complete analytics up to you all. However, things seems to be getting quicker. Some BSODs take a few hours, but they are coming at a pace of about 15-30 minutes while playing a video game.

Thanks for the help again.

I see you updated the network driver. But it is still flagged.

Code:

ffffd000`9342a7d8  fffff800`b8d74802Unable to load image rt640x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
 rt640x64+0xd4802
---------------------------------------------------------------------------------------
    Image name: rt640x64.sys
    Timestamp:        Fri Mar 11 11:27:50 2016 (56E25E5E)

This is the only thing that is clearly flagged in the last crash dump.

You said about storport .... so I checked ..... there are some raw stack items about storport .....

Code:

ffffd000`9342a718  fffff800`b76373f6 storport!RaidCheckPerProcessorCompletions+0x76
ffffd000`9342a748  fffff800`b7633ba1 storport!RaidStartIoPacket+0x3e1
ffffd000`9342a8b8  fffff800`b7678000 storport!WPP_GLOBAL_Control

As far as I can see, it seems that your system is not a RAID one. Is it actually? Let us know.

And some entries pointing to the keyboard/mouse as well ....

Code:

ffffd000`9342b538  fffff800`b9b42000 HIDCLASS!HidpInterruptReadComplete+0x750
ffffd000`9342b550  fffff800`b9b56200 HIDCLASS!WPP_343ddaa2f0f2144f41b75a2a5425abbf_Traceguids

Which apparently should not be there after taking care about the Razer thing.

Now I have some questions for you?

First, why are you using some ASUS bloatwares on a MSI motherboard?

Start Menu\Programs\ASUS\AI Suite Public:Start Menu\Programs\ASUS\AI Suite Public
Start Menu\Programs\ASUS\PC Probe II Public:Start Menu\Programs\ASUS\PC Probe II Public

Was the previous board an ASUS one, and the current installation is actually not a clean installation?
Explain it properly, because this would be one key information here. Have you performed a clean installation after changing the motherboard?

Second .... are you overclocking?

Code:

MaxSpeed:     4000
CurrentSpeed: 4008

Let us know. This will be another key information.

LittleDansonGuy said:

I did not do a clean install. Is that perhaps the answer?

Please perform a clean install. Because the mismatch drivers carried forward from the previous motherboard may cause all the issues there.

• Windows 10 - Clean Install - Page 11 - Windows 10 Forums
• Clean Install Windows 10 Directly without having to Upgrade First - Windows 10 Forums

If it goes the same even after a clean install, then further troubleshooting will be a must. So let us know the situation after a clean install.

In those two dumps, it is again the network driver that is th only flagged driver.

Code:

ffffd000`d7bf11b8  fffff800`2a79a305Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
 rt640x64+0x6a305

Which gives an indication that something is using the network abnormally. If it is the WoW game, then we can say that the game is so called poorly coded .... it causes network and graphics related glitches a lot.
If it behaves the same outside that game, then .... one network usage is common between your previous and current installation. Google Chrome AutoLaunch.

Code:

GoogleChromeAutoLaunch_2C7C08ACC7DE94D8A4468D1F14464A81, "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --no-startup-window /prefetch:5

Please perform a Clean Boot in order to make it sure that some unnecessary background program/service is not causing the issue.

At the next step we will go for hardware testing.