Need help with different BSOD episodes on Windows 10

Toggle sidebar Toggle sidebar
M

mauibot

Reputable
Aug 17, 2014
22
0
4,510
I recently bought a prebuilt desktop from CyberpowerPC during Black Friday sales and I have been worried if I have a hardware problem or the blue screens are being caused by drivers that aren't updated. I check my device manager and all drivers seems to be updated. I have no idea how to update BIOS because I'm not really a proper win10 technician but I've tried everything an average desktop owner could possibly do to find out the problem but I have no luck so far.

Can anyone in this forums help me? Will be much appreciated.


-------------------------------------------------
WhoCrashed Analysis

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

Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: MS-7A38, Micro-Star International Co., Ltd, MSI, B350M BAZOOKA (MS-7A38)
CPU: AuthenticAMD AMD Ryzen 5 1400 Quad-Core Processor AMD586, level: 23
8 logical processors, active mask: 255
RAM: 8540155904 bytes total

I saw on msinfo32.exe under Device Encryption Support TPM is not usable, PRC7 binding not supported, What does that mean???




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 12/8/2017 8:41:19 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFA582BA41B035)
Bugcheck code: 0xA (0xFFFFA582BA41B035, 0xFF, 0xB3, 0xFFFFF8000AD86107)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error.
Google query: IRQL_NOT_LESS_OR_EQUAL





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

One crash dump has been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
Sort by date Sort by votes
can you go to C:\windows folder, change view to show hidden files and folders
copy the Memory.dmp file from here to documents
upload the copy from documents to a file sharing web site and share link here.
Someone with the necessary sopftware to read them will look at dump and see what cause might be

Who crashed tells you what crashed but not why, its hit and miss whether it actually helps. Worth a try though :)
 
Upvote 0 Downvote
I just had another BSOD episode but it seems to be from another different problem... I'm really getting sad and worried as this is a brand new pc and there's a lot of problems I can't solve. I've never had this much technical difficulties before using win10. 🙁

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 12/9/2017 4:11:03 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\120917-25500-01.dmp
This was probably caused by the following module: netwtw04.sys (Netwtw04+0x33F670)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80A9090F670, 0xFFFFC9827DB15040, 0x3)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netwtw04.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwtw04.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED



On Sat 12/9/2017 4:11:03 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: netwtw04.sys (Netwtw04+0x33F670)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80A9090F670, 0xFFFFC9827DB15040, 0x3)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netwtw04.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwtw04.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED


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

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

netwtw04.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

.dmp file here
crash dmp#2

If it's not there yet it means I'm still uploading. I'm just posting beforehand because I had to go somewhere. Thanks to anyone who will be able to help me out!
 
Upvote 0 Downvote
I see, Thanks Paul. Do you have any idea what caused my first bsod? And I already got the latest driver from intel. I remember downloading it a few days back because I've been having bsod episodes at least once a day and I made sure I had my drivers updated even if I had to do it manually so I'm not sure why it caused an error. :/ Sorry for the trouble.

 
Upvote 0 Downvote
I have an Intel® Dual Band Wireless-AC 3165 and the latest version is 19.51.8.2 which turns out I do have the latest driver. I updated my bluetooth driver as well though. Will observe if I get any bsod episodes after this.
 
Upvote 0 Downvote
Okay so I had another hiccup today but it's from BAD_POOL_HEADER

DUMP FILE here.

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 12/10/2017 3:36:52 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121017-27343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x19 (0xD, 0xFFFFE5836BF27000, 0x3FF45C285E09B339, 0x3FF45C285EB9B339)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 12/10/2017 3:36:52 PM 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: 0x19 (0xD, 0xFFFFE5836BF27000, 0x3FF45C285E09B339, 0x3FF45C285EB9B339)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.





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

2 crash dumps have been found and analyzed. 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 
Upvote 0 Downvote
Update:
I updated all my drivers that I could find on MSI site for my motherboard and graphics card and I still got another hiccup

Minidump here

