For the last few days I have had a mysterious bluescreen. It outputs Stop-code 0xF4 which is just a general error "The system has rebooted without cleanly shutting down first". In the Event Viewer the error I get each Bluescreen is the same as when I cut the power to the computer abruptly (Event ID 41, Source: Kernel Power), so no help there. Once I get to the Bluescreen it refuses to write a minidump (stuck on "initializing minidump" or something like that), despite having minidumps activated. I reset the CMOS, ran Memtest for a total of 16 hours without errors, used HDTune and found no damaged sectors, ran a total virus scan with MBAM and even did a full reset of Windows 7 but the problem persists.
I just turn on my computer and it functions normally. After about 30 minutes to an hour some programs (Skype, Spotify) will stop functioning while other programs persist (Games like WoW can still be played). If you attempt to go to the Task Manager to stop or terminate the faulty programs nothing happens (Ctrl + Alt + Delete does nothing at all). After about 10 seconds a message will pop up saying "Microsoft Windows has stopped working." and it gives me the option to terminate or wait it out. Both options will lead to programs shutting down (WoW, Google Chrome, Windows Explorer (the entire taskbar)) after a few seconds which culminates in a Bluescreen.
I am just baffled by this error as it is unlike anything I have encountered. I'm not really sure what to do next and would love some advice on this. I've had the computer for a little less than two years and hadn't touched or moved the computer in the last 3 months prior to the error occuring.
Specs:
Mobo: Gigabyte 990 FXA-UD3
CPU: AMD FX-8350
GPU: Amd Radeon 6950
PSU: Corsair HX 650
HDD: Western Digital Green (ugh) 2TB
Crucial 64GB SSD (OS)
Samsung 840 128GB SSD (Games)
RAM: 16GB (4x4) Corsair 1600MHz
STOP Error 0x000000F4: CRITICAL_OBJECT_TERMINATION
STOP error 0xF4 means that a process or thread crucial to system operation has unexpectedly exited or been terminated.
You've got corruption, bro. This isn't a hardware issue, so trying to diagnose the hardware isn't going to do anything.
I don't think the STOP error is the problem. Based on the description, the error appearing would be appropriate.
Minidumps are typically useless for debugging a problem. You'd want a complete system dump, however it could be troublesome for your PC since you have so much RAM.
Kernel Power errors are only useful for determining when a PC has lost power or crashed. For example if a computer had reset overnight. These errors appear in the System log. You should also look in the Application log.
I have not personally seen this "Microsoft Windows has stopped working" error myself. What do you mean, specifically, by you "reset" Windows 7?
I have not personally seen this "Microsoft Windows has stopped working" error myself. What do you mean, specifically, by you "reset" Windows 7?
The error itself only occurs about half the time the crash occurs. It's similar to the generic message you get when a program halts or stops responding, only with the application name replaced with "Microsoft Windows". Either way, I meant that I had done a format (only of my C drive) + Reinstall of Windows.
The error itself only occurs about half the time the crash occurs. It's similar to the generic message you get when a program halts or stops responding, only with the application name replaced with "Microsoft Windows". Either way, I meant that I had done a format (only of my C drive) + Reinstall of Windows.
Chances are it says "microsoft windows" because the module faulting is ntoskrnl.exe.
I just turn on my computer and it functions normally. After about 30 minutes to an hour some programs (Skype, Spotify) will stop functioning while other programs persist (Games like WoW can still be played). If you attempt to go to the Task Manager to stop or terminate the faulty programs nothing happens (Ctrl + Alt + Delete does nothing at all). After about 10 seconds a message will pop up saying "Microsoft Windows has stopped working." and it gives me the option to terminate or wait it out. Both options will lead to programs shutting down (WoW, Google Chrome, Windows Explorer (the entire taskbar)) after a few seconds which culminates in a Bluescreen.
I am just baffled by this error as it is unlike anything I have encountered. I'm not really sure what to do next and would love some advice on this. I've had the computer for a little less than two years and hadn't touched or moved the computer in the last 3 months prior to the error occuring.
Specs:
Mobo: Gigabyte 990 FXA-UD3
CPU: AMD FX-8350
GPU: Amd Radeon 6950
PSU: Corsair HX 650
HDD: Western Digital Green (ugh) 2TB
Crucial 64GB SSD (OS)
Samsung 840 128GB SSD (Games)
RAM: 16GB (4x4) Corsair 1600MHz
You've got corruption, bro. This isn't a hardware issue, so trying to diagnose the hardware isn't going to do anything.
Minidumps are typically useless for debugging a problem. You'd want a complete system dump, however it could be troublesome for your PC since you have so much RAM.
Kernel Power errors are only useful for determining when a PC has lost power or crashed. For example if a computer had reset overnight. These errors appear in the System log. You should also look in the Application log.
I have not personally seen this "Microsoft Windows has stopped working" error myself. What do you mean, specifically, by you "reset" Windows 7?
Would there be any way to pinpoint what exactly is corrupted or would it be easier to just do a full format of all my drives?
The error itself only occurs about half the time the crash occurs. It's similar to the generic message you get when a program halts or stops responding, only with the application name replaced with "Microsoft Windows". Either way, I meant that I had done a format (only of my C drive) + Reinstall of Windows.
Call a tech.
The STOP is the problem, a critical system process was terminated unexpectedly, causing the system to lockup/bluescreen.
100% false.
A complete dump is a complete waste 90% of the time.
Which is what it is showing, that he held the power button down to reset the PC......
He said he already did this, this wouldn't be something written to these logs.
It happens when a critical system process is terminated unexpectedly, or crashes.
......... Like what the STOP error indicates. z_z
Chances are it says "microsoft windows" because the module faulting is ntoskrnl.exe.
https://en.wikipedia.org/wiki/Ntoskrnl.exe
If so, good luck troubleshooting that one without hours and hours worth of time.
Call a tech.