needing help with BSOD

[kylen1234567777]

Hello, so ive been having BSOD for a while since i upgraded my pc from win 7 to 10, after this i formatted the drive and reinstalled a clean version of win 10 and all the drivers, still having BSOD so i reinstalled win 10 again, still having issues.
From that i started trying to roll back drivers, after roll back of chipset drivers i had no BSOD for 14 days, but now its back again, without any further updates. I have had many errors with different reasons, but currently i am receiving this minidump
(through WhoCrashed)

On Thu 17/08/2017 12:22:10 PM your computer crashed
crash dump file: C:\Windows\Minidump\081717-6312-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80D3D569D0E)
Bugcheck code: 0x7F (0x8, 0xFFFFF8004146BE70, 0x0, 0xFFFFF80D3D569D0E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 385.28
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 385.28
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.28 , NVIDIA Corporation).
Google query: NVIDIA Corporation UNEXPECTED_KERNEL_MODE_TRAP



System specs
Computer name: DESKTOP-QOG6GDH
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\Windows
Hardware: MS-7A38, Micro-Star International Co., Ltd, B350M BAZOOKA (MS-7A38)
CPU: AuthenticAMD AMD Ryzen 7 1700 Eight-Core Processor AMD586, level: 23
16 logical processors, active mask: 65535
RAM: 34309632000 bytes total
GPU: MSI Geforce GTX 1050Ti Gaming X

I am a massive noob so any instructions would be good in basic form,
Thanks in advance

 

[okcnaline]

Try to install an older version of your GPU driver before you RMA it.

 

[kylen1234567777]

so its likely a GPU issue? i have tried earlier versions but i will try the version from the MSI website which is 376.09 rather than the currently installed 385.28

 

[kylen1234567777]

also it doesnt BSOD all the time, maybe 1 in 3 times the computer is turned on, and it occurs after i have logged in.

 

[okcnaline]

What power supply do you have?

 

[kylen1234567777]

i have a cooler master V650

after backdating the nvidia driver i had another BSOD,

here is the crash report:

On Thu 17/08/2017 10:18:39 PM your computer crashed
crash dump file: C:\Windows\Minidump\081717-6000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800B7374067, 0xFFFFE701B7837E70, 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 17/08/2017 10:18:39 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: 0x3B (0xC0000005, 0xFFFFF800B7374067, 0xFFFFE701B7837E70, 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.

 

[kylen1234567777]

just received this error also

On Thu 17/08/2017 10:27:51 PM your computer crashed
crash dump file: C:\Windows\Minidump\081717-5390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x50 (0xFFFFF809186861E6, 0x10, 0xFFFFF809186861E6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 17/08/2017 10:27:51 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: 0x50 (0xFFFFF809186861E6, 0x10, 0xFFFFF809186861E6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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.

 

[okcnaline]

Try a memtest86+.

 

[kylen1234567777]

just ran a memtest86+ and received no errors

Beforehand i had another bsod which gave this report

On Fri 18/08/2017 10:30:59 PM your computer crashed
crash dump file: C:\Windows\Minidump\081817-6359-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x84ED)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801E78C84ED, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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.
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.


do you think it could be something that is broken but just seems to operate sometimes?
thanks

 

[kylen1234567777]

here is another one, don't know how helpful these reports are

On Sat 19/08/2017 3:56:21 PM your computer crashed
crash dump file: C:\Windows\Minidump\081917-6000-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x226A20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF807B13B6A20, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3696fe4b96482e60\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 376.09
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.09
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 376.09 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED

 

[okcnaline]

What's your PSU? And can you do a memtest86+

 

[kylen1234567777]

psu is cooler master V650 and i have, it said there was no errors

 

[kylen1234567777]

still having BSOD issues, this one was today

On Tue 22/08/2017 9:48:14 AM your computer crashed
crash dump file: C:\Windows\Minidump\082217-6109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x139 (0x4, 0xFFFFC78D590DAFA0, 0xFFFFC78D590DAEF8, 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.



On Tue 22/08/2017 9:48:14 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xCD31D)
Bugcheck code: 0x139 (0x4, 0xFFFFC78D590DAFA0, 0xFFFFC78D590DAEF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
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.

 

[okcnaline]

Are you reusing an old hard drive?

 

[kylen1234567777]

the one that is running the OS is less than 4 months old and is a crucial MX300 275GB SSD but i have one that has other programs installed such as games which is a 1tb HDD Caviar Blue that would be just under a year old

 

[Lee-m]

That range of many seemingly unrelated BSOD errors does make me think memory issue. I know you did a mem test, but it might be worth running the machine on one stick of ram at a time to try rule out the possibility one had developed an issue. I had a problem not too dissimilar my self a few years back.

This one: PAGE_FAULT_IN_NONPAGED_AREA is a ram related bsod (but it could be as random as the others I guess). Could also be caused by an unstable overclock.

 

[kylen1234567777]

thankyou i will run the system on each individual stick of ram.
and i have not overclocked the system
could it be to do with the A-XMP profiles on the bios, i have no idea which one i should be running but it seems to have had BSOD on both profiles 1 and 2 as well as when no profile is selected.
thanks

 

[kylen1234567777]

i had not received BSOD in the past 4 days until today,
On Fri 25/08/2017 4:11:00 PM your computer crashed
crash dump file: C:\Windows\Minidump\082517-6203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF800FC478348, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.


i will now proceed to run the pc with swapping out the ram sticks between bsod's to see if one out will stop the issue
thanks

 

[okcnaline]

Is your CPU overclocked?

 

[kylen1234567777]

hello, still having this issue but have been doing exams so i have just been ignoring it.
and no the cpu is not overclocked.
currently seems to crash once or twice on the first start for the day then works perfectly fine.
The BSOD errors have still been random
not really sure what to do.
Thanks

 

[Paul NZ]

The ntfs stop error is hdd related so it maybe faulty. Or corrupt


Upload the latest dmp files to onedrive or somewhere, then post the link

 

[kylen1234567777]

my computer seems to remove the dump files
this is the most recent report from WhoCrashed that happened about an hour ago

On Sat 4/11/2017 9:37:26 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\110417-30500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x50 (0xFFFFF801840B71F2, 0x10, 0xFFFFF801840B71F2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.

and here is a link to the minidump file on onedrive

https://1drv.ms/f/s!AhjhMnllLoTXkgoKoEEm6eNR1ZME

is it more helpful if i set the system to store a full dump report?
thanks

 

[Paul NZ]

Steam maybe causing it - Memory corruption

I would uninstall Afterburner

 

[kylen1234567777]

afterburner has not been installed since i last formatted my drives
although i do have other msi apps such as:
Command centre
Dragon eye
Gaming app
Smart tool
Live update

Could any of these create a similar issue?
thanks

 

[Paul NZ]

Liveupdate is a known cause of crashes

But the main one will be the ntfs.sys crash. Since the system / files will be corrupt. I would also try another sata cable and another port