I was just playing pubg and the game froze, turned black with a little red tinge. It wasn't even a BSOD so I'm really bummed about all these little technical difficulties on a new system.

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 12/11/2017 11:46:23 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\121117-27234-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF801BA8E5B22)
Bugcheck code: 0xD1 (0x3700, 0x2, 0x0, 0xFFFFF801BA8E5B22)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 12/11/2017 11:46:23 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x5B22)
Bugcheck code: 0xD1 (0x3700, 0x2, 0x0, 0xFFFFF801BA8E5B22)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.





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

2 crash dumps have been found and analyzed. 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.
 
Upvote 0 Downvote
I see, thanks... then I have no way of getting that solved since tslgames is pubg itself. It's good to know it's not my hardware that's causing the problem for that...

I still don't have any solutions to my other bsod episodes though ):
 
Upvote 0 Downvote
I see. At least I have an idea what seems to be the problem. Everything else seems to be fine other than my intel wireless driver. Thanks for the insight Paul NZ
 
Upvote 0 Downvote
Well after 7 days I finally got a dreaded bsod. I was just playing league of legends at the time it happened.

Minidump: HERE

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 12/21/2017 2:39:59 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122117-17546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8010D72985E, 0xFFFFA40E06CDEEF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 12/21/2017 2:39:59 AM 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: 0x3B (0xC0000005, 0xFFFFF8010D72985E, 0xFFFFA40E06CDEEF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
 
Upvote 0 Downvote
Okay, I ran Driver Verifier and this is the result I got after making my pc bsod twice.

Minidump: HERE

WhoCrashed Interpretation:

On Fri 12/22/2017 1:31:32 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122217-14359-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Fri 12/22/2017 1:24:54 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: lgbusenum.sys (0xFFFFF80609C801F0)
Bugcheck code: 0xC4 (0x2004, 0xFFFFA00DE05104F8, 0xFFFFF80609C801F0, 0xFFFFC40C14ED80C8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\lgbusenum.sys
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: lgbusenum.sys .
Google query: lgbusenum.sys DRIVER_VERIFIER_DETECTED_VIOLATION

So the Driver Verifier bsod is from my Logitech software? What about the CUSTOM ERROR what is that?

Thanks to anyone who can enlighten me. Sorry for being such a bother on this forum...
 
Upvote 0 Downvote
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/S9Te.html

File: 122217-14359-01.dmp (Dec 22 2017 - 01:24:54)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 12 Sec(s)

File: 122117-17546-01.dmp (Dec 21 2017 - 02:39:59)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 1 Hour(s), 38 Min(s), and 38 Sec(s)

File: MEMORY.DMP (Dec 10 2017 - 15:36:52)
BugCheck: [BAD_POOL_HEADER (19)]
Probably caused by: memory_corruption (Process: Discord.exe)
Uptime: 0 Day(s), 0 Hour(s), 23 Min(s), and 37 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 0 Downvote
Go here and grab latest BIOS - a you tube link on this page also shows how to update BIOS: https://www.msi.com/Motherboard/support/B350M-BAZOOKA

Do you use WiFi or Ethernet as both drivers were loaded at time of error.

Discord crashed? Try updating NIC drivers: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=4&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true

wonder what Corsair Virtual Device driver (Corsair Utility Engine) does? do you have RGB lighted ram?
 
Upvote 0 Downvote
Update.

I just got to use my pc today, been busy. After I removed driver verifier and uninstalled the logitech software, I got another bsod today just after getting to play 1 game of league.

Minidump: HERE

Whocrashed Analysis

On Sat 12/23/2017 10:32:13 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x14C28)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8011E684C28, 0xFFFFFD8B1FF5CD18, 0xFFFFFD8B1FF5C560)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Corsair Driver is for my RGB Strafe Keyboard. I use wifi on my desktop atm, no cable for ethernet atm. I've been thinking is my 450W psu not enough for my my gpu. I'm running on RX 580

Thank you for the replies!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom