Question Random Bluescreen Errors without Restarting

[Brendon90]

I've been getting frequent Blue Screens, but I'm not sure what's causing them. I have a feeling it might be the graphics card, RAM, or some outdated drivers causing issues. I've ran a few passes of memtest with no errors, and CHKDSK with no errors as well.

Some notes:

• When buying the parts back in 2014 I was told the power supply might not be powerful enough to support the CPU, graphics card, etc., but it's been working fine so far.
• I had some previous issues with the Nvidia Graphics Card Driver not being able to install properly because it would cause Blue Screens mid-way while it was installing using the express installation, but I solved that by uninstalling the driver and manually re-installing it with the "Clean" option and have been doing it that way since.
• I was reading up on some other things that could be causing it and realized dust and static electricity could be a serious problem, so I used some compressed air cans to clean it out today. It seems like it didn't work though since as soon as I booted it up there was another Blue Screen shortly after. The Blue Screens seem to be happening when using Chrome or playing games, but that might just be a coincidence.
• I've had the PC sitting under my desk ontop of a piece of hardwood (slightly bigger than the tower) that's resting on carpet, which I think may have been causing some static shocks. Now it's currently sitting on my desk as I'm writing this in safemode. It seems like safemode is free of any Blue Screens (for now), but I'd really like to know what's causing them to solve it once and for all.

The most recent errors are PAGE_FAULT_IN_NONPAGED_AREA, and MEMORY_MANAGEMENT. Previous errors were DRIVER_IRQL_NOT_LESS_OR_EQUAL, and IRQL_NOT_LESS_OR_EQUAL. Also ntoskrnl.exe seems to be the driver causing the most issues, and when the Blue Screens happen the system doesn't restart automatically.

I've uploaded the .dmp files, CPU-Z report, System Info, and a screenshot of the Blue Screen View reports on my PC here:
https://drive.google.com/open?id=1Gk09NJmODQ-YlplX5mvpN-4qbmMfjG8e

Edit: Full PC specs
CPU: Intel Core i5-4570 @ 3.2GHz, 6MB L3 Cache, 22nm
Motherboard: Gigabyte GA-Z87-D3HP Socket 1150 Intel Z87 Chipset | Dual Channel DDR3 2933(O.C.) MHz
Ram: Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz CL9 DIMMs
SSD/HDD: WD 1TB 3.5" SATA 7200RPM 64MB Hard Drive
GPU: EVGA GeForce GTX 760 w/ ACX Cooler 2GB GDDR5 | 980MHz Click, 6009 MHz Memory
PSU: Corsair Builder Series Modular CX430M 430 Watt 80 PLUS Bronze Certified Power Supply
Chassis: Corsair Carbide Series 200R Compact ATX Case Black USB3.0
OS: Microsoft Windows 7 Ultimate, Version 6.1.7601 Service Pack 1 Build 7601
Monitor: LG 24MP55HQ 23.8" IPS LED Monitor | 1920x1080, 2ms, 5M:1 | VGA, HDMI

If there's any more information or tests that are needed I can provide it asap. Any help is much appreciated.

 

[Colif]

shame ntoskrnl is slightly needed by windows, its the windows Kernel after all. It does so much its crashing is generally blamed on it.

I will ask @gardenman to convert dump files for us.

many of the bsod you mention can easily be drivers

 

[PC Tailor]

Running this through a debugger obviously shows lots of results, the majority of them show this:

Spoiler

On Thu 25/04/2019 07:55:59 your computer crashed or a problem was reported
crash dump file: 042519-15849-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88001601986)
Bugcheck code: 0x50 (0xFFFFFAA001F943D8, 0x1, 0xFFFFF88001601986, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS

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 a Microsoft module. Your system configuration may be incorrect.

Spoiler

On Sat 20/04/2019 07:26:13 your computer crashed or a problem was reported
crash dump file: 042119-22900-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93BA0)
Bugcheck code: 0x18 (0xFFFFFA8006D58730, 0xFFFFFA8007AF2D60, 0x1, 0x20000000000)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

However a small few of them we saw something pointing more to hardware:

Spoiler

On Thu 25/04/2019 07:31:54 your computer crashed or a problem was reported
crash dump file: 042519-29062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93BA0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x1364C, 0x1F02C009)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The working set free list is corrupt. This is probably a hardware error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel.

General consensus of the latter is to run memtest and check temperatures of your system. The fluctuation of causes of BSOD can often indicate a hardware error.

 

