|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 06 Jan 2012 | #11 |
|
|
WOAH just had two BSODs within about 3 minutes of each other. One was the code 0x000000f4 and one was 0x0000007A.
Dump files attached. I'm thinking its my D: drive. I've left my system to idle all day and used it for general use for about 4 hours when I got home without the D: drive connected and no BSODs to report. Connected the D: drive and I get two after just a couple of hours. EDIT: I'm gonna go to all lengths to get this fixed. I'm formatting my D: drive. I'm re-installing Windows on my C: drive. BIOs v1.00 is on the motherboard. CMOS is cleared. Hopefully all this should rule out software error. |
My System Specs |
| . |
|
|
| 06 Jan 2012 | #12 |
|
|
Another BSOD for someone to take a look at. Sorry for the bombardment.
This happened during the formatting of my D: drive. |
| My System Specs |
| 06 Jan 2012 | #13 |
|
|
Your DMP analysis was inconclusive.
If you are overclocking anything reset to default before running this test. In other words STOP!!! As a driver appears to be the culprit please run .... > Driver verifier Quote:
I'd suggest that you first backup your data 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).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . Then, here's the procedure: - 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 "Low Resource Simulation" and click "Next" - 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). 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. Further Reading Using Driver Verifier to identify issues with Windows drivers for advanced users |
| My System Specs |
| . |
|
|
|
Random BSOD: STOP 0x000000f4
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
| Similar help and support threads | ||||
| Thread | Forum | |||
|
BSOD - random. STOP error 0x000000f4 Hello, I recently bought a new laptop. After a few weeks I started getting random BSODs. At the time I though this is related to VMWARE and other stupid things I have done. I did re-install Win7 after that and BSODs disappeared for about 2 weeks. Now they're back again. My laptop has a 22Gb... |
BSOD Help and Support | |||
|
Random BSOD. Tried re-installing. STOP 0x000000F4 Crashes started a while back after downloading an update for my windows phone. They got bad enough that I did a clean re-install and everything worked fine for a while. Now the crashes are back with a vengeance. They seem to be pretty random. I get error: *** STOP: 0x000000F4... |
BSOD Help and Support | |||
|
Random BSOD - Stop 0x000000F4 ntoskrnl.exe Hello, I found some good tipps here on the forum, but I couldn't find a solution. I have random BSOD since 2 Month. Sometimes with minidumps, sometimes without. I run a dualboot system with Win7 64bit and XP 32bit. The crashes appear most of the time on Win7 and really rarley in XP,altough... |
BSOD Help and Support | |||
|
BSOD random intervals Windows 7 sony VAio Stop: 0x000000F4 x86 (32-bit) or x64 ? 64 - the original installed OS on the system? yes - an OEM or full retail version? OEM - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? Purchased december 2009 - What is the age of OS... |
BSOD Help and Support | |||
|
Random BSOD occurances, STOP: 0x000000F4 I've been having random BSOD crashes for the past week. Also, multiple attempts to fix the BSOD problem by using System Restore has resulted in a BSOD crash. Every BSOD has displayed "STOP: 0x000000F4" To my knowledge, no new hardware has been installed on my computer in several months. ... |
BSOD Help and Support | |||
|
Stop 0x000000F4 Error (seemingly random?) It seems I've been having random BSOD Stop errors ever since I put my new PC together about a month ago. I'm not sure what's causing it, and it's happened when I've been doing different things, but it almost seems to happen more frequently when I'm listening to Pandora Radio on my web browser... |
BSOD Help and Support | |||
| Our Sites |
Site Links |
About Us |
Find Us |
|
Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd All times are GMT -5. The time now is 16:38. |
|
