Memory errors and PC not booting, Windows 10, SSD

[Frozenassets]

Hello, long time reader, brand new member.

I played this PC repair roulette a few years back on my last build and got it wrong. Rather not go down that road again if avoidable. For a couple months I've had 1 of 2 things happen randomly and a 3rd oddity thrown in for good measure.

1: Game crashes but Windows is ok, get a "memory could not be read/written" error.

2: Windows crashes entirely, usually get the Windows screen saying shit went south and it's taking a dump and will let me know when it's ready for me to wipe.

3: Sometimes for completely unknown reasons the Cortana search is unclickable as well as the start menu. Sometimes it disappears entirely.

A couple weeks back I had enough so I formatted the disk and reinstalled Windows. Problems did not go away. Tonight the PC crashed and would not post, would get to the Windows screen and shut off entirely, no errors. Indicator lights on the board have power but she's off. I did this 3-4 times with the same result. I took my PC apart and put everything back together, moving the 2 DDR modules to new slots and the Sata devices to new ports as well for good measure. This time it boots straight into the BIOS but everything looks corrupt.....shit. I power off/on a few times and finally it comes up and here I am, on the PC in question Wondering WTH is wrong.

My original thoughts due to the errors were SSD or Ram and I ran diags on both which came back clean. That said how likely would it be that bad ram or a bad disk would cause the PC to just power off without error? I'm leaning towards motherboard but that's exactly what I replaced on my last build and was the wrong answer.

Possible Culprits in order of likely-hood (IMO)

Motherboard - Symptoms all fit the MO

CPU - Same as above, if the CPU fails should the PC power off entirely or should it stay
powered on but throw some error beeps?

Ram - Can ram cause it to power off during post?

SSD - Can SSD cause it to power off during post?

Power Supply - Should be more random and without Windows crash screens....right? Couldn't get it to post at all for a time tonight, now it seems ok.

Thanks all!

 

[Colif]

run http://www.memtest86.com/ free version on your ram, it creates a bootable USB so you don't need windows. You want 0 errors

are you still getting bsod? download and run who crashed: http://www.resplendence.com/whocrashed
it creates a summary of the errors and might show a driver name

copy/paste results here

 

[Frozenassets]

I had to wait a few days to get a crash but it's happened 3 times today, the report registered 2 crashes Thursday but I don't recall those, may have happened when I was AFK. Memtest came back 100% clean. I've recently started play WoW again and I crash out of the game semi-often but the problem pre-dates WoW.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 11/26/2016 7:52:54 PM your computer crashed
crash dump file: C:\Windows\Minidump\112616-6437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xEF (0xFFFFBB81A125B800, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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 11/26/2016 7:52:54 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)
Bugcheck code: 0xEF (0xFFFFBB81A125B800, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED



On Sat 11/26/2016 5:56:22 PM your computer crashed
crash dump file: C:\Windows\Minidump\112616-7796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x1A (0x41201, 0xFFFFF400596C3580, 0xE6400001B62EA867, 0xFFFF898DB7EBE9E0)
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 Thu 11/17/2016 10:21:38 PM your computer crashed
crash dump file: C:\Windows\Minidump\111716-5984-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFFB1E02F5910F9)
Bugcheck code: 0x109 (0xA39FF2E544319973, 0xB3B6FF6B96B4BC11, 0xFFFFB1E02F5910F9, 0x1E)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 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 11/17/2016 7:24:11 PM your computer crashed
crash dump file: C:\Windows\Minidump\111716-6078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xEF (0xFFFFBA82808BD800, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

All of the processes mentioned are parts of windows, many times when a driver asks a windows process to do something, the error will occur on the windows side of the transaction.
ntoskrnl = heart of windows, it manages memory and driver requests. Gets blamed for lots of things

They can all driver errors

I think the CRITICAL_STRUCTURE_CORRUPTION might be caused by your graphics drivers only cause win32kfull.sys is associated with the desktop, try doing this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

Memory Management can be drivers or ram, so try running the free version of http://www.memtest86.com/ on your ram sticks, 1 stick at a time.

 

[Frozenassets]

I've ran memtest86 a couple times booting from USB, not on 1 stick at a time however, the test takes a couple hours to run and has come back without errors each time. Is there value in doing 1 at a time if I repeatedly get no errors on both?

Had 2 more crashes today

On Sun 11/27/2016 12:13:10 PM your computer crashed
crash dump file: C:\Windows\Minidump\112716-6093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFF8C80418EC190, 0xFFFF8C80418EC0E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 11/27/2016 12:13:10 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidMmInterface+0x4D4F7)
Bugcheck code: 0x139 (0x3, 0xFFFF8C80418EC190, 0xFFFF8C80418EC0E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
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.

I may be having a mix of issues. When playing WoW I tend to crash when I zone or if I was afk and come back to the game. Those types of transitions. Also, when using the web I can see flash based windows slow to crawl if I have more than 5 tabs open and I know from experience that if I don't close a couple I will crash with a memory error. I have 8GB of ram and a clean install of Windows, disk was formatted.

I'll try clean graphics install and see what that does. I have an older graphics card lying around. Could always swap that and see what happens as WoW is not very intensive to run anyway.

If that fails I'm leaning towards buying a cheap 1155 board and ram to hobble along until the spring. Planning on a rig that can handle VR for 2017 so want to wait for the next gen and not hop on board at the tail end of a gen.

Thanks for your assistance thus far!

 

[Colif]

The last crash listed above is Direct X. If you notice, the two listed happened at exact same time, Whocrashed seems to do that when it only has 1 error to report, its shown both sides of the error which I wish it did for every error.

This should be fixed if you swap graphics drivers like you said you were going to.

 

[Frozenassets]

I went through the steps and installed a clean driver. Crashed again this evening. I'm pretty convinced it's hardware and I'm leaning towards ram. As I've mentioned I've done a complete wipe of Windows and installed all brand new drivers and it did nothing to help the issue. I can suffer along with 1 DIMM for a few days and see what happens.

Will advise but if you have any further suggestions I am open to them.

On Sun 11/27/2016 6:47:54 PM your computer crashed
crash dump file: C:\Windows\Minidump\112716-6171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x4E (0x99, 0x1D6013, 0x2, 0x200001000015192)
Error: PFN_LIST_CORRUPT
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 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 Sun 11/27/2016 6:47:54 PM 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: 0x4E (0x99, 0x1D6013, 0x2, 0x200001000015192)
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.

 

[Colif]

PFN list corruption is a ram error but as description suggests, its not hardware... both sides of error blame windows though - ntoskrnl & ntkrimp are both parts of the kernel, which really doesn't help me.

Have a read of this and follow its instructions - use who crashed to look at the erorrs it produces as it should BSOD, that is its purpose: http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

 

[Frozenassets]

I've been running 3 days on 1 DIMM with no crashes. Wow itself has crashed once but no Windows crashes. Going to keep running this way for a few more days then swap the other DIMM as I'd LOVE to get a positive confirmation of a bad DIMM.

 

[Frozenassets]

I should not have updated my post.....

This is a different error though than the others.

On Thu 12/1/2016 7:26:46 PM your computer crashed
crash dump file: C:\Windows\Minidump\120116-6578-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x18C994)
Bugcheck code: 0x7F (0x8, 0xFFFFC5816B52DB30, 0x6C3B379D, 0xFFFFF80758CCC994)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\System32\DriverStore\FileRepository\c0307329.inf_amd64_55b6bd3e40065979\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. UNEXPECTED_KERNEL_MODE_TRAP



