Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on multiple occasions... Error 0x0000007A and 0x000000F4

25 Feb 2012   #1

Windows 7 Home Premium 64-Bit
 
 
BSOD on multiple occasions... Error 0x0000007A and 0x000000F4

Hey everyone, i'm new to this forum so please bare with me if my posting isn't up to 'par.'

I have an HP G60-630US laptop. Its almost 4 years old i believe. This laptop serves a work computer, however, i do use it for pleasure as well. A couple of days ago, i left for lunch and closed the lid on my lappy. When i returned from lunch i opened my laptop and it started up like the laptop was turned off. Once i got back into Windows, i had a message pop up that i had got a Blue Screen and Windows had shut down. At that point, i started getting errors that some of the programs could not start properly. Also, my taskbar changed from Transparent to Grayish Blue color and my wifi showed disconnected. Then the taskbar changed back to transparent and the wifi came back. Then the did the same thing again and then wifi would not come back. Had to restart a couple times to get the wifi to stay on. The problem has gotten a lot worse since. When i try to restart my computer i get Blue Screen sometime and when i turn it on and log into windows, i also have gotten blue screen. Those are the two errors posted in the title. Also when restarting my laptop, it will take a long time to get to login screen. Once i log in the screen will stay black with just the mouse cursor for quite some time before finally going into Windows. Also, the same wifi issue and taskbar changing colors back and forth happen as well. Once in Windows i have to wait almost 10 minutes to finally be able to use my laptop (and that's if it does make it in all the way without crashing). Please help with my issue... i am sorry that my first post is me asking for help... but i am really desperate as this is my work computer and need it to be working good for work.

Here are some of my system specs:

Laptop Model: HP G60-630US
OS: OEM Preinstalled Windows 7 Home Premium 64-Bit
Processor: Pentium Dual-Core CPU T4400@2020GHz
RAM: 3.00 GB

Here are some things i tried to fix:

1. Updated my BIOS
2. Uninstalled Programs that were updated or installed the day i started having problems
3. Booted Windows into Repair mode and ran test on hardware with no reported issues
4. Tried to run CHKDSK /R and CHKDSK F/ R/ however get error that either disk is write protected or it is currently in use.
5. Updated my graphics card driver
6. Ran full system scans with Kaspersky 2012 and Norton (one at a time, i uninstalled kaspersky before installing norton and scanning) no virus found
7. Ran Malwarebytes and had not issues found
8. Tried disabling some display features
9. Disabled Windows Gadgets

The dmp files and system diagnostics report zip file is attached.

Thanks in advance!


My System SpecsSystem Spec
.

25 Feb 2012   #2

Windows 7 Ultimate x64
 
 

Hello, welcome to SevenForums!

Many different errors, nothing really as far as processes go to lead on. Two things I'd like you two do:

1. Memtest. Read the following to learn how to download and run memtest to test your memory for errors.

2. If Memtest comes back clean, it's most likely software / driver related. Hopefully we can further diagnose it if it comes to that by enabling Driver Verifier.

LOTS of drivers in need of update:

Quote:
iirsp.sys - iirsp Tue Dec 13 16:47:54 2005 (Intel Raid StorPort Driver). Update here.

nfrd960.sys - nfrd960 Tue Jun 06 17:11:48 2006 (IBM ServeRAID Controller Driver). Update here.

mdmxsdk.sys - mdmxsdk Mon Jun 19 17:27:26 2006 (Conexant Modem Diagnostic Interface x86 Driver). Update here.

adpu320.sys - adpu320 Tue Feb 27 19:04:15 2007 (Adaptec .NET Ultra320 Driver). Update here.

adpahci.sys - adpahci Tue May 01 13:30:09 2007 (Adaptec Windows SATA Storport Driver). Update here.

arc.sys - arc Thu May 24 17:27:55 2007 (Adaptec RAID Storport Driver). Update here.

SiSRaid2.sys - SiSRaid2 Wed Sep 24 14:28:20 2008 (SiS RAID Stor Miniport Driver). Update here.

sisraid4.sys - sisraid4 Wed Oct 01 17:56:04 2008 (SiS AHCI Stor-Miniport Driver). Update here.

adp94xx.sys - adp94xx Fri Dec 05 18:54:42 2008 (Adaptec HostRAID SAS Driver). Update here.

lsi_fc.sys - lsi_fc Tue Dec 09 17:46:09 2008 (LSI Logic Fusion-MPT FC Driver (StorPort). Update here.
Code:
*******************************************************************************
*                                                                             *
*                        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: fffff6fc40028f70, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000008727ebe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880051ee000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ef8b52 to fffff80002e87c40

STACK_TEXT:  
fffff880`03d1d848 fffff800`02ef8b52 : 00000000`0000007a fffff6fc`40028f70 ffffffff`c0000185 00000000`8727ebe0 : nt!KeBugCheckEx
fffff880`03d1d850 fffff800`02eaf6cf : fffffa80`05a20b40 fffff880`03d1d980 fffff800`030bd500 fffff800`02e97e96 : nt! ?? ::FNODOBFM::`string'+0x37bba
fffff880`03d1d930 fffff800`02e95f59 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`02ea74d3 : nt!MiIssueHardFault+0x28b
fffff880`03d1d9c0 fffff800`02ebc470 : 00000000`00000001 fffff880`051ee000 fffffa80`0634ba00 fffff6fc`40028f48 : nt!MmAccessFault+0x1399
fffff880`03d1db20 fffff800`02ebc660 : fffffa80`031d4b60 00000000`00000001 fffffa80`00000000 fffff800`02eb9493 : nt!MiInPageSingleKernelStack+0x134
fffff880`03d1dc30 fffff800`02ebc5ef : 00000000`00000000 00000000`00000001 fffffa80`02391b30 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`03d1dc90 fffff800`02ebc334 : 00000000`00000000 00000000`00000000 fffffa80`02391b00 fffffa80`02391b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03d1dcc0 fffff800`03122fee : ffffffff`ffffffff ffffffff`ffffffff ffffffff`ffffffff ffffffff`ffffffff : nt!KeSwapProcessOrStack+0x84
fffff880`03d1dd00 fffff800`02e795e6 : fffff800`02ffde80 fffffa80`02422600 fffff800`0300bcc0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`03d1dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+37bba
fffff800`02ef8b52 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+37bba

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+37bba

BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+37bba

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        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: fffffa80043d28e0, Terminating object
Arg3: fffffa80043d2bc0, Process image file name
Arg4: fffff800031d58b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80043d28e0

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

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.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0a7b5ac8 fffff800`0325c5e2 : 00000000`000000f4 00000000`00000003 fffffa80`043d28e0 fffffa80`043d2bc0 : nt!KeBugCheckEx
fffff880`0a7b5ad0 fffff800`0320999b : ffffffff`ffffffff fffffa80`053c9530 fffffa80`043d28e0 fffffa80`043d28e0 : nt!PspCatchCriticalBreak+0x92
fffff880`0a7b5b10 fffff800`03189448 : ffffffff`ffffffff 00000000`00000001 fffffa80`043d28e0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`0a7b5b60 fffff800`02ed0ed3 : fffffa80`043d28e0 fffff880`c0000006 fffffa80`053c9530 fffffa80`04e22060 : nt!NtTerminateProcess+0xf4
fffff880`0a7b5be0 00000000`772615da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`008ab6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772615da


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

Followup: MachineOwner


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

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40007f20, ffffffffc0000185, 6f0ab860, fffff88000fe4df0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff80003116278
Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff6fc40007f20, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000006f0ab860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88000fe4df0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b9d9a10 -- (.trap 0xfffff8800b9d9a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800b9d9bf0 rbx=0000000000000000 rcx=fffffa8002ff5ce0
rdx=fffff8800b9d9be0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000fe4df0 rsp=fffff8800b9d9ba8 rbp=fffff80003084260
 r8=0000000000000000  r9=fffffa8002ff5e00 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
partmgr!PmPowerChanged:
fffff880`00fe4df0 0000            add     byte ptr [rax],al ds:fffff880`0b9d9bf0=f0
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f54b52 to fffff80002ee3c40

STACK_TEXT:  
fffff880`0b9d96f8 fffff800`02f54b52 : 00000000`0000007a fffff6fc`40007f20 ffffffff`c0000185 00000000`6f0ab860 : nt!KeBugCheckEx
fffff880`0b9d9700 fffff800`02f0b6cf : fffffa80`05d842b0 fffff880`0b9d9870 fffff800`03119500 fffffa80`05d842b0 : nt! ?? ::FNODOBFM::`string'+0x37bba
fffff880`0b9d97e0 fffff800`02ef1f59 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`017aabcf : nt!MiIssueHardFault+0x28b
fffff880`0b9d98b0 fffff800`02ee1d6e : 00000000`00000008 fffff880`00fe4df0 00000000`00000000 fffffa80`02ff5ce0 : nt!MmAccessFault+0x1399
fffff880`0b9d9a10 fffff880`00fe4df0 : fffff880`00fd8a67 fffffa80`00000000 fffff800`00000001 fffffa80`02ff8600 : nt!KiPageFault+0x16e
fffff880`0b9d9ba8 fffff880`00fd8a67 : fffffa80`00000000 fffff800`00000001 fffffa80`02ff8600 fffffa80`02ff5c00 : partmgr!PmPowerChanged
fffff880`0b9d9bb0 fffff800`031da9e3 : fffffa80`02ff5b90 fffff800`03084260 fffffa80`0606f040 fffffa80`0606f040 : partmgr! ?? ::FNODOBFM::`string'+0x494
fffff880`0b9d9c40 fffff800`02eee001 : fffff800`03194500 fffff800`03084201 fffff800`030e5800 fffffa80`0606f040 : nt!IopProcessWorkItem+0x23
fffff880`0b9d9c70 fffff800`0317efee : fffff880`0430f5a8 fffffa80`0606f040 00000000`00000080 fffffa80`02391b30 : nt!ExpWorkerThread+0x111
fffff880`0b9d9d00 fffff800`02ed55e6 : fffff800`03059e80 fffffa80`0606f040 fffffa80`02489680 fffff880`01a69384 : nt!PspSystemThreadStartup+0x5a
fffff880`0b9d9d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !partmgr
    fffff88000fe4000-fffff88000fe400a  11 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+1e0
    [ 8a 42 01 24 1f 3c 11 0f:55 00 53 00 42 00 20 00 ]
    fffff88000fe400c-fffff88000fe401a  15 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+1ec (+0x0c)
    [ 00 8a 42 02 0f b6 72 0c:69 00 6e 00 74 00 65 00 ]
    fffff88000fe401c - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+1fc (+0x10)
    [ 00:6f ]
    fffff88000fe401e-fffff88000fe4028  11 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+1fe (+0x02)
    [ 8a 42 03 c1 e6 08 88 84:74 00 68 00 65 00 72 00 ]
    fffff88000fe402a-fffff88000fe402f  6 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+20a (+0x0c)
    [ 00 8a 42 04 45 88:46 00 43 00 2d 00 ]
    fffff88000fe4031-fffff88000fe4036  6 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+211 (+0x07)
    [ 24 88 84 24 8d 00:00 34 00 30 00 43 ]
    fffff88000fe4038-fffff88000fe4040  9 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+218 (+0x07)
    [ 00 8a 42 05 88 84 24 8c:4e 00 20 00 55 00 53 00 ]
    fffff88000fe4042-fffff88000fe404a  9 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+222 (+0x0a)
    [ 00 8a 42 06 88 84 24 8b:20 00 50 00 72 00 69 00 ]
    fffff88000fe404c-fffff88000fe4054  9 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+22c (+0x0a)
    [ 00 8a 42 07 88 84 24 8a:74 00 65 00 72 00 20 00 ]
    fffff88000fe4057-fffff88000fe4074  30 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+237 (+0x0b)
    [ 8a 42 08 88 84 24 89 00:00 01 04 15 05 dc 00 54 ]
    fffff88000fe4076-fffff88000fe4082  13 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+256 (+0x1f)
    [ 8a 42 02 41 c6 04 24 01:01 00 00 00 03 00 00 00 ]
    fffff88000fe4084-fffff88000fe408b  8 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+264 (+0x0e)
    [ 00 8a 42 03 88 84 24 8e:74 00 65 00 72 00 00 00 ]
    fffff88000fe408f-fffff88000fe4095  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+26f (+0x0b)
    [ 8a 42 04 88 84 24 8d:00 00 00 00 00 00 00 ]
    fffff88000fe4099-fffff88000fe409f  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+279 (+0x0a)
    [ 8a 42 05 88 84 24 8c:00 00 00 00 00 00 00 ]
    fffff88000fe40a3-fffff88000fe40a9  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+283 (+0x0a)
    [ 8a 42 06 88 84 24 8b:00 00 00 00 00 00 00 ]
    fffff88000fe40ad-fffff88000fe40b3  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+28d (+0x0a)
    [ 8a 42 07 88 84 24 8a:00 00 00 00 00 00 00 ]
    fffff88000fe40b7-fffff88000fe40bd  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+297 (+0x0a)
    [ 8a 42 08 88 84 24 89:00 00 00 00 00 00 00 ]
    fffff88000fe40c1-fffff88000fe40c7  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2a1 (+0x0a)
    [ 8a 42 09 88 84 24 88:00 00 00 00 00 00 00 ]
    fffff88000fe40cb-fffff88000fe40d1  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2ab (+0x0a)
    [ 8a 42 0a 88 84 24 83:00 02 00 00 00 00 00 ]
    fffff88000fe40d4-fffff88000fe40db  8 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2b4 (+0x09)
    [ 00 8a 42 0b 88 84 24 82:02 00 00 00 03 00 00 00 ]
    fffff88000fe40df-fffff88000fe40e5  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2bf (+0x0b)
    [ 8a 42 0c 88 84 24 81:00 01 00 00 00 00 00 ]
    fffff88000fe40e9-fffff88000fe40ef  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2c9 (+0x0a)
    [ 8a 42 0d 88 84 24 80:00 00 00 00 00 00 00 ]
    fffff88000fe40f3-fffff88000fe40f6  4 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2d3 (+0x0a)
    [ 8b b4 24 80:00 28 03 00 ]
    fffff88000fe40f8-fffff88000fe40fe  7 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2d8 (+0x05)
    [ 00 00 48 8b 9c 24 88:50 52 49 56 00 20 00 ]
    fffff88000fe4102-fffff88000fe4124  35 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+2e2 (+0x0a)
    [ 41 38 3c 24 74 51 49 8b:00 00 00 00 00 00 00 00 ]
    fffff88000fe4128-fffff88000fe4155  46 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+308 (+0x26)
    [ 48 8b cb e8 e0 76 ff ff:00 00 00 00 00 00 00 00 ]
    fffff88000fe4158-fffff88000fe415f  8 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+338 (+0x30)
    [ c0 8b c7 48 8b 9c 24 98:00 00 00 00 00 00 00 00 ]
    fffff88000fe4163-fffff88000fe4193  49 bytes - partmgr!PmIoctlPassThroughQuerySectorWriteScsi+343 (+0x0b)
    [ 48 83 c4 40 41 5f 41 5e:00 00 00 00 00 00 00 00 ]
    fffff88000fe4197-fffff88000fe4199  3 bytes - partmgr!PmIoctlPerformance+17 (+0x34)
    [ 83 60 08:00 00 00 ]
    fffff88000fe419b-fffff88000fe419e  4 bytes - partmgr!PmIoctlPerformance+1b (+0x04)
    [ 48 8b 82 b8:00 00 00 00 ]
    fffff88000fe41a2-fffff88000fe41b2  17 bytes - partmgr!PmIoctlPerformance+22 (+0x07)
    [ 48 8b 79 40 33 db 83 78:00 00 00 00 00 00 00 00 ]
    fffff88000fe41b5-fffff88000fe41b8  4 bytes - partmgr!PmIoctlPerformance+35 (+0x13)
    [ c0 e9 bd 00:00 01 00 01 ]
    fffff88000fe41bb-fffff88000fe41c2  8 bytes - partmgr!PmIoctlPerformance+3b (+0x06)
    [ 48 8b 6a 18 38 9f 29 01:00 00 00 00 00 00 00 00 ]
    fffff88000fe41c4-fffff88000fe41c7  4 bytes - partmgr!PmIoctlPerformance+44 (+0x09)
    [ 00 0f 85 88:01 00 00 00 ]
    fffff88000fe41cb-fffff88000fe4228  94 bytes - partmgr!PmIoctlPerformance+4b (+0x07)
    [ 33 d2 48 8d 4c 24 30 44:00 00 00 00 00 00 00 00 ]
    fffff88000fe422c-fffff88000fe4234  9 bytes - partmgr!PmIoctlPerformance+ac (+0x61)
    [ 01 75 1b 48 8d 8f 38 01:00 00 00 00 00 00 00 00 ]
    fffff88000fe4236-fffff88000fe4245  16 bytes - partmgr!PmIoctlPerformance+b6 (+0x0a)
    [ e8 15 dd ff ff 85 c0 8b:00 00 01 00 00 00 00 00 ]
    fffff88000fe4248-fffff88000fe424b  4 bytes - partmgr!PmIoctlPerformance+c8 (+0x12)
    [ eb 05 bb 10:00 00 00 00 ]
    fffff88000fe424e-fffff88000fe4256  9 bytes - partmgr!PmIoctlPerformance+ce (+0x06)
    [ c0 85 db 78 25 44 8b 8f:00 00 00 00 00 00 00 00 ]
    fffff88000fe425a-fffff88000fe425e  5 bytes - partmgr!PmIoctlPerformance+da (+0x0c)
    [ 48 8b 8f 38 01:00 00 01 00 00 ]
    fffff88000fe4261-fffff88000fe4274  20 bytes - partmgr!PmIoctlPerformance+e1 (+0x07)
    [ 4c 8d 05 18 d4 ff ff 48:00 00 00 00 00 00 00 01 ]
    fffff88000fe4278-fffff88000fe427c  5 bytes - partmgr!PmIoctlPerformance+f8 (+0x17)
    [ 4c 8d 9c 24 a0:00 00 00 00 00 ]
    fffff88000fe4280-fffff88000fe42bc  61 bytes - partmgr!PmIoctlPerformance+100 (+0x08)
    [ 8b c3 49 8b 5b 18 49 8b:00 00 00 00 00 00 00 00 ]
    fffff88000fe42c0-fffff88000fe42d0  17 bytes - partmgr!PmIoctlQueryDeviceState+20 (+0x40)
    [ 4c 8b 61 40 33 f6 83 78:41 00 72 00 69 00 61 00 ]
    fffff88000fe42d3-fffff88000fe4302  48 bytes - partmgr!PmIoctlQueryDeviceState+33 (+0x13)
    [ c0 eb 71 48 8b 7a 18 33:00 00 00 00 00 00 00 00 ]
    fffff88000fe4304-fffff88000fe430a  7 bytes - partmgr!PmIoctlQueryDeviceState+64 (+0x31)
    [ 00 00 41 8b 94 24 9c:ff ff ff 00 64 00 00 ]
    fffff88000fe430e-fffff88000fe4315  8 bytes - partmgr!PmIoctlQueryDeviceState+6e (+0x0a)
    [ 89 57 04 41 8b 94 24 d0:00 00 00 00 01 00 01 00 ]
    fffff88000fe4319-fffff88000fe4325  13 bytes - partmgr!PmIoctlQueryDeviceState+79 (+0x0b)
    [ 49 8d 4c 24 28 89 57 08:00 00 00 00 00 00 00 00 ]
    fffff88000fe4329-fffff88000fe4330  8 bytes - partmgr!PmIoctlQueryDeviceState+89 (+0x10)
    [ 89 57 0c 41 8b 94 24 d8:00 00 00 01 00 00 00 00 ]
    fffff88000fe4334-fffff88000fe4338  5 bytes - partmgr!PmIoctlQueryDeviceState+94 (+0x0b)
    [ 89 57 10 33 d2:03 00 00 00 fd ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3688 errors : !partmgr (fffff88000fe4000-fffff88000fe4fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
My System SpecsSystem Spec
25 Feb 2012   #3

Windows 7 Home Premium 64-Bit
 
 

Wow! Thanks for the rapid response! Should i try updating the drivers first? since the memory checker takes overnight to complete?
My System SpecsSystem Spec
.


25 Feb 2012   #4

Windows 7 Ultimate x64
 
 

Yes, that would be my first option as well
My System SpecsSystem Spec
25 Feb 2012   #5

Windows 7 Home Premium 64-Bit
 
 

Hey bud, I ran about 9 passes on that memtest and generated no errors... When I get home I will work on updating those drivers and after I will start using that driver verifier. At least we eliminated hardware issues! :-) thanks!
My System SpecsSystem Spec
25 Feb 2012   #6

Windows 7 Ultimate x64
 
 

Sounds great!

Good to hear for once memory was NOT the issue
My System SpecsSystem Spec
25 Feb 2012   #7

Windows 7 Home Premium 64-Bit
 
 

Hey bud... i can't seem to find this driver for Windows 7.
iirsp.sys - iirsp Tue Dec 13 16:47:54 2005 (Intel Raid StorPort Driver)

Seems they got Windows XP, Windows Vista, Windows 2000 Server, Windows Server 2003 and Windows Server 2008... any ideas on what i should do about that?
My System SpecsSystem Spec
25 Feb 2012   #8

Windows 7 Ultimate x64
 
 

I don't believe the Intel Raid StorPort Driver has a Windows 7 driver, especially if it's not listed in the Intel downloads. One thing you can try is checking your Laptop's specific page on HP's website to see if there's an update there.
My System SpecsSystem Spec
25 Feb 2012   #9

Windows 7 Home Premium 64-Bit
 
 

yea not seeing anything on HP website either... what do you think i should do about it?
My System SpecsSystem Spec
25 Feb 2012   #10

Windows 7 Ultimate x64
 
 

Don't think there's much you can do about it if there are no updates :P

I would recommend enabling Driver Verifier now
My System SpecsSystem Spec
Reply

 BSOD on multiple occasions... Error 0x0000007A and 0x000000F4




Thread Tools



Similar help and support threads for2: BSOD on multiple occasions... Error 0x0000007A and 0x000000F4
Thread Forum
Solved BSOD after every boot up, errors 0x000000f4 and 0x0000007a BSOD Help and Support
BSOD Randomly and Under Load, Errors 0x000000F4 and 0x0000007a BSOD Help and Support
Random multiple BSOD, error 0x000000f4 BSOD Help and Support
Solved BSOD playing Shank... on multiple occasions; error 0x0D1 BSOD Help and Support
BSOD multiple firefox tabs error Stop 0x0000007A BSOD Help and Support
BSOD, Kernel_Data_Inpage_Error, 0x000000F4 and 0x0000007A BSOD Help and Support
BSOD 0x0000007a Sometimes 0x000000F4 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:48 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33