[Colif]

Hardly ever see reference by pointer error.

Gardenmans conversion can also should the drivers running at time, those reports just blame ntoskrl as usual as it is what crashed, it doesn't show why it crashed though.

1st error crashed DirectX Graphics MMS and 90% of time directX errors are GPU drivers, so try running DDU in safe mode, uninstall the nvidia drivers, and depending where you got last ones from, either get them from windows update or Nvidia - https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

 

[PC Tailor]

Will be good to see gardenman's conversion. i've done a more detailed debug run to cover all dump and posted the conclusion here as well as the underlying report - waiting for Gardenman's conversion also. As this has also pulled out realtek wireless driver errors.

__

Conclusion

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

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 430.39 , NVIDIA Corporation)
rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation )

Some Other Errors Found:
Memory Management Errors (x4)
BAD_POOL_HEADER
REFERENCE_BY_POINTER

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.

Spoiler: Detailed Dump Analysis

Detailed Crash Dump Analysis


On Fri 26/04/2019 00:05:10 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042519-16676-01.dmp
uptime: 00:01:41
This was probably caused by the following module: win32k.sys (0xFFFFF96000167F87)
Bugcheck code: 0x50 (0xFFFFFB00C0C5018C, 0x0, 0xFFFFF96000167F87, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Multi-User Win32 Driver
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 a 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 Thu 25/04/2019 08:21:46 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042519-15444-01.dmp
uptime: 00:23:37
This was probably caused by the following module: ntkrnlmp.exe (nt!MmAccessFault+0x2322)
Bugcheck code: 0x50 (0xFFFFF8800EAB06D0, 0x0, 0xFFFFF800036916AC, 0x0)
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.



On Thu 25/04/2019 07:55:59 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042519-15849-01.dmp
uptime: 00:23:06
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88001601986)
Bugcheck code: 0x50 (0xFFFFFAA001F943D8, 0x1, 0xFFFFF88001601986, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a 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 Thu 25/04/2019 07:31:54 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042519-29062-01.dmp
uptime: 00:21:10
This was probably caused by the following module: ntkrnlmp.exe (nt!MiAllocateWsle+0x28C)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x1364C, 0x1F02C009)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. The working set free list is corrupt. This is probably a hardware error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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 Thu 25/04/2019 07:09:39 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042519-16972-01.dmp
uptime: 02:22:40
This was probably caused by the following module: ntkrnlmp.exe (nt!MiAllocateWsle+0x28C)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x19C22, 0x1C73D009)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. The working set free list is corrupt. This is probably a hardware error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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 Thu 25/04/2019 03:58:05 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042419-91182-01.dmp
uptime: 00:03:55
This was probably caused by the following module: ntkrnlmp.exe (nt!MiAllocateWsle+0xF6)
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0xA89A, 0xAA9BFFFFFFFE)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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. 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 Thu 25/04/2019 01:49:27 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042419-16629-01.dmp
uptime: 02:35:10
This was probably caused by the following module: ntfs.sys (Ntfs!NtfsReleaseFcb+0x2C)
Bugcheck code: 0x50 (0xFFFFF8800A4B5B60, 0x1, 0xFFFFF800036908A6, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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.



On Mon 22/04/2019 23:01:29 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042219-56129-01.dmp
uptime: 04:22:51
This was probably caused by the following module: ntkrnlmp.exe (nt!MmAccessFault+0x6B8)
Bugcheck code: 0x50 (0xFFFFFA00038F06AC, 0x8, 0xFFFFFA00038F06AC, 0x7)
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.



On Sat 20/04/2019 07:26:13 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\042119-22900-01.dmp
uptime: 09:58:16
This was probably caused by the following module: ntkrnlmp.exe (nt!ObpCloseHandleTableEntry+0xC1)
Bugcheck code: 0x18 (0xFFFFFA8006D58730, 0xFFFFFA8007AF2D60, 0x1, 0x20000000000)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 19/04/2019 01:53:11 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041819-12542-01.dmp
uptime: 00:46:12
This was probably caused by the following module: ntkrnlmp.exe (nt!MmAccessFault+0x736)
Bugcheck code: 0x50 (0xFFFFF681003BB258, 0x0, 0xFFFFF80003660AB8, 0x5)
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.



On Fri 12/04/2019 06:37:24 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041219-60169-01.dmp
uptime: 11:49:29
This was probably caused by the following module: ntkrnlmp.exe (nt!ExFreePool+0x73E)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8011693170, 0xFFFFFA8011693170, 0xFFFFFA8007B60148)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
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. 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 Thu 11/04/2019 18:26:44 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041119-30466-01.dmp
uptime: 00:00:27
This was probably caused by the following module: ntfs.sys (Ntfs!NtfsStorageDriverCallout+0x16)
Bugcheck code: 0xD1 (0xFFFFF8800E1F3000, 0x2, 0x0, 0xFFFFF88000DBE206)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.

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.



