Intermittent BSOD

[JaseJ]

Hi,

I previously made a thread about this but didnt upload the correct files so I have created a new thread.

windows 7 x64
Is the original Os on the system
oem
Roughly 3/4 months i brought the system
I havent reinstalled the Os

Thanks

 

[yowanvista]

Remove PC Tools and Avast, running two antivirus programs can cause BSODs
Use MSE instead

PCTCore64.sys        fffff880`014b3000    fffff880`014f6000    0x00043000    0x4cec9fad    24/11/2010 09:16:29

aswFsBlk.SYS        fffff880`05fd0000    fffff880`05fd9000    0x00009000    0x4dac711c    18/04/2011 21:13:00                
aswMonFlt.sys        fffff880`05f96000    fffff880`05fd0000    0x0003a000    0x4dac7127    18/04/2011 21:13:11                
aswRdr.SYS        fffff880`02f34000    fffff880`02f3e000    0x0000a000    0x4dac7133    18/04/2011 21:13:23                
aswSnx.SYS        fffff880`042d7000    fffff880`0436f000    0x00098000    0x4dac7246    18/04/2011 21:17:58                
aswSP.SYS        fffff880`04461000    fffff880`044ae000    0x0004d000    0x4dac7244    18/04/2011 21:17:56                
aswTdi.SYS        fffff880`0402b000    fffff880`0403b000    0x00010000    0x4dac71e5    18/04/2011 21:16:21                
peauth.sys        fffff880`05b4d000    fffff880`05bf3000    0x000a6000    0x4a5bd8df    14/07/2009 05:01:19

Your Hard Disk is the direct cause, run http://www.sevenforums.com/tutorials/433-disk-check.html

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80078bd6a0, fffffa80078bd980, fffff800031d22d0}

Probably caused by : hardware_disk


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: fffffa80078bd6a0, Terminating object
Arg3: fffffa80078bd980, Process image file name
Arg4: fffff800031d22d0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80078bd6a0

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_RECORD:  fffff880073f9b78 -- (.exr 0xfffff880073f9b78)
ExceptionAddress: 00000000774958d5
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000773d0c34
   Parameter[2]: 00000000c000009d
Inpage operation failed at 00000000773d0c34, due to I/O error 00000000c000009d

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000773d0c34

EXCEPTION_PARAMETER3:  00000000c000009d

IO_ERROR: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

EXCEPTION_STR:  0xc0000006_c000009d

FAULTING_IP: 
+23a
00000000`774958d5 ??              ???

BUGCHECK_STR:  0xF4_IOERR_C000009D

FOLLOWUP_IP: 
+23a
00000000`773d0c34 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000009D_IMAGE_hardware_disk

BUCKET_ID:  X64_0xF4_IOERR_C000009D_IMAGE_hardware_disk

 

[JaseJ]

Apologies for the late reply I have done as you suggested and removed pc tools and avast, also I have ran both chkdsk and sfc /scannow and neither returned any errors but the blue screen has happend again since. Any other ideas??
Oh another piece of info that might be helpful I dont know if this would make any difference but the blue screen normally happens when I start my pc for the day, meaning its had a good 8 ish hours of not being on. I dont seem to get it as much once the pc has been on for a while.

 

[yowanvista]

Apologies for the late reply I have done as you suggested and removed pc tools and avast, also I have ran both chkdsk and sfc /scannow and neither returned any errors but the blue screen has happend again since. Any other ideas??
Oh another piece of info that might be helpful I dont know if this would make any difference but the blue screen normally happens when I start my pc for the day, meaning its had a good 8 ish hours of not being on. I dont seem to get it as much once the pc has been on for a while.

Please upload latest .zip

 

[JaseJ]

Ok i presume you mean these Many thanks

 

[cluberti]

This one isn't too difficult to figure out, but root cause may be:

2: kd> .bugcheck
Bugcheck code 0000007A
Arguments 00000000`00000020 ffffffff`c000009d fffffa80`0]72097c8 00000000`00000000
 
2: kd> !error ffffffffc000009d
Error code: (NTSTATUS) 0xc000009d (3221225629) - STATUS_DEVICE_NOT_CONNECTED

That second argument, ffffffffc000009d means that the disk subsystem reported an error, and Windows bugchecked to prevent further data loss. As to why it's reporting a failure, we don't necessarily know. However, it's not a *filesystem* issue, this error was reported by the disk controller itself (the motherboard I/O controller, a vritual drive driver, or the hard disk that was being written to or read from itself). What it ultimately means is that your system was reading from or writing to hardware (real or virtual), and that device went offline during an inpage operation from disk to memory, and anytime that happens Windows bugchecks. This doesn't always signify a hardware problem, though - I noticed you have a virtual disk driver loaded, as well as AVG. I'd start by updating your Intel chipset drivers (iastor.sys) to the latest version, and remove the software that provides this virtual drive:

// Remove this:
2: kd> lmivm ISODrv64
start             end                 module name
fffff880`02fd0000 fffff880`02fee000   ISODrv64   (deferred)             
    Symbol file: ISODrv64.sys
    Image path: ISODrv64.sys
    Image name: ISODrv64.sys
    Timestamp:        Tue Feb 10 04:22:18 2009 (4991474A)
    CheckSum:         0001C6DB
    ImageSize:        0001E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e
 
// Update this:
2: kd> lmivm iaStor
start             end                 module name
fffff880`01273000 fffff880`0147b000   iaStor     (deferred)             
    Symbol file: iaStor.sys
    Image path: iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Fri Oct 02 15:58:50 2009 (4AC65B7A)
    CheckSum:         00089194
    ImageSize:        00208000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'd also suggest removing AVG for the time being (not disable, remove) as it also adds filter drivers that affect *all* data I/O on the system (as would any antivirus package - we need to test now, so please don't install one until this is finished for these reasons). If doing the above does not resolve the issue, I'd suggest it's time to back up anything precious to you to someplace safe, and start testing your disk hardware for errors, starting with the hard disk(s).

 

[JaseJ]

Ok thanks for responding to this thread, I dont really know much about computers and such so dont really know what this means. A Friend of mine normally sorts my problems out and refered me to your site. I will have to speak to him to explain in lay-mans terms to me.

 

[cluberti]

Print out my post, and bring it to him - that should be sufficient.

 

[JaseJ]

Will do. Many thanks again for your help