Random BSODs, mostly memory management issues?

[robotgopher]

Forgive me if I make any mistakes or break any forum rules, this is my first time posting here.

My roommate has had this issue for a while now. Randomly, while he is either gaming or just surfing the internet, his PC will crash with a BSOD. More often than not, it is the "memory management" issue, but on occasion he will receive an error with "DRIVER_IRQL_NOT_LESS_OR_EQUAL", and one additional one (which hasn't appeared for a while, he is having trouble remembering exactly what it was).

Specs:

• 
  CPU: i4-3770K @ 3.50GHz
  MEM: Corsair Vengence Pro 16GB 2400 MHz
  MOBO: ASRock Z77 Extreme4
  GPU: Nvidia GeForce GTX 970

Solutions we have tried:

• 
  Motherboard BIOS and other Drivers up-to-date.
  
  Running Memtest86 & Windows Memory Diagnostic Tool has returned no errors.
  
  Running sfc /scannow has returned no issues.
  
  It was mentioned in a comment by Ernst Zimmer here that the page file should be moved to a different partition, as he has Windows 10 loaded onto a SSD and his other programs and files on a HDD. However, we are unable to shrink the C: partition, and can't figure out why. Moved page file to a separate hard drive.

Minidump Files from yesterday's crashes.

We have tried other solutions but I'm forgetting them at the moment, I will update this when I remember them.

If there is anything I missed please let me know. He has encountered 5 BSODs just today as of writing this post. Any help or advice you can offer is greatly appreciated.

 

[Laptop_Nerd]

Hi,

Please do try these troubleshooting steps that may help.
- First, go to Device Manager and uninstall the graphics driver.
- Next is to open Programs and Features then uninstall anything related to the graphics card.
- Once uninstalled, download and install the latest driver.
- Reboot the laptop once the latest driver has been installed.
- If all these will not work last option would be to reinstall Windows.

 

[robotgopher]

Hi,

Please do try these troubleshooting steps that may help.
- First, go to Device Manager and uninstall the graphics driver.
- Next is to open Programs and Features then uninstall anything related to the graphics card.
- Once uninstalled, download and install the latest driver.
- Reboot the laptop once the latest driver has been installed.

Thanks for the response. Gave that a try, still experiencing the issue. We're trying to hold off on re-installing windows 10 until we've exhausted everything.

Also I'm updating the original post, hopefully including some minidump files.

 

[Colif]

try running driver booster and confirm the drivers you have are the latest. Motherboard makers can be slow to upgrade some parts.

download and run http://www.resplendence.com/whocrashed
it will look at error logs and give us a summary of the errors
might point out culprit but normally points at windows... will at least show us all error names

copy/paste results in here.

 

[robotgopher]

try running driver booster and confirm the drivers you have are the latest. Motherboard makers can be slow to upgrade some parts.

download and run http://www.resplendence.com/whocrashed
it will look at error logs and give us a summary of the errors
might point out culprit but normally points at windows... will at least show us all error names

copy/paste results in here.

Wow, I like this much more than BlueScreenView...

Output:

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 5/27/2016 7:08:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052716-18078-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF5801896976C, 0x2, 0x1, 0xFFFFF801808407D5)
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.
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 5/27/2016 7:21:48 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052716-20953-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFlushVolume+0x36A)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80181CAB79A, 0xFFFFD00025145EE8, 0xFFFFD00025145700)
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 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.



On Thu 5/26/2016 6:30:00 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052616-20250-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF6810DEEB748, 0x3, 0x2)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 5/26/2016 6:27:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052616-17843-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x2F65F0, 0x2, 0x80002F0002F3997)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 5/26/2016 7:27:48 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052616-5906-02.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFlushVolume+0x36A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000270B79A, 0xFFFFD00021C3E930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 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.



On Thu 5/26/2016 7:04:00 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052616-5906-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF580188847DC, 0x2, 0x1, 0xFFFFF80053644A18)
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.
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 5/26/2016 5:53:08 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052516-6375-01.dmp
This was probably caused by the following module: ci.dll (CI!MinCrypK_TrimMemory+0xC9)
Bugcheck code: 0x50 (0xFFFFF6FB40000020, 0x0, 0x0, 0x6)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
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 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.



On Thu 5/26/2016 5:27:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052516-6406-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF5801890675C, 0x2, 0x1, 0xFFFFF800666567D5)
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.
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 5/26/2016 4:38:00 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052516-6593-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6808C9A97C8, 0x800000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 5/26/2016 3:53:00 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\052516-6531-02.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41284, 0x58D2C000, 0x227F, 0xFFFFF58010804000)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

50 crash dumps have been found and analyzed. Only 10 are included in this report. 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 368.22 , 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.

 

[Colif]

Have you got Alcohol CD & DVD burner installed on pc? http://www.file.net/process/ci.dll.html

its odd it mentioned the Nvidia driver in the conclusion but not in any of the 10 dumps included.

Almost all the files in the reports are part of windows, ntkrnlmp.exe is the Kernal & NTFS is the file system. They don't offer a clue as to whats causing them using whocrashed, will need someone who can read logs to investigate further.