Random 0x0F4 BSOD + Random hanging

[Burton2000]

Hi,

I keep getting random computer hangs could be once a month or 10 times in a day its really random when it does it. In between these I have been getting equally random BSOD, I could be playing a game or surfing the web or nothing at all and it will just BSOD, with code 0x0F4 every time.

I am presuming the two problems are related so hopefully solving the BSOD can sort out the random hanging.

I know this code is a hardware/driver issue so I have ran memtest for 8+ hours on several occasions with no errors detected at all so I don't think its a RAM issue. I have also ran Prime 95 for several hours with no issue. I also believe I have all latest drivers and bios installed.

Any help would really be appreciated to finally solve this issue, thanks!

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008364910, fffffa8008364bf0, fffff800035d9270}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------

0xF's can often be symptomatic of HDD errors. Run the DOS version of SeaTools - run both SHORT and LONG tests, and report back.

http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[Burton2000]

Hi,

Thanks for the reply. I have now done the DOS version of SeaTools test, both long and short, and all my hard drives passed so that doesn't seem to be the problem.

Is it possible that the problem is caused by the motherboard? This whole build is less than a year old and I have tried new installation of windows but didnt help.

 

[Golden]

Please do the following:

1. Delete all .dmp files in C:\Windows\Minidump (you will require Administrator privileges to do that)
2. Now run Driver Verifier, noting the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

3. Once you receive a BSOD, re-run DM Log Collector to generate a fresh ZIP file, and upload it here in your next reply.

 

[Burton2000]

Thanks for your reply, done everything as you said and got a blue screen this morning but it was a different error code than I have got before.

 

[Burton2000]

I got another 0x0f4 BSOD today. It happened when I changed my audio cable at the back of my computer from my headset to speakers. I have attached the new log.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40006008, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 0000000047e42860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88000c01000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

BUGCHECK_STR:  0x7a_c00000c0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

Check that all motherboard controller/drivers are updated from the manufacturer site.

On the SANDISK SSD, do this:

1. Check for and install the latest firmware if required,
2. Check the alignment:
http://www.sevenforums.com/tutorials/113967-ssd-alignment.html

Now do this:
1. Click Start

2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type chkdsk /R and hit enter.

You will be prompted whether you wish to schedule a chkdsk scan at next startup, type 'Y' and hit enter. Now restart your computer and chkdsk will automatically run.

Check memory:
Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Reference this tutorial to help you use MemTest86+:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[Burton2000]

Hi,

I know its been a while since I replied, I thought the problem had stopped but just recently I have been getting them and a lot more frequently.

I checked my SSD and the firmware is up to date and the alignment is okay as well. chkdks return no errors.

I also ran Memtest for 12 passes and not a single error. However the first time I tried to run it Memtest did freeze after like 3 minutes of testing, does this indicate anything?

Any help in solving my issue would be much appreciated

I have attatched the latest logs from all the recent BSOD as well if you need them.

 

[Golden]

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public

Uninstall the above software - its a common cause of BSOD's.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800866ab30, fffffa800866ae10, fffff80003586130}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------

Since the hard disks pass the tests, that leaves the motherboard. Can you connect the drives to a different SATA porrt on the motherboard, and run Driver Verifier again please.