[hoosierdaddy68]

Randomly and without warning, my piece of crap Gateway that I severely overpaid for will go into a BSOD. No drivers, system files mentioned, just the following


STOP Ox000000F4 (0x0000000000000003, 0xFFFFFA800E4B4060, 0xFFFFFA800E4B4340, 0xFFFFF80003590240). I don't think it ever writes a thing to memory, because I can't seem to find a dump file.

Does anyone have a clue?

[TheSystemWizard]

Download and install the free edition of WhoCrashed
Link: http://www.resplendence.com/whocrashed

Launch the application and click the analyze button and it will analyze the crash dumps created from the Blue Screens. Then Scroll down to the Analysis section and you can work out what driver (if any - it COULD be a hardware error) is causing the problems. If you are having a hard time figuring out the information listed in the analysis section just post the results here and I'll help you.


The crash dumps are located in C:\Windows\Minidump
Also makes sure you've enabled crash dumps. WhoCrashed will also tell you if you have it enabled or not.

[rainforest123]

Please see:
Hello & welcome to tech guy forum.

http://aumha.org/a/stop.htm

The 0XF4:CRITICAL_OBJECT_TERMINATION is a tough one. It means that something critical to the system operation has stopped working and terminated the system. Unfortunately, this cryptic message has a myriad of causes that can be resolved by looking carefully at the history of the system and removing things accordingly.

When did the problem begin?
Did the computer have a different OS? If so, which?

Have you run diags on the ram, HDD & cpu?

When does the error appear?

Strip down the PC to:
mouse, monitor, keyboard
motherboard, cpu, ram, HDD
power supply

RF123

[hoosierdaddy68]

I added a new Western Digital 2 TB hard drive, and it's only a week or two old. I had not seen the error before then.

The only thing I've done diags on is the memory using memtestx86 v2.11. It took 2 hours but ran a pass on all 12GB of memory and said it passed.

Hard to believe that a new hard drive would randomly cause these errors. It is odd as to how it happens. One time I just turned it on and never logged on (I have kids to chase). Then when I finally got around to getting back to my PC, the BSOD was sitting there (I make sure it doesn't automatically restart). Yesterday, it worked fine for what seemed hours, and immediately after playing a PC game, there it showed up.

Don't know if that'll help diagnose the issue. Thanks for the reply.

[hoosierdaddy68]

TheSystemWizard,

That's the thing...I checked the C:\windows\minidump folder and it contained no files.

[rainforest123]

h :

http://www.google.com/search?hl=en&c...+to%22&spell=1

Configure the dump type
To configure startup and recovery options to use the small memory dump file, follow these steps.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. In the Write debugging information list, click Small memory dump (64k).

To change the folder location for the small memory dump files, type a new path in the Dump File box (or in the Small dump directory box, depending on your version of Windows).
http://support.microsoft.com/kb/315263

You may need to set your computer to show [ unhide ] hidden, system & protected OS files. If you don't know how to do so, kindly ask us.
Hint: control panel [ classic view ] > folder options > "view" tab

Not "TheSystemWizard", but that may help.

You are welcome.

RF123