View Single Post
Unread 10 Jul 2007, 15:25   #7
djbass
mmm.. pills
 
djbass's Avatar
 
Join Date: Apr 2000
Location: Australia
Posts: 2,152
djbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond reputedjbass has a reputation beyond repute
Re: [BSOD] STOP: 0x000000f4

I only had a brief look into the error during lunch earlier but I've since had time to look a little deeper into this issue.

Starting with the root cause:

Quote:
0x000000F4: CRITICAL_OBJECT_TERMINATION
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function.
Noted common causes:
  • A piece of software or driver is conflicting in such a way that it freezes or terminates a system process.
  • The pagefile is damaged.
  • The IO controller is faulty (which these days is located on the mainboard).

Some possible fixes for the above:

Software/Driver conflict
Try uninstalling/rollback any recently installed drivers and software.
If system restore is enabled you might try reverting to a date before this started happening.

You could attempt the following to pinpoint the faulty driver:
1) Goto Start->Run...
2) Type in 'verifier' and hit enter
3) Select 'Create Standard Setting' and hit next
4) Select 'Automatically select all drivers installed on this computer' and hit Finish
5) Reboot


This will attempt to verify the drivers as they are running and will slow windows down a bit. If for some reason it fails to boot at all after doing this, start the computer in safe mode (F8) and repeat the above but choose 'Select driver names from a list' at step 4, check the box next to any
driver where the provider is not Microsoft, hit Finish and reboot.

When the BSOD next occurs it should have "DRIVER_VERIFIER_DETECTED_VIOLATION" instead with details of the faulting driver.


Pagefile is damaged
Recreate the pagefile using the following steps.

Right click my computer, select properties, then the advanced tab.

Under performance, click settings. Click on the advanced tab and then on the change button.

Click on the custom size button and click in the initial size box, make the size of the page file 0. Click in the maximum size box, make the size of the page file 0.

Click set.

Now reboot your machine. After your system has restarted, run a defrag.

Once the defrag has finished, go back to the pagefile settings above and click on the change button. For the initial and maximum pagefile size make it 1.5 times the ammount of ram you have. I.E if you have 512mb of ram set the page file to 768mb.

Click on the set button again and reboot your system. You now have a brand new page file.


For an alternative method refer to the following article


Faulty IO controller
Get a new motherboard.. sorry no easy fix for this one
__________________
CSS : the result of letting artists design something only an engineer should touch.
djbass is offline   Reply With Quote