[SOLVED] Random BSOD. FIX: I set the RAM to run at stock settings and I uninstalled malwarebytes.

piorun321

piorun321

Member
Joined
Apr 1, 2023
Posts
9
My computer crashes for no reason



Microsoft Windows 10 (10.0) Home 64-bit

I think original install was Windows 8

Full Version

system about 8 years old

windows reinstalled few years ago

Intel Core i7 5960X

NVIDIA GeForce GTX 1080 Ti

MSI X99A GODLIKE GAMING (MS-7883)

Seasonic Prime 1300 Platinium (model SSR-1300PD

Home made



Thanks for you help
 

Attachments

The one dump file you uploaded and the only BSOD in your System log (since 11th March 2023) is a 0x124 WHEA_UNCORRECTABLE_ERROR, indicating a hardware error. Sometimes bad or missing drivers can trigger this BSOD, as can out of date firmware.

In the dump the call stack gives a good clue to the source of your problem...
Code: 
4: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffffb98f`b12de488 fffff801`509b8a4c     nt!KeBugCheckEx
01 ffffb98f`b12de490 fffff801`509b95a9     nt!WheaReportHwError+0x3ec
02 ffffb98f`b12de570 fffff801`509b96c5     nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
03 ffffb98f`b12de5a0 fffff801`554037b1     nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
04 ffffb98f`b12de600 fffff801`553fcb80     storport!StorpWheaReportError+0x9d
05 ffffb98f`b12de690 fffff801`553cf07c     storport!StorpMarkDeviceFailed+0x358
06 ffffb98f`b12de920 fffff801`5548edb6     storport!StorPortNotification+0x91c
07 ffffb98f`b12de9f0 fffff801`5548f574     stornvme!NVMeControllerInitPart2+0x226
08 ffffb98f`b12dea70 fffff801`5548e4af     stornvme!NVMeControllerReset+0x124
09 ffffb98f`b12deaa0 fffff801`553fa275     stornvme!NVMeControllerAsyncResetWorker+0x3f
0a ffffb98f`b12dead0 fffff801`50607df5     storport!StorPortWorkItemRoutine+0x45
0b ffffb98f`b12deb00 fffff801`506bdef5     nt!IopProcessWorkItem+0x135
0c ffffb98f`b12deb70 fffff801`50655485     nt!ExpWorkerThread+0x105
0d ffffb98f`b12dec10 fffff801`50802d48     nt!PspSystemThreadStartup+0x55
0e ffffb98f`b12dec60 00000000`00000000     nt!KiStartSystemThread+0x28
You can see calls to the storport.sys driver, which is the Windows high-level storage driver. You can also see calls to the stornvme.sys driver, this is the Windows NVMe storage driver. Neither of these drivers will be at fault however, because they are Windows drivers.

You can see that things start to go awry during the three calls to stornvme.sys (notice the call to stornvme!NVMeControllerReset, probably to reset the drive controller after some sort of error). Following these stornvme.sys calls we again see storport.sys being called to mark the device as failed and initiate the bugcheck (notice the call to storport!StorpMarkDeviceFailed).

It thus seems most likely that there has been a failure of some sort accessing your NVMe drive (the Samsung 970 Pro). Sometimes (in my experience) M.2 drive issues can be fixed by removing and re-seating the drive, so I'd try that first. If that doesn't help then download Samsung Magician and see whether there is a recent Samsung driver for that 970 Pro. You might also look for a firmware update to the 970 Pro within Samsung Magician too.
 
@piorun321 Do you mind running LatencyMon for about two hours, and telling me what you get?
I think I might have solved a similar issue, and I'm curious to see what yours looks like, right now. Also do what ubuysa suggests, I just want to start thinking about this in case I can help.
 
I run sumsung magician and all firmware is up to date. I don't know why it does not show all the crashes. Tomorrow I will run LatencyMon and post the results.
 
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. Also one or more ISR routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 2:55:57 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-6798OMG
OS version: Windows 10, 10.0, version 2009, build: 19044 (x64)
Hardware: MS-7883, MSI
BIOS: 1.A1
CPU: GenuineIntel Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 65434 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 30 MHz
Reported CPU speed (registry): 30 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 20539.80
Average measured interrupt to process latency (µs): 22.317265

Highest measured interrupt to DPC latency (µs): 20533.60
Average measured interrupt to DPC latency (µs): 15.481218


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 1328.693333
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.034946
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.036817

ISR count (execution time <250 µs): 1162889
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 110166
ISR count (execution time 1000-2000 µs): 107
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 152214.313333
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.071882
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.29 , NVIDIA Corporation

Total time spent in DPCs (%) 0.227411

DPC count (execution time <250 µs): 18724837
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 180317
DPC count (execution time 1000-2000 µs): 38191
DPC count (execution time 2000-4000 µs): 6387
DPC count (execution time >=4000 µs): 1875


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: mbamservice.exe

Total number of hard pagefaults 13010
Hard pagefault count of hardest hit process: 4316
Number of processes hit: 74


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 711.150891
CPU 0 ISR highest execution time (µs): 1328.693333
CPU 0 ISR total execution time (s): 61.563536
CPU 0 ISR count: 1078775
CPU 0 DPC highest execution time (µs): 21979.563333
CPU 0 DPC total execution time (s): 201.223987
CPU 0 DPC count: 2851512
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 457.321858
CPU 1 ISR highest execution time (µs): 976.816667
CPU 1 ISR total execution time (s): 0.609083
CPU 1 ISR count: 191452
CPU 1 DPC highest execution time (µs): 9794.623333
CPU 1 DPC total execution time (s): 23.934843
CPU 1 DPC count: 1062478
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 508.521533
CPU 2 ISR highest execution time (µs): 17.750
CPU 2 ISR total execution time (s): 0.015940
CPU 2 ISR count: 2609
CPU 2 DPC highest execution time (µs): 152214.313333
CPU 2 DPC total execution time (s): 62.484608
CPU 2 DPC count: 2958229
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 405.159638
CPU 3 ISR highest execution time (µs): 19.106667
CPU 3 ISR total execution time (s): 0.002356
CPU 3 ISR count: 326
CPU 3 DPC highest execution time (µs): 2523.630
CPU 3 DPC total execution time (s): 5.27140
CPU 3 DPC count: 885759
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 419.454082
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 2526.126667
CPU 4 DPC total execution time (s): 7.956855
CPU 4 DPC count: 992376
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 421.547454
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 2523.713333
CPU 5 DPC total execution time (s): 5.274482
CPU 5 DPC count: 841453
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 434.066558
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 2524.086667
CPU 6 DPC total execution time (s): 7.433853
CPU 6 DPC count: 950031
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 432.998440
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 2523.713333
CPU 7 DPC total execution time (s): 5.580011
CPU 7 DPC count: 888261
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 431.268246
CPU 8 ISR highest execution time (µs): 0.0
CPU 8 ISR total execution time (s): 0.0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 2519.370
CPU 8 DPC total execution time (s): 7.140351
CPU 8 DPC count: 928106
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 431.314489
CPU 9 ISR highest execution time (µs): 0.0
CPU 9 ISR total execution time (s): 0.0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 2517.623333
CPU 9 DPC total execution time (s): 5.348787
CPU 9 DPC count: 858142
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 421.704345
CPU 10 ISR highest execution time (µs): 0.0
CPU 10 ISR total execution time (s): 0.0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 2516.220
CPU 10 DPC total execution time (s): 7.007146
CPU 10 DPC count: 910492
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 409.887949
CPU 11 ISR highest execution time (µs): 0.0
CPU 11 ISR total execution time (s): 0.0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 2516.680
CPU 11 DPC total execution time (s): 5.807184
CPU 11 DPC count: 881220
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 419.725836
CPU 12 ISR highest execution time (µs): 0.0
CPU 12 ISR total execution time (s): 0.0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 2513.716667
CPU 12 DPC total execution time (s): 7.333890
CPU 12 DPC count: 922881
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 421.861145
CPU 13 ISR highest execution time (µs): 0.0
CPU 13 ISR total execution time (s): 0.0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 2515.30
CPU 13 DPC total execution time (s): 6.012737
CPU 13 DPC count: 877268
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 429.785248
CPU 14 ISR highest execution time (µs): 0.0
CPU 14 ISR total execution time (s): 0.0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 2512.353333
CPU 14 DPC total execution time (s): 11.027862
CPU 14 DPC count: 1009093
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 435.517002
CPU 15 ISR highest execution time (µs): 0.0
CPU 15 ISR total execution time (s): 0.0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 2513.286667
CPU 15 DPC total execution time (s): 15.299432
CPU 15 DPC count: 1134306
_________________________________________________________________________________________________________
 
@piorun321
I doubt I'm going to be able to help you too much, however, I'm having similar issues - I can't say anything good about Win10/11, so I'll choose to say nothing at all - one thing I notice is that it seems like your network driver is the cause for your high latency spikes.

Some of the people who have similar problems to us have had luck downloading the latest version of their specific lan/wifi drivers, or obscure one-offs, uninstalling their drivers, and installing the specific drivers while praying Windows Update, which you can no longer turn off without slapdash methods, doesn't auto-update and mess up your solution. I don't know what drivers you use for Wifi/Lan, but maybe take a look at the manufacturers site and try that?
 
the validated memory for this cpu i7-5960X
should be DDR4 1600/1866/2133

your memory reports a running speed
Code: 
[Memory Device (Type 17) - Length 40 - Handle 005ah]
  Physical Memory Array Handle  0058h
  Memory Error Info Handle      [Not Provided]
  Total Width                   72 bits
  Data Width                    72 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM_A1
  Bank Locator                  NODE 1
  Memory Type                   1ah - Specification Reserved
  Type Detail                   0080h - Synchronous
  
[HI]
Speed                         3400MHz
[/HI]

  Manufacturer                  Undefined
  Serial Number                         
  Asset Tag Number                             
  Part Number                   F4-3400C16-8GTZ

thats far to much.
reduce the memoy speed, remove any tweaks increasing the speed and check again the behaviour of your system.

the dump encounters a lot of memoy coruptions whichs results in your problems.
 
i shut off overclocking, did not know it was on. pulled M2 drive out and put it back in. computer runs really slow and I still get BSOD
_part-2000000000150373_.jpg
 
Without wishing to step on the toes of the others helping you, I think now might be the time to enable Driver Verifier. This is a built-in Windows tool that subjects selected drivers to additional checks whenever they are run, if a driver fails any of these checks the system will BSOD - the resulting dump should enable us to identify the driver at fault. The idea is that you leave Drive Verifier running (it stays on even across reboots and shutdowns) for at least 24 hours, hopefully in that time you'll have had many Driver Verifier caused BSODs, and thus many dumps, and from those dumps we should be able to locate the flaky driver(s).

Full instructions on how to enable Driver Verifier, and which checks to include and which drivers to test, are here: Driver Verifier - BSOD related - Windows 11, 10, 8.1 and 8.

NOTE: Please don't skip the first item, creating a restore point. It is possible that Driver Verifier could BSOD a driver loading at boot time, that would leave you in a boot-BSOD loop. By taking a restore point before you start you can boot the Windows installation media and restore to that restore point from there, thus recovering your system.

Remember also, that we expect and want Driver Verifier to BSOD, that's what it does. Once it's been running for 24 hours or so run the data collector app again and upload the resulting zip file.

The Driver Verifier link above also tells you how to disable Driver Verifier.
 
If you're getting a Stop 0x124 and a Stop 0x7F then there definitely an issue with your SSD or least somewhere in the storage stack. Have you tried booting into Safe Mode with Networking and checking if the system crashes there?

That is why your system crashed with the Stop 0x124 bugcheck:

Code: 
4: kd> !du fffff801554a2340
IO queues sync creation failed

Additionally, and while this probably isn't causing your issue, I've noticed that you have a number of MSI Afterburner applications installed, along with a driver which is known to cause BSOD crashes according to the DRT. I would suggest removing them all and then running FRST to check for any remaining remnants:

FRST Registry Search
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Copy and paste NTIOLib_X64 into the Search box and click the Search Registry button.
4. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Hardware is not my thing, but I'm wondering whether your motherboard can fully support the Samsung 970 PRO NVMe M.2 SSD?

In the specs for your motherboard it states that the M.2 port is SATA only...
• 1 x M.2 port, supports M.2 SATA 6Gb/s module* or M.2 PCIe module up to 32Gb/s speed**
Click to expand...

The asterisks there resolve to this...
* The SATA Express port or SATA5~6 ports will be unavailable when installing the M.2 (Gen2 x2 mode) module in the M.2 port.
** Intel RST does not support PCIe M.2 SSD with Legacy ROM.
Click to expand...
...which again implies that it's a SATA port.

As I understand it (which isn't very well) an NVMe drive will run in a SATA M.2 port, but only at SATA speeds, so you're never going to be able to fully exploit the 970 Pro on that board anyway. I am wondering however, whether there is some other incompatibility between the motherboard and the 970 Pro that's causing this issue?

Later edit: Your board uses PCIe Gen3 whilst the 970 Pro is a Gen4 device. Again, it should work but at reduced speed.

Bear in mind that hardware is not my thing so this might all be rubbish!
 
Last edited:
The following script will delete those MSI services.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.



Your Stop 0x7F bugcheck was seemingly caused by Malwarebytes, please remove it completely using their removal tool for now - https://support.malwarebytes.com/hc...warebytes-using-the-Malwarebytes-Support-Tool
 

Attachments

I'm going to assume that the issue has been resolved and mark this thread as solved. Please let us know if you have any other issues.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top