BSOD Can't find the fault driver.

[SergioQ]

Hi Guys,

I'm having frequent BSOD.

What is not:
is not the ram or HD because I checked both and bought new ones.

I think is some driver fault but I can` find which one is it.

I already update all my driver to the latest.

Below is the report form whoCrashed.
____________________

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-B9FF5CR
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., B85M-G R2.0
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17080770560 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 16/07/2017 19:18:11 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071617-28390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x61948, 0x1F8220, 0x1, 0x1F8220)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 16/07/2017 19:18:11 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61948, 0x1F8220, 0x1, 0x1F8220)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 16/07/2017 04:47:04 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071617-26421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF802BA068D48)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 15/07/2017 03:59:46 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-24984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x888A, 0xFFFFF05EC7A82E50, 0xC00064A7F000F065, 0xFFFFDE8005F9F100)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 15/07/2017 02:22:52 your computer crashed
crash dump file: C:\WINDOWS\Minidump\071517-40187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800AD604FC7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

11 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Thanks!

 

[Colif]

who crashed just blaming windows. Sometimes its not overly helpful.

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it


In case no one looks at this for a while, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again. Also helps to run system restore before hand to create a backup to roll back to if necessary. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB
Once it bsod, run Who crashed and see what driver it reveals

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC

 

[SergioQ]

Hi,

I already did the virifier but it didn't find nothing. Or I don't know how to use it.

Here are the dumpfiles.

https://www.4shared.com/rar/yxBVq0T2ei/Minidump.html

 

[gardenman]

Hi, after trying a few times I finally figured out that I have to sign up to 4shared with email (I don't do social media which was an another way to login) and wait 60 seconds to download the minidump. I'm waiting on a verification email from them which hasn't went through yet, but the download did go through.

I ran the dump files through the debugger and got the following information: https://pastebin.com/bfnujjWL

File: 071717-27828-01.dmp (Mon Jul 17 04:50:33.602 2017)
BugCheck: [MEMORY_MANAGEMENT (1A)] {61948, 1fac62, 1, 1fac62}
Probably caused by: memory_corruption (Process: AvastSvc.exe)

File: 071717-31687-01.dmp (Sun Jul 16 23:17:51.467 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (a)] {ffffd605a5f027a0, ff, 0, fffff801a0afca26}
Probably caused by: aswbidsdrivera.sys (Process: AvastSvc.exe)

File: 071717-30171-01.dmp (Mon Jul 17 01:21:42.007 2017)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)] {c0000005, fffff80133218e58, ffffbc006c0dea20, 0}
Probably caused by: memory_corruption (Process: Battle.net.exe)

File: 071717-29500-01.dmp (Mon Jul 17 15:18:02.922 2017)
BugCheck: [MEMORY_MANAGEMENT (1A)] {41201, ffff8d3ffbf86398, 1fc454025, ffff908e7176fd90}
Probably caused by: memory_corruption (Process: sppsvc.exe)

File: 071717-28296-01.dmp (Mon Jul 17 13:29:48.569 2017)
BugCheck 4E, {99, 1fbb51, 0, 0}
Probably caused by: memory_corruption (Process: chrome.exe)

File: 071617-33296-01.dmp (Sun Jul 16 22:52:06.408 2017)
BugCheck: [MEMORY_MANAGEMENT (1A)] {41201, ffff83bffb6c7b68, 1fc90d025, ffffad0a53e7b540}
Probably caused by: memory_corruption (Process: SppExtComObj.Exe)

I can't help you with this. Wait for Colif or someone else to reply. Good luck.

 

[Colif]

top 2 say they caused by Avast... while that is possible, the fact you have battlenet showing makes me wonder if its the lan drivers instead.

sppsvc = Microsoft Software Protection Platform Service. this is tied into licencing so are you running a legit activation of windows?
SppExtComObj.Exe is part of Key Management Services connection broker, which is also tied into licencing

 

[SergioQ]

Hi Colif and Gardenman,

thank you for for answers.

Yes my windows 10 is pirate. But I have also installed this pirate version on my notebook and the BSOD doesn't happen there. In the past I thought could be this too, so I change to windows seven (pirate) it gave the same BSOD, but my other computer didn't when using the same pirate version of it.

About the avast and battlenet I don't think is either because before installing them I had bsod already.
About the lan, I use a offboard wifi connect and gives the BSOD still, when a removed it and use the inboard by cable lan it also gave BSOD all the same.

Should I upload all my minidumps so you can have a more clear picture?
What software are you guys using to read the minidump, because I can't read them using windbg, using this softwere I can only read the big dump file but not the minidump.

Also, I really greatful for your help, thanks so much.

Thanks!

 

[Colif]

I can't help you with Pirate version of windows, it goes against the rules here so your best bet is to get legal copies and see if it fixes errors