Need help with different BSOD episodes on Windows 10

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

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.
 
dxgmms2.sys = Direct X. Most of the time this crashes its caused by the GPU

Try this: http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

I think if PSU wasn't good enough for GPU you would be getting different behaviour like screen turning off randomly or PC not starting USB slots (as they seem to be ignored if power is low)

Not sure why realtek network drivers running then if you on WiFi - i can't read dumps but Gardenman will some time.
 
Alright I'll try to do the clean install tomorrow. How do I know the chipset of my motherboard btw? There's so much to see under my device manager and I don't even know why there are so many repeated devices 🙁 Sorry I'm just plain average on PCs.

Device Manager Screenshot: HERE
 
chipset? Why do you need to know that? Your motherboard is a: B350M BAZOOKA (MS-7A38) , that is its chipset.

See here: https://www.msi.com/Motherboard/B350M-BAZOOKA/Specification

You should have looked in system info, not device manager, to find motherboard... I was trying to work out why you even looked there until i figured out you were looking for motherboard details. System devices does seem to have a lot in there but as I never look, it might be normal for a Ryzen CPU.
 
Crashed today
Minidump: HERE

WhoCrashed:
On Thu 12/28/2017 12:38:52 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\122817-18343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x139 (0x3, 0xFFFF9A80BA9F74C0, 0xFFFF9A80BA9F7418, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
NPFD.sys =
The NPFS component provides the Named Pipe File System driver and supporting registry information. The Named Pipe File System driver is contained in the npfs.sys file and implements named pipes.

https://msdn.microsoft.com/en-us/library/aa940098%28v=winembedded.5%29.aspx?f=255&MSPPError=-2147217396

I wish I knew what it did, or what to offer as a solution to why it crashed.

Usually, npfs.sys blue screen errors are caused by problems with your hardware devices or issues with low-level software running in the Windows kernel. Many reasons can cause errors on your hard disk, such as shutting down the computer irregularly, removing USB devices without using Safely Remove, and wrong version of device drivers. Fortunately, there is a utility called chkdsk (short for Check Disk) that can scan for errors and fix potential problems.
i won't link source as their 2nd fix is just silly.

since running chkdsk wants a restart anyway, might as well run it in advanced startup
go to settings/update & security/recovery
under advanced startup, click restart now button
this loads a blue menu
choose troubleshoot
choose advanced
choose command prompt
type chkdsk C: /f (if you only have a HDD, you can type chkdsk C: /r) and press enter

 
Everything seems fine after the chkdsk. I grew tired of the technical difficulties and just resorted to a clean install of win10. I couldn't figure out what's causing the hiccup :/ thank you all for the replies and the time you spent in trying to help me out. Windows 10 is just like a woman you can never figure out sometimes..
 
windows 10 is also more complicated that it appears on the surface, the more I find out the less I know.

Funny you say a fresh install fixes it as the source of one of the posts above suggested reinstalling win 10 to fix it. That isn't a step I suggest normally unless a few other fixes don't work. Seems you were ready to jump to that step without me.
 
Yeah I'm sorry 🙁 I got a new ssd so I ended up installing a new os there. So far no bsods. I guess it was one of my drivers that I couldn't figure out which. Thank you for your help though, I learned a lot from it.