I've currently got this issue which is killing me slowly. Last week my computer started randomly shutting off (BSOD), I initially saw it as a driver issue so I restored my computer to factory new. It was working for a couple of days and the issue occurred again, I thought Windows Update was the culprit so I stopped updates all together to see if it was and to no avail, computer keeps BSOD'ing five minutes after startup.
I constantly browse this forum for tips, lurking about in the topics because this is the "go-to place" to get any sort of help or community. Now, I'm writing to you while in Safe Mode as I can't access windows normally without it imminently crashing. I've tried running memory diagnostics, system file diagnostics and nothing worked.
I also enabled crash dumps to be created but none ever do. The BSOD always says initializing memory dump (or something like that) and never created it where the default spot is suppose to be. Any solutions to getting that? As 9/10 you guys will probably need.
I've luckily written down the code that popped up. Any to all help is appreciated guys.
Try to reset your bios by removing the bios battery on your motherboard. Best, replace that battery with a new one 2032 size. Also try to set the memory paging in auto.
Here is how to do this:
1. Right click on Computer.
2. Click on Properties.
3. Click on Advanced System Settings.
4. Click on settings in Performance under Advanced Tab.
5. Click on Advanced Tab in Performance Options Window.
6. Click on Change.
7. Uncheck “automatically manage Paging File size for all drives”.
8. Select C:/drive.
9. Select “System Managed Size”.
10. Click Set.
11. Click OK.
12. Now restart the computer when it prompts for a restart.
The location of the crash dump is user specified. (make sure there is room on the drive)
try to locate the crash dump files
dir /s *.dmp
this will search your hard drive looking for your memory dump(s) and tell you its location.
it may be in
c:\windows\minidump (but it can be in other locations)
The error code 0x000000F4 is basically a critical process terminated.
This can happen because of file corruption or often malware.
You would want to start cmd.exe as a admin then run:
chkdsk /s /f (on you drives, to fix any file system corruption caused by various issues)
sfc.exe /scannow (this will check your core windows files for corruption)
after you do this you would then run a full malwarebytes scan
if you still have problems you would then locate and have someone look at the memory dump produced by the bugcheck.
(assume you work out why you don't see one, various causes for that ( look in wrong location, drive full, connection to drive failed and did not reconnect would be the most common. To fix a failed connection you try and move the connector to another port, or enable hotswap in your BIOS if you have that setting.