BSOD when computer is idle, happens after about 1-2 hours of up time.

[cphillips71395]

Hi, i am getting a BSOD. I have done a little research thinking that it might be a bad video card (I own an NVIDIA GeForce 9400GT on v340) or some bad memory(running 4 x 1GB). I am not exceptional at reading dump codes or anything like that so I went and found that I could upload my files and receive some help. If you guys need any information more than this please let me know.

 

[koolkat77]

Hello.

This bugcode is usually Hard driver (Storage) related.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\New folder\122814-28314-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c54890
Debug session time: Mon Dec 29 05:39:34.646 2014 (UTC + 6:00)
System Uptime: 0 days 0:34:39.285
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005c96b30, fffffa8005c96e10, fffff80002d8c270}

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

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

0: 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: fffffa8005c96b30, Terminating object
Arg3: fffffa8005c96e10, Process image file name
Arg4: fffff80002d8c270, Explanatory message (ascii)

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

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

PROCESS_OBJECT: fffffa8005c96b30

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`02b520a8 fffff800`02e14ab2 : 00000000`000000f4 00000000`00000003 fffffa80`05c96b30 fffffa80`05c96e10 : nt!KeBugCheckEx
fffff880`02b520b0 fffff800`02dbfabb : ffffffff`ffffffff fffffa80`05f12060 fffffa80`05c96b30 fffffa80`05c96b30 : nt!PspCatchCriticalBreak+0x92
fffff880`02b520f0 fffff800`02d3ef04 : ffffffff`ffffffff 00000000`00000001 fffffa80`05c96b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`02b52140 fffff800`02a85e53 : fffffa80`05c96b30 fffff800`c0000005 fffffa80`05f12060 00000000`009f06e0 : nt!NtTerminateProcess+0xf4
fffff880`02b521c0 fffff800`02a82410 : fffff800`02ad182f fffff880`02b52b38 fffff880`02b52890 fffff880`02b52be0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02b52358 fffff800`02ad182f : fffff880`02b52b38 fffff880`02b52890 fffff880`02b52be0 00000000`009f1f20 : nt!KiServiceLinkage
fffff880`02b52360 fffff800`02a86242 : fffff880`02b52b38 00000000`0000aab7 fffff880`02b52be0 00000000`009f19f8 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`02b52a00 fffff800`02a84dba : 00000000`00000001 00000000`009f0c98 00000000`00000001 00000000`0000aab7 : nt!KiExceptionDispatch+0xc2
fffff880`02b52be0 00000000`770e8e5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`009f0ca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770e8e5d


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
---------

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.