[SOLVED] Lately I've been getting tons of BSOD's .. these 4 only in the last 5 minutes .. could someone take a look at the .dmp files?

Solution
I wouldn't have blamed GPU right away based on not getting error with it not inside, I sort of guessed the Nvidia errors would stop since the card wasn't in. I would have suggested you try GPU in another PC and see if it had same problems.

4 x 8gb sets are specially picked to work with each other, the more sticks you try to get to work together, the harder it becomes. The current pairs of sticks might be fine in 2 x 8gb mode but slight differences is all it takes when you try top match 4. Sticks aren't damaged, hence no ram errors. its more a case of a slight little difference somewhere.

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

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sat 2/2/2019 1:30:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x7EA9)
Bugcheck code: 0x1 (0x7FFD596AFD34, 0x0, 0xFFFF, 0xFFFFA984D323FA80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 2/2/2019 1:27:08 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020219-5343-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF805EBD8B519)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF805EBD8B519, 0xFFFF83852CC3EA28, 0xFFFF83852CC3E270)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 417.71
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 417.71
Bug check description: This indicates that a system thread 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 417.71 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 2/2/2019 12:50:03 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020219-5593-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8036018041D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8036018041D, 0xFFFFFFFFFFFFFFFF, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\020219-5468-01.dmp
C:\Windows\Minidump\020219-5578-01.dmp




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

5 crash dumps have been found and analyzed. Only 3 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 417.71 , NVIDIA 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.
 
Top 2 errors could be caused by Nvidia drivers (since one mentions them). Try running DDU and reinstall GPU drivers - http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

last one isn't so clear, I will get someone to convert dump files into format i can read, it will show what drivers were running at time. His reply might look similar to who crashed output but the pastefile he attaches shows more info that could help.
 
i used DDU then installed windows 10 pro 1709 (i was on 1809) then installed an older nvidia driver (417.22) and after few minutes i got another bsod ... dump file says it's the nvidia driver again
 
you could try running ddu again, and instead of getting drivers from Nvidia, try windows update and let it find drivers for card. They aren't the newest but more stable generally

I can't tell what PC you have so can you give us some details of PC? The dump will show some of it, but not all.
 
both drives are on the latest firmware + chkdsk shows no error. also ran windows memory diagnostic to be sure the RAM is ok and no errors were detected during that or during stress testing with aida64
 
i went for 2 months with my Nvidia drivers randomly turning off, we threw multiple drivers at it, reinstalled windows with 2 different versions of 10, stress tested PC for 48 hours using AIDA... one advantage (if you can call it one) is you are getting BSOD. I wish mine had been as I could have worked that out. Mine ended up being caused by my mouse. I am not sure how but replacing mouse stopped the errors...

You could try running memtesst86 on each of your ram sticks, one stick at a time, up to 8 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

The windows memory tester isn't always accurate. Ram could be reason the nvidia drivers keep failing.

in a few hours my friend might reply unless he is snowed in.
 
another bsod

On Sat 2/2/2019 6:07:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020219-4734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1637D0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8001E1743E7, 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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 2/2/2019 6:07:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0xD65B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8001E1743E7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

3 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 391.35 , NVIDIA Corporation)

https://drive.google.com/open?id=1iIFy4yCzn-PnvfgOiUa1SpWCM-z8u1e8
 
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/Sr7t.html

File: 020219-5593-01.dmp (Feb 2 2019 - 05:50:03)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: MsMpEng.exe)
Uptime: 1 Day(s), 19 Hour(s), 11 Min(s), and 40 Sec(s)

File: 020219-5343-01.dmp (Feb 2 2019 - 06:27:08)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 16 Sec(s)

File: 020219-4734-01.dmp (Feb 2 2019 - 11:07:24)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: Steam.exe)
Uptime: 0 Day(s), 0 Hour(s), 27 Min(s), and 07 Sec(s)

The following dump files were 0 bytes long which means they are invalid:
020219-5578-01.dmp
020219-5468-01.dmp
The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)
The overclocking driver "IOCBios2.sys" was found on your system.(Intel Extreme Tuning Utility)
The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Motherboard: https://www.asus.com/us/Motherboards/ROG-MAXIMUS-X-HERO/
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.
 
Did you grab these drivers after the BSOD happened?

I went to https://www.asus.com/us/Motherboards/ROG-MAXIMUS-X-HERO... and downloaded & updated the following : bios , chipset , LAN , SATA
as your previous LAN drivers were from 2016 and the newest on motherboard web site are from 2018

One error crasshed Defender, the last crashed Steam, makes me think the cause is a LAN driver.

Have you run any AV Scans as I am not 100% sure what smrtkrnl.sys is, I can only find 1 reference to it here: https://threatinfo.net/certificates/Eikonect%2BSoftware%2BSL%253BMicrosoft%2BWindows%2BHardware%2BCompatibility%2BPublisher - something to do with web pages? http://www.eikonect.com/

So GPU is working now? I would have removed Afterburner and seen if maybe some of its settings were reason newer drivers wouldn't install.
Intel extreme tuning and AI Suite generally cause different errors.
 
I had a thought that it might be GPU itself, its just it lets you install drivers and then crashes. A lot of time, if the cause is the actual GPU itself, the drivers can't recognise the card and refuse to install.. its why i didn't suggest it. One way to see if it is the card is install it in another PC and see if you have same problems.
 
I really hope it's not the GPU since I'm not gonna be able to afford anything else right now and I have no way to test it in another PC. The one that had something to do with web pages - before 2 bsod's I was browsing chrome and some random tabs i had open went offline like i had no internet then after a few seconds bsod. Since I got this mobo in 2017 i never updated the LAN driver and never had issues up until december 2018. I haven't ran any AV scans since I use only windows defender since it got quite good lately but I will do a full scan with malwarebytes anyway. I have removed afterburner and turned off XMP for now since i read that it was causing bsod for many people but now i need an alternative otherwise I can't play anything without my gpu overheating .. you think GPU Tweak II is ok?
 

TRENDING THREADS