Windows 10 BSOD Multiple Errors For RAM, SSD, and now nVidia Graphics.

Toggle sidebar Toggle sidebar
T

TheMattman

Prominent
Apr 7, 2017
4
0
510
Hey y'all,

So about 2 days ago I started getting BSOD. Initially I thought it was related to a graphical fix I downloaded for Nier Automata, but it very quickly started crashing regardless, and now will barely last 10 seconds after logging in before crashing. Let me give you a rough timeline of the different BSOD errors and the fixes I tried.

- dpc watchdog violation
- pfn list corrupt
tried chkdsk, "did it instantly" on restart, nothing seemed wrong
- irql not less or equal to
tried resetting windows w/ keeping files, "did it instantly" again
- a few rounds of system service exception (ntfs.sys) and the kernal ntfs error (forgot the exact name)
updated the driver(s) for my SSD
- memory management
- bad pool header
removed one of my RAM sticks
- nvlddmkm.sys

The fact that 3 different components are getting errors makes me think that either a) windows' driver manager went haywire, or b) something hardware-based like power distribution has been messed up. Malwarebites came up clean and my bios seems to be working fine. I would use something like memtest or do a full Whocrashed dump, but my computer crashes too quickly.

I'm currently doing another keep-my-files reset and it's actually working this time. However, it's been stuck on C: Scanning and Repair 100% for like 10 mins now.

Any suggestions or hints would be appreciated. Thanks!
 
Sort by date Sort by votes
do you have who crashed installed?

how about we try safe mode
on the 1st login screen, where you click a kewy to bring up login box, click the power icon
before pressing anything else, hold shift key & click restart
this loads advanced start up
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
PC will restart and load safe mode

run who crashed & click file/export and save a html image of the report to your hdd or a USB device to upload here and share with us.

also, do this to fix the GPU drivers: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

Memtest86 creates a bootable USB, create it on another PC and boot into it on your PC and check sticks, 1 stick at a time
 
Upvote 0 Downvote


So I ran memtest and it didn't see any issues with my sticks. Also, finally managed to get Safe Mode working long enough to get a Who Crashed report off my computer (was even crashing in Safe Mode, though had networking also on).

Here it is (don't know how to import a web page here so just copied the text over):

************************************************************************************************

System Information (local)

Computer name: MATT_TOWER
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASRock, Z87 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17106829312 bytes total



Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 4/7/2017 5:30:05 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\040717-55812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x41201, 0xFFFF813FFFA87B10, 0x21, 0xFFFFA68776367010)
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.
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. 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 Fri 4/7/2017 5:30:05 AM 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: 0x1A (0x41201, 0xFFFF813FFFA87B10, 0x21, 0xFFFFA68776367010)
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. 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 Fri 4/7/2017 4:17:59 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\040717-58953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x41284, 0x9D72000, 0x0, 0xFFFF9E8010804310)
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.
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. 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 Fri 4/7/2017 3:58:45 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\040717-58906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x41793, 0xFFFF953FFFEFCD90, 0x28, 0x27)
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.
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. 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 Fri 4/7/2017 2:27:50 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\040717-59109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x5003, 0xFFFFC68010804310, 0x12F3, 0x12F500025E7)
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.
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. 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.




Conclusion

30 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

**********************************************************************************************************************

I'd like to add that a lot of previous BSOD crashes had different error messages (like the ones described in the OP).
 
Upvote 0 Downvote


or in other words, Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)


unless Paul needs entire dump?

if it crashes in safe mode, usually a sign its not drivers.
 
Upvote 0 Downvote


Ok so I set up those settings, but it didn't create a Small memory dump file after I hit Ok (all of the old 400-500 KB files from all of the crashes are in there though). Do I need to make it BSOD again?

Also it doesn't crash in base Safe Mode, I think it was because I had Safe Mode with networking turned on, and that caused it to crash.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom