Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

The machine in question is a Dell PP22L laptop. After logging on, the system will act normally, but slowly, for about 5 minutes before going to a BSOD with the following details: (shown by using BlueScreenView)

BSOD 0x7F

share|improve this question
add comment

3 Answers

up vote 1 down vote accepted

The only way to know for sure is to get a kernel dump and use WinDbg.exe to get the stack trace and find out what kernel mode code was involved in the crash. Most likely it is a driver.

To properly diagnose this error you need to configure your machine to create a proper Kernel Memory Dump (not a mini dump) and make sure your page file is large enough to hold it (physical ram + 1mb).

Once you have a proper dump, you can use the downloadable Debugging Tools for Windows to install WinDbg (pronounced wind-bag by the cool people). Debugging kernel dumps is not for the faint hearted. Here is a guide to get you started.

share|improve this answer
add comment

I have had 2 pc's go through my shop in the last 2 weeks with the same bsod. One had a faulty hp printer driver causing the issue, a quick removal and re-installation of the software and driver resolved it. The other had some minor partition problems that were resolved by running a 5 stage check disk, the guide is for vista but the steps are the same in xp anyway.

Past that some further internet research had another 2 computers, one fixed his issue by replacing the bios battery (unfortunately not easy on a laptop). The other resolved the problem by running memtest86+ and discovering a faulty memory module.

Please run some tests and tell us if you find anything.

Good Luck!

share|improve this answer
add comment

From TROUBLESHOOTING WINDOWS STOP MESSAGES:

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. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive; compare KB 330100.

If this doesn't help, please supply additional information:

  • Are there any error messages in the Error Log?
  • Have you added/replaced any hardware just before this started?
  • Have you installed any software or drivers just before this started?
  • You might run Memtest86+ to check the computer memory
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.