On Thu 11/04/2019 09:18:16 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041119-22666-01.dmp
uptime: 05:16:02
This was probably caused by the following module: usbccgp.sys (0xFFFFF88007D1EF09)
Bugcheck code: 0xD1 (0xFFFFF8800E5BFB48, 0x2, 0x1, 0xFFFFF88007D1EF09)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbccgp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Common Class Generic Parent Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

The crash took place in a 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 Thu 11/04/2019 04:00:57 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041019-23774-01.dmp
uptime: 04:14:20
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmiProcessTerminationCommand+0x5F)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000365D09E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

The crash took place in a 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 Wed 10/04/2019 23:45:51 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041019-40919-01.dmp
uptime: 00:03:07
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1B5D2D)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80003645DD8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ed316ebc2bdc1c66\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 430.39
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 430.39
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
It means that a crash dump file was properly written out.
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 430.39 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL



On Wed 10/04/2019 23:41:40 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041019-48859-01.dmp
uptime: 00:59:05
This was probably caused by the following module: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000368F9C0)
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 is a software bug.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 10/04/2019 21:34:14 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041019-20857-01.dmp
uptime: 00:05:16
This was probably caused by the following module: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)
Bugcheck code: 0xA (0x41, 0x2, 0x1, 0xFFFFF80003690E88)
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 is a software bug.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 10/04/2019 07:48:23 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\041019-72852-01.dmp
uptime: 06:49:11
This was probably caused by the following module: ntkrnlmp.exe (nt!MmAccessFault+0x736)
Bugcheck code: 0x50 (0xFFFFF6810001B888, 0x0, 0xFFFFF800036BAAD8, 0x5)
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.



On Wed 10/04/2019 00:37:06 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\040919-23368-01.dmp
uptime: 00:04:26
This was probably caused by the following module: ntkrnlmp.exe (nt!KiBugCheckDispatch+0x69)
Bugcheck code: 0xA (0xFFFFF8800E9ED8A8, 0x2, 0x0, 0xFFFFF800036505F1)
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 is a software bug.

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 09/04/2019 05:51:28 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\040919-26722-01.dmp
uptime: 06:54:25
This was probably caused by the following module: rtwlane.sys (0xFFFFF8800569995D)
Bugcheck code: 0xD1 (0xFFFFF8800CD304C8, 0x2, 0x1, 0xFFFFF8800569995D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
product: Realtek PCIEWireless LAN PCI-E NIC
company: Realtek Semiconductor Corporation
description: Realtek PCIE NDIS Driverr
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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: rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation ).
Google query: rtwlane.sys Realtek Semiconductor Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


On Mon 08/04/2019 22:55:39 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\040819-19593-01.dmp
uptime: 00:11:51
This was probably caused by the following module: ntkrnlmp.exe (nt!KiGeneralProtectionFault+0x2F2)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003683D90, 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.

On Mon 08/04/2019 22:42:14 your computer crashed or a problem was reported
crash dump file: E:\Dumps to Analyse\040819-21496-01.dmp
uptime: 00:00:51
This was probably caused by the following module: ntkrnlmp.exe (nt!MiAllocateWsle+0xF6)
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x7CFA, 0x7EFBFFFFFFFE)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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. 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.

 

[gardenman]

Hi, since you provided about 15+ dumps I only ran the latest 10 since that should be enough info to get us going. Here's the info I got: https://pste.eu/p/i4D3.html

Spoiler

File information:	042519-29062-01.dmp (Apr 25 2019 - 02:31:54)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: FILF.exe)
Uptime:	0 Day(s), 0 Hour(s), 21 Min(s), and 10 Sec(s)

File information:	042519-16972-01.dmp (Apr 25 2019 - 02:09:39)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: FILF.exe)
Uptime:	0 Day(s), 2 Hour(s), 22 Min(s), and 40 Sec(s)

File information:	042519-16676-01.dmp (Apr 25 2019 - 19:05:10)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	win32k.sys (Process: WerFault.exe)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 41 Sec(s)

