BSOD Bugcheckcode 10

[batmounn123]

Heya!

I'm back again and I'm extremely unhappy. I built this PC about 5-6 weeks ago and I've gone to 3 computer stores (or whatever you call them, I'm no native English speaker). They found nothing wrong after testing and they also ran multiple stress tests which never, you know, crashed at all. But I just got it back this week from the 3rd turn in and it's still not fixed and I'm literally losing my mind.
Just mere minutes ago I got my first actual BSOD (other crashes have just been a bugcheckcode 0 Kernel Power 41 63 crash, which I'm still uncertain of because I've got no idea whats causing it).

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>5</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000400000000002</Keywords> 
  <TimeCreated SystemTime="2017-10-07T21:43:54.182890800Z" /> 
  <EventRecordID>10816</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-OLR01E8</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">10</Data> 
  <Data Name="BugcheckParameter1">0xffff8c860739ffe0</Data> 
  <Data Name="BugcheckParameter2">0x2</Data> 
  <Data Name="BugcheckParameter3">0x1</Data> 
  <Data Name="BugcheckParameter4">0xfffff80165ac20a5</Data> 
  <Data Name="SleepInProgress">0</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  <Data Name="BootAppStatus">0</Data> 
  <Data Name="Checkpoint">0</Data> 
  <Data Name="ConnectedStandbyInProgress">false</Data> 
  <Data Name="SystemSleepTransitionsToOn">0</Data> 
  <Data Name="CsEntryScenarioInstanceId">0</Data> 
  <Data Name="BugcheckInfoFromEFI">true</Data> 
  </EventData>
  </Event>

Specs:
ASUS GeForce GTX 1060 6GB
Intel Core 87-7700k Kaby Lake
Crucial Ballistix Sport LT DDR4 16GB
ASUS Strix B250F Gaming

I'm losing my mind googling back and forth looking for "fixes" and I'm going insane and I'd appreciate any help thrown at me. Thank you.

 

[johnbl]

put the files from c:\windows\mindump directory on a cloud server like Microsoft onedrive, share the files for public access and post a link.

otherwise, update your bios and drivers from your motherboards vendors website as a first attempt at a fix.

 

[batmounn123]

put the files from c:\windows\mindump directory on a cloud server like Microsoft onedrive, share the files for public access and post a link.

otherwise, update your bios and drivers from your motherboards vendors website as a first attempt at a fix.

Sorry for the delay, but thank you for taking your time to respond to my plead for help!
I went to sleep in my frustration but I'm back now and I was able to put only one of the .dmp files into a .zip.

Link: https://1drv.ms/u/s!Apcha57W88jxsAFrvom9ipJH6foc

I also had some more problems on my side such as one of the ram-sticks deciding to revolt and stop cooperating with my mobo. Dual channel worked fine for about 2 weeks and now it decided it had had enough.
Good news though (or so I'd like to think)! The games that caused the PC crashes are now playable for about 5 minutes instead of 30 seconds before the screens go black and the fans hit the road going 110mph.

 

[johnbl]

some hardward did not respond within its timeout.
(two graphics tweak drivers would be a likely cause of this bugcheck)
I would remove RivaTuner and retest
RTCore64.sys Fri Sep 30 05:03:17 2016
also remove asus gpu tweak utility:
IOMap64.sys Fri Apr 28 03:02:15 2017

I would consider removing
NetFilter SDK TDI Hook Driver
netfilter2.sys Sat Sep 17 17:52:38 2016
http://netfiltersdk.com/download.html
-------------

this driver has a bug that corrupts memoryno fix)
Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver
ScpVBus.sys Sun May 5 14:31:26 2013
I think the uninstaller did not work correctly also, to remove it you have to use this method:https://technet.microsoft.com/en-us/library/cc730875(v=ws.11).aspx
(most likely not the cause of this bugcheck)


old asus driver installed:
Asus PCProbe Utility
AsIO.sys Wed Aug 22 02:54:47 2012

 

[axe0axe0]

A driver took too long to finish a DPC or ISR, a 0x133 is typically speaking of a double delay before execution and typically caused by a driver.

Run driver verifier: https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html

 

[johnbl]

ScpVBus.sys fails verifier testing so you have to remove it or exclude it from testing first or the system will just bugcheck due to ScpVBus.sys. (the driver does not have a required pooltag)

A driver took too long to finish a DPC or ISR, a 0x133 is typically speaking of a double delay before execution and typically caused by a driver.

Run driver verifier: https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html

 

[axe0axe0]

I did not see any bsod caused by driver verifier on top of my head, where have you found the driver causing memory corruption and being flagged by verifier?

 

[johnbl]

just past experience. when verifier gets turned on it bugchecks on the 2013 ScpVBus.sys
driver. I think it was they used a null pool tag.

I did not see any bsod caused by driver verifier on top of my head, where have you found the driver causing memory corruption and being flagged by verifier?