Random BSOD 0xF4

[koen3950]

Hi all,

I recently reinstalled windows 7 (after a full format) on my laptop (which was working fine but getting a bit bloated). Ever since I keep getting random freezes/BSODs. I have no clue what is causing it since sometimes it BSODs immediately after system startup, sometimes when installing windows updates, sometimes after being idle for an hour, ...

What did I do already:
- opened it up, checked all cables and removed dust
- ran memtest (ok)
- ran disk check (ok)
- reinstalled windows AGAIN
- updated all drivers from asus site, installed all windows updates
- ran verifier (it always causes a bsod immediately after system startup, no matter what drivers I select) but to be honest, I have no idea how to use it
- ran sfc /scannow succesfully (no problems found)

Maybe most difficult thing is I almost NEVER get a (mini-)dump file after such a BSOD. Up untill now (after like 100 bsods) I only have 2 minidumps, which I attached. I looked into them but understanding is beyond my capabilities ...

Does anyone have any idea?
much appreciated!

Kind regards,

Koen

 

[Shintaro]

Mate,

That's a pretty good start. You have covered a lot of things!

Could you do the following please:

1. Click the Start Button.
2. Type in cmd
3. You should see cmd.exe in the list.
4. Right click on cmd.exe and select "Run as Administrator"
5. In the command prompt window type in:

wmic recoveros set DebugInfoType = 2
​

It should say that the command was successful.

• Download hwInfo and run it.
  • Click on "Save Report"
  • Make sure the Export Format is HTML
  • Click "Browse" and select your "Desktop"
  • Give the file a name like MyComputer or your Forum username.
  • Click on Save
  • Click on "Next".
  • Click on "Finish"
  • Put the newly created MyComputer.html (Or what ever you decided to call it) in to a zip file and upload it to the forum.

Once that you have done that then please enable Driver Verifier.


Driver verifier

The Driver Verifier tool that is included in every version of Windows since Windows 2000 it is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior.

***FIRST: Please 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 Windows 7 Startup Repair feature.)

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select:
   ---- Special Pool
   ---- Pool Tracking
   ---- Force IRQL Checking
   ----Deadlock Detection
   ---- Security Checks (Windows 7 & 8)
   ---- Miscellaneous Checks
5. Click "Next"
6. Select "Select driver names from a list" and click "Next"
7. Then select all drivers NOT provided by Microsoft and click "Next"
8. 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.

Will I see anything when I enable Driver Verifier?

No, Driver Verifier configures Windows so that people looking at the crash dump files get (in most cases) more detailed information about what actually crashed the computer.
​

How Long should I wait for a crash?

- If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
​

How do I turn Driver Verifier off?!

- Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page.

- Or press the Windows Key + R, and type in "verifier /reset" (Without the quotes)

- Then locate and zip up the memory dump file and upload it with your next post. then locate and zip up the memory dump file and upload it with your next post.
​

I can't get in to Windows, what do I do?

- If Windows will not start and get to a login screen or desktop, 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.
​

How do I put the crash dump files in a Zip file?

Instructions on putting files in a Zip file and extracting (Taking them out) again are explained HERE.
​

 

[koen3950]

Hello,

thanks for your reply! I ran the hwinfo report as requested. It bluescreened a few times but sadly these bsods didnt generate a minidump ...

Ok, i'm running verifier now and am unable to enter Windows. It hangs on a grey screen after the welcome message. Should i keep it sitting there or should i reset the system until it bluescreens?

kind regards,

Koen

 

[Shintaro]

Mate,

Disable Driver Verifier.

Could you please get a screen capture of the following registry location and post it to the forum.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl]


Once you have done that please do the following:

1. Click on the Start button and type in cmd.
2. In the list you will see cmd.exe.
3. Right click on Cmd.exe and select "Run as Administrator"
4. At the command prompt type in the following:

verifier /volatile /flags 0xdd9

Close the command prompt.
You won't need to reboot.

Hopefully it will provide more information about who is crashing the computer.

 

[Shintaro]

Just so that you know, and you might already know this. Crash dumps can be in any of the following directories:
c:\Windows
c:\Windows\Minidump
c:\Windows\Live KernelReports\WATCHDOG

 

[koen3950]

Hello,

I attached the screenshot you asked for. The directories you mentioned are all empty...
I have noticed something, don't know if it is of any use: often (but not always) after a bsod, my wireless network adapter is disabled ... But when i look in the device manager, it says its drivers are up to date ...

I will now run verifier with the settings you mentioned.

Thanks for the help!

 

[Shintaro]

Ok, well the registry looks correct.

Can you make sure that the pagefile is managed by Windows.

 

[koen3950]

Yes pagefile is managed by windows.
When verifier is running my system hangs after a few minutes but no bsod and no dmp's :-(
Or should i keep it hanging for a while (i long-pressed the powerbutton after 5 minutes)?
Edit: it's running again after a reboot and nothing happens now...

Thanks

 

[Shintaro]

Hmmm this is a tricky one.

Do you run CCleaner? Because, by default I think it removes crash dump files.

Sorry what do you mean "Nothing is happening now"?

 

[Shintaro]

Also make sure that the ONLY things plugged in to the USB ports are a standard USB Microsoft mouse and if you need it, a keyboard.

 

[koen3950]

No I don't run CCcleaner or something similar. Only security essentials ...

By "nothing happens" I mean that it doesn't hang or bsod ... But I only kept it running for an hour because I had to leave ... Will retry tonight.

The only USB device plugged in is a simple mouse. I can try to unplug it and use the touchpad instead?

 

[koen3950]

I'm running out of ideas here ...
I ran memtest for 21 hours now, no problems found ... I havent had a bluescreen for days (when running verifier as you suggested) but it just freezes instead ...
Sadly, no logs/dumps/... found

 

[koen3950]

Ok just did another test:
ran chkdisk again, no problems found

installed seatools and ran a test, bluescreen after 2 minutes!
I uploaded the full kernell dump here:
http://www.filedropper.com/m51va

Thanks!

 

[koen3950]

Because I got a bit out of hope, I reinstalled Windows with an iso with SP1 etc baked in.
Installed drivers 1 by 1, found 1 that caused bsods (a ricoh sd cardreader driver). Restored system and installed an older (Vista) version of the driver and all was fine.
I ran verifier together with a system stresser (aida64) to make sure it was stable and it was.

Then I wanted to start installing windows updates, but after the first(!) recommended update (an ati graphics card update) it bsods again when running verifier :-(

Can someone please look at the dump to see whats wrong with my system? :-(

Thanks!