BSOD within five minutes of starting windows

Hello and congratulations on gaining the 2nd million post achievement!

BSOD Analyse

BCCode

Code:

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800961eb30, Terminating object
Arg3: fffffa800961ee10, Process image file name
Arg4: fffff80002fd8510, Explanatory message (ascii)

Try to do this.

* Press Start
* Search 'msconfig'
* Select Startup
* Deselect all of them

This will prevent 3rd party consoles from starting up.

This is a decent place to start when we have this kind of bugcheck I believe.

Best Regards,
Frederik.

Thanks for the fast response!

And I'm very happy to be the 2nd millionth post!

Trying your suggestion right now.

It's not within five minutes of windows starting, I thought so at first, but it appears to be random. I got it just after running 3Dmark 11, but not during. I ran Windows memory test and it found nothing. I ran Intel Tool Box for my SSD, and it didn't show any problems. There could be the SandForce bug but that should be sorted with the latest firmware...

Tried disabling all the startup programs, still BSOD.

Interesting.

I see you're having this, powerbiosserver.exe. It should be possible to uninstall this through the Control Panel as usual, but I cannot identify what this type of process indicates.

Code:

powerbiosserver.exe	c:\program files (x86)\hotkey\powerbiosserver.exe	2108	8	200	1380	2012-08-15 21:04	1.0.0.0	34,50 KB (35*328 bytes)	2011-02-18 14:57

Code:

hotkey.exe	c:\program files (x86)\hotkey\hotkey.exe	3756	8	200	1380	2012-08-15 21:05	1.0.0.0	4,51 MB (4*727*296 bytes)	2012-04-11 12:12

Best Regards,
Frederik.

In that case you can leave it.

I believe this is process/driver related. Therefore, let's run driver verifier in order to do some stress testing on your drivers.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

No problem, and good luck mate.

Scandinavian Power. :)

Best Regards,
Frederik.