File information:	042519-15849-01.dmp (Apr 25 2019 - 02:55:59)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	dxgmms1.sys (Process: csrss.exe)
Uptime:	0 Day(s), 0 Hour(s), 23 Min(s), and 06 Sec(s)

File information:	042519-15444-01.dmp (Apr 25 2019 - 03:21:46)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	ntkrnlmp.exe (Process: taskmgr.exe)
Uptime:	0 Day(s), 0 Hour(s), 23 Min(s), and 37 Sec(s)

File information:	042419-91182-01.dmp (Apr 24 2019 - 22:58:05)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: Dropbox.exe)
Uptime:	0 Day(s), 0 Hour(s), 03 Min(s), and 55 Sec(s)

File information:	042419-16629-01.dmp (Apr 24 2019 - 20:49:27)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	ntkrnlmp.exe (Process: svchost.exe)
Uptime:	0 Day(s), 2 Hour(s), 35 Min(s), and 10 Sec(s)

File information:	042219-56129-01.dmp (Apr 22 2019 - 18:01:29)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	ntkrnlmp.exe (Process: svchost.exe)
Uptime:	0 Day(s), 4 Hour(s), 22 Min(s), and 51 Sec(s)

File information:	042119-22900-01.dmp (Apr 20 2019 - 02:26:13)
Bugcheck:	REFERENCE_BY_POINTER (18)
Probably caused by:	ntkrnlmp.exe (Process: Dropbox.exe)
Uptime:	0 Day(s), 9 Hour(s), 58 Min(s), and 16 Sec(s)

File information:	041819-12542-01.dmp (Apr 18 2019 - 20:53:11)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: Dropbox.exe)
Uptime:	0 Day(s), 0 Hour(s), 46 Min(s), and 12 Sec(s)

BIOS info was not included. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

well, I would have looked at lan drivers anyway based on fact some of those things that crashed are internet based applications

Jan 05 2015

rtwlane.sys

Realtek PCI-E Wireless LAN NIC NDIS driver https://www.realtek.com/en/

realtek drivers used to be easier to find than they are now. Shouldn't be so bad on a Win 7 PC though.
What wifi card are you using?

As for Nvidia, you have the latest drivers but they may not work well with a GTX 760 so I would user older ones. New drivers more for current cards, very unlikely to make a card from a few generations ago any better

 

[Brendon90]

Unfortunately I got another blue screen yesterday and here's the dump file:
https://drive.google.com/open?id=1TaaaKdVQc7Xsj5WRFzwWPEysB_ipnUHt

I noticed a lot of the blue screen dump files are around the same size. Does that mean anything? or is it just a similar type of blue screen error / dump?

Thank you guys for the detailed analysis and reports. It definitely seems like it has to do with the Graphics Card/Driver and/or the Wireless Card/Driver.

Everything is backed up now, so I'll post the results of what happens later today after I uninstall the graphics driver in DDU, install the latest one in safe mode, and update the wireless LAN driver as well if there is one. I'll also run Memtest for 10-20 passes to make sure there's nothing funny going on.

My BIOS Version/Date is: American Megatrends Inc. F2, Date: 4/17/2013
Is there more information needed than that? I'll check for a BIOS update as well since it's been a long while.

This is the model of the Wifi Card: ASUS N300 PCE-N15 PCI-Express Adapter, 300MBPS 802.11 B/G/N | Single N300 adapter | Software AP support | Graphical setup interface | Low-profile bracket included.

What should I use to track the CPU / GPU temperatures and is there anything I should note for any potential problems?
Also is there a specific update you would recommend to go back to for the Graphics driver?

 

[gardenman]

I ran the new dump file through the debugger and got the following information: https://pste.eu/p/3Hpp.html

File information:	043019-48173-01.dmp (Apr 28 2019 - 01:41:26)
Bugcheck:	NTFS_FILE_SYSTEM (24)
Probably caused by:	ntkrnlmp.exe (Process: System)
Uptime:	0 Day(s), 4 Hour(s), 40 Min(s), and 53 Sec(s)

Minidump files are always about the same size but can vary. I wouldn't worry about the size of them. The ones you have uploaded have been valid. If they were cut short they would be invalid.

Most minidumps contain BIOS info, which shows a ton of info about your system including RAM (and even RAM model numbers), CPU info and more. Not all PCs have that info available when crashing. Sometimes if they don't, updating the BIOS helps, but not always.

