Windows 7: BSOD recurring on custom build; 0x07A 0x0f4

Freiberg · 30 May 2013

My custom rig is having issues with a recurring BSOD, particularly when playing Guild Wars 2. I have researched and researched, but have yet to come up with a definitive solution to my problem. I am grasping at straws at this point and am hoping for some additional help with this issue. I have attached the info obtained from the SF Tool as well as the BSOD itself. This is my second attempt at finding help in this forum, as I believe my first attempt was too vague, because nobody was offering any info. Any insight is greatly appreciated, and I thank you in advance!

Arc · 30 May 2013

Hi nickfreiberg.

Scan the system for possible virus infection with the following programs.

Do some Disc checks.

Re-seat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Post a screenshot of your HDD using CrystalDiskInfo - Software - Crystal Dew World

Uninstall Marvell SCSI controllers (Marvell 91xx) in Control panel > Programs and Features. Then follow Drivers - Clean Left over Files after Uninstalling to clean up the leftovers. Visually it is very old.

Code:

fffff880`0113e000 fffff880`011cb000   mv91xx     (deferred)             
    Image path: mv91xx.sys
    Image name: mv91xx.sys
    Timestamp:        Mon Nov 22 12:30:45 2010 (4CEA151D)
    CheckSum:         0004B35E
    ImageSize:        0008D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

And, marvell is poorly coded.

Disable RAID in BIOS. Set the storage controller to AHCI mode.

Let us know the results.
______________________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80096b8b30, fffffa80096b8e10, fffff800033cb350}

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

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffffa80096b8b30, Terminating object
Arg3: fffffa80096b8e10, Process image file name
Arg4: fffff800033cb350, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

KERNEL_LOG_FAILING_PROCESS:  è

PROCESS_OBJECT: fffffa80096b8b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0953be38 fffff800`03452d22 : 00000000`000000f4 00000000`00000003 fffffa80`096b8b30 fffffa80`096b8e10 : nt!KeBugCheckEx
fffff880`0953be40 fffff800`033ff08b : ffffffff`ffffffff fffffa80`0c846b50 fffffa80`096b8b30 fffffa80`096b8b30 : nt!PspCatchCriticalBreak+0x92
fffff880`0953be80 fffff800`0337f144 : ffffffff`ffffffff 00000000`00000001 fffffa80`096b8b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0953bed0 fffff800`030c3e93 : fffffa80`096b8b30 fffff800`c0000005 fffffa80`0c846b50 00000000`020a03c0 : nt!NtTerminateProcess+0xf4
fffff880`0953bf50 fffff800`030c0450 : fffff800`0310f81f fffff880`0953ca38 fffff880`0953c790 fffff880`0953cae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0953c0e8 fffff800`0310f81f : fffff880`0953ca38 fffff880`0953c790 fffff880`0953cae0 00000000`020a1ed0 : nt!KiServiceLinkage
fffff880`0953c0f0 fffff800`030c4282 : fffff880`0953ca38 00000000`0000aab7 fffff880`0953cae0 00000000`020a19a8 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`0953c900 fffff800`030c2dfa : 00000000`00000001 00000000`020a0ad8 00000000`773f8d01 00000000`0000aab7 : nt!KiExceptionDispatch+0xc2
fffff880`0953cae0 00000000`772e8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`020a0ae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e8e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

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

Freiberg · 30 May 2013

Thanks so much Arc, glad to see a reply! I know you BSOD guys probably stay busy so I greatly appreciate the help...i'll update as soon as I do those things!

Arc · 30 May 2013

No hurry. Take your time. :)

Forgot to mention one thing. You have Magic Disc installed? If so, uninstall it, too.

Freiberg · 30 May 2013

Sure thing! I am at work presently, so it'll be a few hours :)

Arc · 30 May 2013

BTW, who built the system? If it is built by yourself, IMHO you should take care of a couple of things. First, RAID setup is never needed for a single HDD setup, and RAID is always troublesome. Second,using more than one SCSI drivers may cause problems and conflicts, which may result in storage access failure, BSOD 0xF4 and 0X7A. You had both Marvell and JMicron SCSI drivers installed.

Freiberg · 30 May 2013

Well, I built this system myself in February 2012, it is my first ever and currently only build. I'm very pleased with the outcome sans a few issues I have had including this one. I am sure my inexperience and lack of advanced technical knowledge is contributing to the blue screens. I try to keep only the required and important drivers and software installed. I uninstalled MSI Live Update because of this exact reason. It kept prompting me to download a whole mess of things I considered to be unnecessary. I definitely know that a RAID is not necessary with a single HDD, idk why I have that installed :/ I thought I saw something in the DMP file that may have pertained to the keyboard I use, which is a Logitech G19, thoughts?

Arc · 30 May 2013

I have not noticed anything about the keyboard. But if you want, I will check it :)

But the prima facie issues are to get the first attention

Freiberg · 30 May 2013

Would you advise against ASC 6? Quite a few of the other threads I was reading on had a lot of members suggest running MSE and MWB in tandem and nothing else. I have CCleaner, Advanced Systemcare, and MSE...might not be the best idea...

Arc · 31 May 2013

Quote: Originally Posted by nickfreiberg

Would you advise against ASC 6?

Yes, as it does not care, but damages the installation beyond repair in normal course.