BSOD - random occurance - 0x000000F4, atapi.sys, ntfs.sys

[dbx10]

Hello, i've got random BSOD occuring ever since i changed my video card from an ASUS EN9600GT to a GTX550Ti

Intel Core i5 760 @ 2.81ghz
ASUS P7H55M/CSM
4(2x2)GB Kingston DDR3-1333
Seagate Barracuda SATAII 160GB 7200RPM
Thermaltake Toughpower 750W
ASUS GTX550Ti 1GB
LG 16x supermulti DVD Writer
ASUS WL-138G v2 wireless network card
Zowie Hammer USB Soundcard

Windows 7 Home Premium x64 retail has ran on this machine since october 2010

The first occasions, the BSODs displayed ntfs.sys once, and atapi.sys twice. Other occurances displayed a panoply of STOP: 0x000000F4 codes, all with different arguments. I noted two of them.

"0x000000F4 (0x0000000000000003, 0xFFFFFA8005741B30, 0xFFFFFA8005741E10, 0xFFFFF800037DB5F0)"

"0x000000F4 (0x0000000000000003, 0xFFFFFA80053BD060, 0xFFFFFA80053BD340, 0xFFFFF800037935F0)"

my minidump is empty, Windows doesn't write before pooping itself. It's quite frustrating.

I know atapi is the IDE controller, so i took the liberty of testing out if the dvd burner would work, and it doesn't. It crashes midway through burning.

I ran Windows_NT6_BSOD_v3.03_jcgriff2_.exe and i attached the .rar with everything in it.

I also attached a .txt with an atapi.sys error report i found.

Halp?

View attachment 205324
View attachment 205325

EDIT: important to mention, i also ran SFC /scannow and chkdsk /f, and ran the HDD diagnostic on UBCD.

 

[zigzag3143]

Sorry No DMP files included in upload, try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[dbx10]

It is already set that way, ill have to wait until it crashes in safe mode to see if it will dump. I'll update when it does.

 

[zigzag3143]

It is already set that way, ill have to wait until it crashes in safe mode to see if it will dump. I'll update when it does.

Sounds good.

 

[dbx10]

I let it bsod 3 times in safe mode, and it still did not dump.

EDIT: attached is a list of my drivers running in safe mode using driverview.exe

View attachment 205399

 

[zigzag3143]

I let it bsod 3 times in safe mode, and it still did not dump.

EDIT: attached is a list of my drivers running in safe mode using driverview.exe

View attachment 205399

I appreciate the effort but we need the DMPS when you crash as it is not a static file but rather something we can sort to data mine.

 

[dbx10]

After 3 more BSOD's it still does not dump.

EDIT: when i tried verifying if it was set to dump the way you ask me to, it said the page file was less than 1MB when i clicked okay. It said it could not write dump files because of that.

I checked if it indeed was and it was set to my C:/ drive and system managed. It had approx. 3600mb.

 

[zigzag3143]

After 3 more BSOD's it still does not dump.

EDIT: when i tried verifying if it was set to dump the way you ask me to, it said the page file was less than 1MB when i clicked okay. It said it could not write dump files because of that.

I checked if it indeed was and it was set to my C:/ drive and system managed. It had approx. 3600mb.

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.

 

[dbx10]

UAC was turned on, i had it set to small dump, and the page file is on the same hard drive.

I just set it to memory dump to see if it will dump something at all next crash.

EDIT: no memory.dmp anywhere, and nothing in the minidump folder no matter what settings i try.

 

[zigzag3143]

UAC was turned on, i had it set to small dump, and the page file is on the same hard drive.

I just set it to memory dump to see if it will dump something at all next crash.

EDIT: no memory.dmp anywhere, and nothing in the minidump folder no matter what settings i try.

Have you had another BSOD? We need at least one to see if it can/will create one.

 

[dbx10]

yes, many. and it still doesn't dump anything.

 

[zigzag3143]

yes, many. and it still doesn't dump anything.

Hum, that will make it difficult. Lets try looking through Event viewer logs

Please provide us with your Event Viewer administrative logs by following these steps:


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

 

[dbx10]

View attachment 205529

there

 

[zigzag3143]

View attachment 205529

there

The event log runs from jun 2010 to the present and seems not to be in English. Unsure of the proper translation

The Explorateur d’ordinateurs service depends on the Station de travail

 

[dbx10]

Yea sorry, this is in french. If theres anything you need to translate, you can ask me.

In any case if this is too much trouble i can always format and reinstall. Im just intrigued by this particular problem.

 

[zigzag3143]

Yea sorry, this is in french. If theres anything you need to translate, you can ask me.

In any case if this is too much trouble i can always format and reinstall. Im just intrigued by this particular problem.

I would be happy to keep doing this till solved but truth be told you will get working faster and more efficiently if you do format and re-install. Your call

 

[dbx10]

I will most likely be formatting, a fresh install would help anyway. Thanks for your help.

 

[zigzag3143]

I will most likely be formatting, a fresh install would help anyway. Thanks for your help.

Smart idea and let us know if you need help

 

[dbx10]

Well, something new came up. I got rid of the BSOD problem after formatting, and i'm running on a brand new hard drive. I currently am on a fresh format, but after i'm done with all the windows updates it doesn't boot anymore. It started by posting NTLDR missing, BOOTMGR missing, then stopped posting altogether. White line flashing, top left corner. The BIOS detects the hard drive, posts, but it doesn't show windows boot options no matter what the boot order is. It installs W7 just fine, but it doesn't detect my Windows partition after only a few reboots. I also can't burn DVDs. It gives me an "unexpected error".
What could this possibly be? My DVD drive reads discs just fine but i can't burn anything on it, ever. I had the same issue when i had the BSOD problem. I tried using my W7 DVD to repair my MBR, but it can't see my Windows partition either.

EDITED

 

[writhziden]

See post #13 by gregrocker who is probably our best analyst with solving these problems involving MBR.

I am concerned with the problems with hard disks you have had. I wonder if your motherboard/connection for the hard disk is faulty. It could be a bad cable, bad connectors, or a bad board...