....Before the blue screen happened spammed with errors that say "The instruction at 0x00000006EDFC00 referenced memory at 0x00000004EDF5C00. The memory could not be writted. Click OK to terminate the program" and the box is WerFault.exe - Application error
The fact that an area of RAM could not be written to suggests that either the RAM is bad, the SSD/HDD (whichever your OS is installed onto; could be the non-OS drive too) is failing/failed or an underlying piece of hardware that affects RAM's ability to hold kernel code is bad. The latter includes PSU, mobo, etc...
I tried wiping both my SSD and HDD and reinstalled windows, that didn't fix it. I took out each drive indivisually to see if it was a hdd or ssd problem, and reinstalled windows again. that didn't fix it. I also ran memtest through windows on each stick indivisually and they both passed with 0 errors.
Go to the SSD manufacturer's support site and make sure that you have the latest firmware installed.
Re-run memtest86+ one stick at a time; alternate the slots. It is time consuming, but must be done.
https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html
I talked to a microsoft support rep and they tried having be boot to lgkc and it said critical process died with a blue screen then we tried to use recovery mode and it blue screen crashed again. I tried reinstalling windows and after it installed it restarted and gave me a blue screen again. I've tried swapping around the RAM in different slots and when I removed a single stick it actually let me into the OS for the first time but after 10 minutes of me screwing around on my desktop it blue screen crashed again.
That is a bugcheck 0xf4 BSOD (critical process unexpectedly and suddenly terminated) -- and is almost always caused by a problem with the hard drive. Check that SSD firmware.
Run SeaTools for DOS on the HDD -
https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics-ssd-test.html
Try this on the SSD -
https://www.sysnative.com/forums/ha...drive-hdd-diagnostics-ssd-test.html#post97972
I really would like for you to reinstall Windows onto the SSD only (meaning -- remove the HDD during installation) as Windows places a small hidden partition on non-OS attached drives during installation (so you cannot just remove the internal HDD at this time). Having only the SSD to deal with would help us here - at least a little. Any future error messages that refers to the internal drive would then have to involve the SSD. Also, it would certainly assure us that the HDD is not involved in your system issues.
The windows rep said that my OS stick could be corrupted so I installed a windows10 version that he gave me onto a flash drive and it still gave me a blue screen with the same error code after installed. I ran CHKDSK through the CMD and it came up with errors on my HDD but it fixed them after a scan and I still get a BSOD.
"OS Stick" - ? No idea what the rep is referring to. Assuming the rep was speaking of a RAM stick, saying that 1 stick (the "OS Stick) could contain OS corruption is simply asinine. The OS can be loaded across RAM sticks. Furthermore, if Windows detected kernel corruption it would BSOD your system immediately and likely with a
0X109 bugcheck = CRITICAL_STRUCTURE_CORRUPTION.
I'd like to see the chkdsk report if you can find it. It is in the Event Viewer Application log.
Bring up the Event Viewer; find the CHKDSK report -
WIN key | type eventvwr.msc | expand "Windows Logs" | select "Application" log | click on "FIND" on the right side | enter chkdskinto the search box | when chkdsk event is found, highlight the event line up top (left-click on it 1x) | to the right of "COPY" (on the right side) there is a little arrow - click on it and select "Copy Details as Text" | Paste them into your next post using CODE brackets, if possible (click on the pound sign (#) in the post reply menu; paste the chkdsk info between them (doing so will keep the spacing)
Once a hard drive shows errors, the best course of action is to replace it as new bad sectors will inevitably pop up; the errors go on and on.
Regards. . .
jcgriff2