Memtest86 is a good idea. We usually recommend 8 passes but the more the better, it will just take longer.

Someone else can answer some of the other questions you have.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Brendon90]

I uninstalled the Wifi Card driver then downloaded and installed the latest one, but it ended up being the same.

Then I used DDU and reinstalled the latest graphics driver with a clean installation.

Finally I ran Memtest and as soon as it started it was spitting out errors everywhere. Thousands per second.

See a short video of it here:
https://drive.google.com/file/d/1xMonu_krEh3SwWBOoxI_KVVlDgf_gig2/view?usp=drivesdk

I'm not sure if I had the Memtest settings right or if it has the log files output somewhere. Does this mean I should buy new RAM, or is it an error that can be fixed?

 

[gardenman]

Ram: Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz CL9 DIMMs

So you have 2 RAM modules. With both RAM modules installed at the same time, it's hard to tell if one or both are causing the errors which is why we suggest testing 1 at a time. Try testing each one individually (in the first slot) with memtest86. If one works and the other doesn't, try using the working one by itself for a day or so to see if things clear up.

 

[Brendon90]

So you have 2 RAM modules. With both RAM modules installed at the same time, it's hard to tell if one or both are causing the errors which is why we suggest testing 1 at a time. Try testing each one individually (in the first slot) with memtest86. If one works and the other doesn't, try using the working one by itself for a day or so to see if things clear up.

Ok I didn't think of testing them 1 by 1, so I'll do that and post the results later today. Thanks!

 

[Satan-IR]

I ran the 042519-19875-01.dmp too and it points to a '1A' bugcheck which is memory corruption. So testing RAM module 1 by 1 with memtest is a good idea.

The new one 043019-48173-01.dmp show bugcheck '24' which is usually causes by corruption of bad blocks in NTFS records and such. I'd suggest you do a "SFC /scannow" (without quotes).

Bad memory would cause data corruption while in transfer between components/processes and also on storage media, hence, NTFS stop/BSOD.

I didn't run the other dumps. So a driver issue is quite possible as others have come across. Also some of those might be a byproduct of memory corruption, that is, the driver tries to write to a memory address which is problematic to begin with and it goes wrong.

 

[Colif]

inally I ran Memtest and as soon as it started it was spitting out errors everywhere. Thousands per second.

No point looking at dump files until memory is fixed. It can be cause of everything and drivers might be fine

his is the model of the Wifi Card: ASUS N300 PCE-N15 PCI-Express Adapter, 300MBPS 802.11 B/G/N | Single N300 adapter | Software AP support | Graphical setup interface | Low-profile bracket included.

You could try updating its driver from Asus though its still a 2015 driver - https://www.asus.com/au/Networking/PCEN15/HelpDesk_Download/

 

[Brendon90]

Ok I tried installing that exact driver, but I think that specific version might be for other versions of Windows. After installing it again it "updated" to the same driver that was already there.

Today I tested the first RAM stick for about 5-6 hours, 9 passes and no errors. Then as soon as I swapped in the second RAM stick the computer wouldn't even boot up. It would hum like it's powering up, then immediately shut off and constantly repeat itself in that loop. I guess that must have been the cause of the blue screens because it was sitting in slot 2 generating thousands of errors per second.

This is the memtest86 results from the first stick of RAM:
https://drive.google.com/file/d/1CITNecSSo9LoY-iaLqJZjDurMJ-XdZn7/view?usp=sharing

I'm still not sure what caused the RAM stick to go bad though, and I'm a little concerned whatever caused it might end up frying the other stick of RAM eventually. I have .dmp files from earlier from mid 2018 to 2019. Should I upload those as well?

Is any other hardware in my PC at risk for corruption or crashing because of that 1 stick of failing memory? Are there general tips, any programs, or steps I should take to prevent or fix the memory problems from happening again?

I've learned a lot so far like unplugging the power, pressing the power button to discharge current, and touching the case to get rid of static electricity before installing RAM. I am now many steps closer to solving this problem thanks to you guys.

To make sure everythings fine I will be getting some new RAM sticks tomorrow because I don't trust the one that's left. Is there any recommended size or type of RAM for the specific motherboard I have? (Gigabyte GA-Z87-D3HP Socket 1150 Intel Z87 Chipset) Ideally I'll be upgrading to 2 sticks of the biggest size it can support.

 

[Brendon90]

Also here are my BIOS settings:
https://photos.app.goo.gl/QYEGLqQ8LbJy1kSW8