On Thu 12/1/2016 7:26:46 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x18C994)
Bugcheck code: 0x7F (0x8, 0xFFFFC5816B52DB30, 0x6C3B379D, 0xFFFFF80758CCC994)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\System32\DriverStore\FileRepository\c0307329.inf_amd64_55b6bd3e40065979\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. UNEXPECTED_KERNEL_MODE_TRAP

 

[Colif]

atikmdag = Radeon drivers. did you clean install them before?

If not, try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

 

[Frozenassets]

Yes, am painfully aware of ATI driver errors. I did do the clean install.

I've swapped the DIMM but am prepared to call that particular crash a "one of" as it's the first time I've seen a crash related to m ATI drivers in months.

Will give if some more time and see what happens with the 2nd DIMM.

 

[Colif]

I didn't know Intel CPU's create traps...

The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

This trap could be a bound trap (a trap the kernel is not permitted to catch) or a double fault (a fault that occurred while processing an earlier fault, which always results in a system failure).

0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

1. A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
2. A hardware problem.

Cause

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed.

error description

hmm, wish i had looked at that before assuming it was the GPU. it could still be ram.

 

[Colif]

i wonder if i am looking in wrong place, I don't know for sure if its ram or maybe the GPU itself. You could run http://www.ozone3d.net/benchmarks/fur/ on GPU and see if it causes any BSOD,

i feel like we not getting anywhere.

 

[Frozenassets]

Well the good news is I can rule out bad memory and bad video card as I have 2 of each.

I'm running on the 2nd DIMM right now and will continue to do so for the next little while. Have family in this weekend so won't really be able to give it a proper test until next week.

If it crashes again (also have to consider that I'm running games in windowed mode AND running multiple Chrome tabs on 4GB of ram) then I'll swap in my older video card which is still perfectly ok to run WoW.

I appreciate your help and I'll provide an update next week.

 

[Frozenassets]

So good news and bad news. Good news is I've ran a week on 1 DIMM and 0 crashes.

Bad news is that starting last night my disk usage quickly pegs at 100% even if I'm not running anything. I disabled caching to ensure it wasn't due to the low ram but it doesn't make a difference. I've tried all the suggestions recommended in other threads to no avail which include but not limited to:

Disabled Superfetch
Disabled Windows Search
Disabled BITS
Disabled Message Signaled Interrupt

That said if I boot into safe mode disk usage is ok.

I'm starting to believe in a higher power and that higher power wants me to build a new PC. AMD event is in 2 days, let's hope for a launch before Christmas!

I may just add new ram and reimage (again)

 

[Colif]

i hadn't asked you to do this before cause I can't read the error logs, but i seen someone around recently who can and who just maybe might look at them for you if we lucky.

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

might help figure out latest thing too.

 

[Frozenassets]

Hiya, an update, a good one I think......

Subsequent to my last update I bought new ram. 2X4. Put both modules in and....crash crash crash. Couldn't get the system stable enough to run Whocrashed. Switched the same 2 modules to the other banks, no change, still crashing like crazy. So my ram was ok but if I have 2 DIMM's in things go haywire.......I eventually did run Whocrashed and the error was that it seems like it was a config issue, not software or hardware. One thing I hadn't tried was to update my Bios, reason being that my Bios settings haven't changed in years. Flashed Bios/reset Bios settings to default/rebooted and she's been stable as a rock since and I had a game running the entire day yesterday while running Chrome tabs with constant 70-80% memory usage and no issues.

Not sure what changed but something in my system changed that the Bios didn't like and it reacted violently.

As long as she remains stable for a few more days I'll mark this as closed. Thank you for your time!

 

[Colif]

New BIOS can support newer hardware that may not have existed at time 1st bios was made, also support drivers better too that may need features not in original bios.

 

[Frozenassets]

Been running error free for a couple days now with all 4 DIMM's in so it's safe to say the issue is resolved. I even managed to double my ram!

Thanks for your timely help