I believe everything is set to default and nothing is overclocked. Is there any settings I should change?

 

[Satan-IR]

Here is the Gigabyte QVL for RAM for your motherboard. The manual says a maximum of 32GB for the 4 slots. So the slots can take 8GB modules.

You already had 1600Mhz and it worked (as it should have). You can play it safe and get two 8GB 1600Mhz which doesn't need XMP and no need for possible BIOS update which is a little risky (less risky if that's a dual BIOS motherboard which I think it is.). Or you can get two 8GB 1866 and enable XMP in BIOS.

You can also search the web for combinations of RAM people are using with this board and CPU, being an i5 might not be able to play well with some higher XMP profiles.

 

[PC Tailor]

Is any other hardware in my PC at risk for corruption or crashing because of that 1 stick of failing memory? Are there general tips, any programs, or steps I should take to prevent or fix the memory problems from happening again?

I've learned a lot so far like unplugging the power, pressing the power button to discharge current, and touching the case to get rid of static electricity before installing RAM. I am now many steps closer to solving this problem thanks to you guys.

There's not really much of a risk to your other components in this case, a faulty module will just be limited to the module, the key thing it may cause corruption to is your OS or files on your storage device. But that can usually be resolved.

Discharging any static before working on the case is just standard practice for me, it often doesn't cause an issue, but static discharge certainly can fry components. I severely doubt that it is what has caused your current module to go bad, as it happens pretty immediately after the discharge and first boot - either way most RAM have a heat shield on it that will prevent you discharging into any of the actual circuitry anyway.

I wouldn't worry about steps to prevent a module going bad, it can just be bad luck. Inappropriate overclocking can cause a module to become faulty and eliminating static discharge will simply ensure you don't damage the module or other components whilst installing it. But I doubt you did anything wrong, likely just bad luck.

To make sure everythings fine I will be getting some new RAM sticks tomorrow

Good shout, whilst your other RAM module i'm certain is absolutely fine so I don't think you need to worry about using it again, however it's good practice nonetheless to buy full new RAM modules from one pack, as mixed modules are not guaranteed to work together.

I have little doubt that your issue will go away once you replace the RAM!

 

[Brendon90]

Here is the Gigabyte QVL for RAM for your motherboard. The manual says a maximum of 32GB for the 4 slots. So the slots can take 8GB modules.

You already had 1600Mhz and it worked (as it should have). You can play it safe and get two 8GB 1600Mhz which doesn't need XMP and no need for possible BIOS update which is a little risky (less risky if that's a dual BIOS motherboard which I think it is.). Or you can get two 8GB 1866 and enable XMP in BIOS.

You can also search the web for combinations of RAM people are using with this board and CPU, being an i5 might not be able to play well with some higher XMP profiles.

Thanks for that Gigabyte QVL list I'll definitely be using it when buying the new RAM modules. I'd rather go the safe route with 2 8GB 1600MHz and not change any BIOS settings for now. Especially since you mentioned some components might not be able to handle it (like the i5).

There's not really much of a risk to your other components in this case, a faulty module will just be limited to the module, the key thing it may cause corruption to is your OS or files on your storage device. But that can usually be resolved.

Discharging any static before working on the case is just standard practice for me, it often doesn't cause an issue, but static discharge certainly can fry components. I severely doubt that it is what has caused your current module to go bad, as it happens pretty immediately after the discharge and first boot - either way most RAM have a heat shield on it that will prevent you discharging into any of the actual circuitry anyway.

I wouldn't worry about steps to prevent a module going bad, it can just be bad luck. Inappropriate overclocking can cause a module to become faulty and eliminating static discharge will simply ensure you don't damage the module or other components whilst installing it. But I doubt you did anything wrong, likely just bad luck.

Good shout, whilst your other RAM module i'm certain is absolutely fine so I don't think you need to worry about using it again, however it's good practice nonetheless to buy full new RAM modules from one pack, as mixed modules are not guaranteed to work together.

I have little doubt that your issue will go away once you replace the RAM!

That's good to know and that RAM has built in heat shields, is there any tests I should run or ways to find out if any of the OS files or my storage devices were affected by the faulty RAM? I'm thinking along the same lines since nothing that drastic has happened thankfully.

Yeah it might have been bad luck. I haven't overclocked anything so that's another worry eliminated. Thanks, I'll keep the surviving RAM as backup incase anything happens in the future. Then pick up 2 new RAM modules and install them later today or tomorrow.