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: Recent BSODs, dumps attached

27 Jun 2010   #1

Windows 7 x64 Professional
 
 
Recent BSODs, dumps attached

Hello-

Been having BSOD problems on Friday and again today, however I was away this weekend, so its every few minutes I use my computer now.

On Friday with the first one I received I only briefly saw the screen before it restarted and was under the impression that something was wrong with my hard drive. So I focused on rebacking my laptop stuff up before I went away for the weekend.

Today I am getting more errors that don't seem to be the same every time so I need some help. I dont really think I have changed any hardware settings recently either, so I don't know whats going on. The minidump.zip is attached. Thanks in advance for any help you can give me.

-Russell

My System SpecsSystem Spec
.

27 Jun 2010   #2

Windows 7 Ultimate 32 bit
 
 

Hi Russell, I looked at the last five dmps since the first two were older. These dmps point to hardware issues. Three of them showing a stop error code of 3B.

Quote:
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory
BSOD Index

STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory
BSOD Index


STOP 0x00000116: VIDEO_TDR_ERROR (go to top of page)

Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Minidump.zip\062510-24913-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Fri Jun 25 13:36:20.660 2010 (GMT-4)
System Uptime: 0 days 0:29:07.595
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002caa187, fffff8800dc92a00, 0}

Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+227 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002caa187, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800dc92a00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!MmCopyToCachedPage+227
fffff800`02caa187 8b7838          mov     edi,dword ptr [rax+38h]

CONTEXT:  fffff8800dc92a00 -- (.cxr 0xfffff8800dc92a00)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff80002c0b000 rsi=ffffffffffffffff rdi=fffffa800844d330
rip=fffff80002caa187 rsp=fffff8800dc933d0 rbp=fffff8800dc93440
 r8=0000098000000000  r9=00000000070e3040 r10=0000058000000000
r11=0000000000000002 r12=fffff6fcc00fa518 r13=0000000000000000
r14=0000000000001000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MmCopyToCachedPage+0x227:
fffff800`02caa187 8b7838          mov     edi,dword ptr [rax+38h] ds:002b:00000000`00000038=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002caa187

STACK_TEXT:  
fffff880`0dc933d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmCopyToCachedPage+0x227


FOLLOWUP_IP: 
nt!MmCopyToCachedPage+227
fffff800`02caa187 8b7838          mov     edi,dword ptr [rax+38h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MmCopyToCachedPage+227

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

STACK_COMMAND:  .cxr 0xfffff8800dc92a00 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MmCopyToCachedPage+227

BUCKET_ID:  X64_0x3B_nt!MmCopyToCachedPage+227

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Minidump.zip\062710-19390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50
Debug session time: Sun Jun 27 19:14:08.121 2010 (GMT-4)
System Uptime: 0 days 0:15:48.768
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 2250a, 0, 2224a}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000002250a, page frame number
Arg3: 0000000000000000, current page state
Arg4: 000000000002224a, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d4e2bc to fffff80002cbe600

STACK_TEXT:  
fffff880`06e47d88 fffff800`02d4e2bc : 00000000`0000004e 00000000`00000099 00000000`0002250a 00000000`00000000 : nt!KeBugCheckEx
fffff880`06e47d90 fffff800`02c5734c : 81200000`2250a863 fffffa80`0066f1e0 00000000`00000000 00000dd0`00000000 : nt!MiBadShareCount+0x4c
fffff880`06e47dd0 fffff800`02cb3c55 : 00000000`00000000 00000000`00000366 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x47897
fffff880`06e47f30 fffff800`02def34f : 00000000`00000001 fffff800`02cca202 00000000`00000000 fffff880`0b161000 : nt!MiFreePagedPoolPages+0x129
fffff880`06e48080 fffff800`02df387c : 00000000`00000000 fffff880`06e48250 fffff880`06e481c0 00000000`00000001 : nt!MiFreePoolPages+0x343
fffff880`06e48190 fffff960`00104c18 : fffff900`c3200228 fffff880`06e48290 00000000`35316847 00000000`00000001 : nt!ExFreePoolWithTag+0x7cc
fffff880`06e48240 fffff960`001053ea : fffff900`c00bf010 fffff900`c3200000 00000000`00000000 fffff900`c3200228 : win32k!FreeObject+0x58
fffff880`06e48270 fffff960`00105584 : ffffffff`00000000 fffff880`00000000 fffff900`c3200000 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x58a
fffff880`06e483c0 fffff960`000c65a5 : ffffffff`a3050ed7 fffff900`c3200000 00000000`00000ed7 00000000`7efdb000 : win32k!bDeleteSurface+0x34
fffff880`06e483f0 fffff800`02cbd853 : fffffa80`0856bb60 fffff880`06e484a0 00000000`06e80820 00000000`00000001 : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`06e48420 00000000`73a32dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ad188 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73a32dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d4e2bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Minidump.zip\062710-20919-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Sun Jun 27 20:02:50.578 2010 (GMT-4)
System Uptime: 0 days 0:08:33.529
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800111fc8d, fffff880061a1eb0, 0}

Probably caused by : iaStor.sys ( iaStor+56c8d )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800111fc8d, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880061a1eb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
iaStor+56c8d
fffff880`0111fc8d 488941e0        mov     qword ptr [rcx-20h],rax

CONTEXT:  fffff880061a1eb0 -- (.cxr 0xfffff880061a1eb0)
rax=0000000100000034 rbx=fffffa800526d900 rcx=0000000000000020
rdx=fffffa800526d900 rsi=fffffa8007c90610 rdi=0000000000000000
rip=fffff8800111fc8d rsp=fffff880061a2888 rbp=0000000000000104
 r8=0000000000000038  r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=fffffa8004ec91a0 r13=0000000000000001
r14=0000000000000000 r15=fffffa8004ec91a0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
iaStor+0x56c8d:
fffff880`0111fc8d 488941e0        mov     qword ptr [rcx-20h],rax ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  IAANTmon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800111fc8d

STACK_TEXT:  
fffff880`061a2888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : iaStor+0x56c8d


FOLLOWUP_IP: 
iaStor+56c8d
fffff880`0111fc8d 488941e0        mov     qword ptr [rcx-20h],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  iaStor+56c8d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a287aa4

STACK_COMMAND:  .cxr 0xfffff880061a1eb0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_iaStor+56c8d

BUCKET_ID:  X64_0x3B_VRF_iaStor+56c8d

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Minidump.zip\062710-21153-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02e9ee50
Debug session time: Sun Jun 27 20:14:15.090 2010 (GMT-4)
System Uptime: 0 days 0:08:16.041
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffff9800f6264e0, fffff8801059c150, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+71c150 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffff9800f6264e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801059c150, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+71c150
fffff880`1059c150 803d19e4550000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`10afa570)],0

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`07959b48 fffff880`03e5fef8 : 00000000`00000116 fffff980`0f6264e0 fffff880`1059c150 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`07959b50 fffff880`03e33867 : fffff880`1059c150 fffffa80`07b84000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07959b90 fffff880`03e5fd07 : fffff980`ffffd87b ffffffff`fffe7960 fffff980`0f6264e0 00000000`00000010 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`07959c40 fffff880`03f2eec1 : fffff980`14044d50 00000000`00000080 00000000`00000000 fffff980`13578410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`07959cc0 fffff800`02f76a86 : 00000000`032a769d fffffa80`07b8bb60 fffffa80`03c905f0 fffffa80`07b8bb60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`07959d00 fffff800`02cafb06 : fffff800`02e4be80 fffffa80`07b8bb60 fffff800`02e59c40 fffff880`0125f534 : nt!PspSystemThreadStartup+0x5a
fffff880`07959d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+71c150
fffff880`1059c150 803d19e4550000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`10afa570)],0

SYMBOL_NAME:  nvlddmkm+71c150

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b07613e

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_nvlddmkm.sys

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp3_Minidump.zip\062710-21216-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Sun Jun 27 20:26:05.675 2010 (GMT-4)
System Uptime: 0 days 0:08:19.626
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880010aac8d, fffff880092b5eb0, 0}

Probably caused by : iaStor.sys ( iaStor+56c8d )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880010aac8d, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880092b5eb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
iaStor+56c8d
fffff880`010aac8d 488941e0        mov     qword ptr [rcx-20h],rax

CONTEXT:  fffff880092b5eb0 -- (.cxr 0xfffff880092b5eb0)
rax=0000000300000034 rbx=fffffa8004e1a300 rcx=0000000000000020
rdx=fffffa8004e1a300 rsi=fffffa8006927340 rdi=0000000000000000
rip=fffff880010aac8d rsp=fffff880092b6888 rbp=0000000000000120
 r8=0000000000000038  r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=fffffa80047ec1a0 r13=0000000000000001
r14=0000000000000000 r15=fffffa80047ec1a0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
iaStor+0x56c8d:
fffff880`010aac8d 488941e0        mov     qword ptr [rcx-20h],rax ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  IAANTmon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880010aac8d

STACK_TEXT:  
fffff880`092b6888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : iaStor+0x56c8d


FOLLOWUP_IP: 
iaStor+56c8d
fffff880`010aac8d 488941e0        mov     qword ptr [rcx-20h],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  iaStor+56c8d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a287aa4

STACK_COMMAND:  .cxr 0xfffff880092b5eb0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_iaStor+56c8d

BUCKET_ID:  X64_0x3B_VRF_iaStor+56c8d

Followup: MachineOwner
---------
All of the above point to hardware errors/conflicts. One dmp, stop error 116 point to your video card.

You have some older drivers that need to be updated:
Quote:
000.fcl Fri Sep 26 09:11:22 2008 (48DCDF7A)
agrsm64.sys Mon Nov 10 10:01:35 2008 (49184CCF)
amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
enecir.sys Mon Apr 28 13:55:30 2008 (48160F92)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
iaStor.sys Thu Jun 04 21:53:40 2009 (4A287AA4)
iPodDrv.sys Fri Apr 10 00:07:40 2009 (49DEC60C)
jmcr.sys Mon Mar 31 04:49:10 2008 (47F0A586)
netw5v64.sys Thu Mar 26 12:21:24 2009 (49CBAB84)
SynTP.sys Fri Jun 20 19:06:00 2008 (485C37D8)
VClone.sys Fri May 22 19:08:37 2009 (4A173075)
I know you are having trouble booting. See if you can boot in the safe mode w/internet support. If so, update the drivers above. Old drivers can definitely cause conflicts with /windows 7.

How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Let me when you accomplish this and we will start testing your hardware.

Also, when you can boot, p
lease fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading
Speccy
.
My System SpecsSystem Spec
27 Jun 2010   #3

Windows 7 x64 Professional
 
 

Ok thanks for the help. I tried to look into on my own, but it BSODs quickly now, before I can really do anything. Having to post from my phone at the moment, so I really appreciate it.
My System SpecsSystem Spec
.


27 Jun 2010   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by DoubleW720 View Post
Ok thanks for the help. I tried to look into on my own, but it BSODs quickly now, before I can really do anything. Having to post from my phone at the moment, so I really appreciate it.

Try booting into safe mode (F8) and see if it still does it.


Ken
My System SpecsSystem Spec
27 Jun 2010   #5

Windows 7 x64 Professional
 
 

Ken-

That was the first thing I did, yet it did not help. Still BSODs even in safemode. The time it takes doesn't seem to be consistent however. On Friday I had enough time to do a full backup of my system, yet today I didn't have enough time to logon here and make my first post. Thanks though.
My System SpecsSystem Spec
27 Jun 2010   #6

Windows 7 Ultimate 32 bit
 
 

Do you have a Windows CD to boot from? Do you have access to another computer?
My System SpecsSystem Spec
27 Jun 2010   #7

Windows 7 x64 Professional
 
 

Yes, I have the CD I installed windows with in the fall.
My System SpecsSystem Spec
27 Jun 2010   #8

Windows 7 x64 Professional
 
 

I also now have another laptop for the moment that I can use. What do you have in mind?
My System SpecsSystem Spec
27 Jun 2010   #9

Windows 7 Ultimate 32 bit
 
 

First thing is to see if you can boot from the CD. That will indicate whether you have a bad hardware problem or not. Ken may come back and add to this.

Go into the sevenforums from your laptop and fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you. You can make this easier by downloading Speccy.

If you can burn a CD from your laptop,
Download a copy of Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7. Boot from the CD, and leave it running for at least 5 passes.




My System SpecsSystem Spec
27 Jun 2010   #10

Windows 7 x64 Professional
 
 

Updated Info.

Don't know if this is relevant or not, but I have my computer booted up, and the resolution will not change to higher than 1024x768 when I normally have it at 1680x1050. This is not in safemode either, which seems odd to me. Going to burn the iso and run memtest. Thanks again.
My System SpecsSystem Spec
Reply

 Recent BSODs, dumps attached





Thread Tools



Similar help and support threads for2: Recent BSODs, dumps attached
Thread Forum
Multiple different BSOD - crash dumps attached BSOD Help and Support
Can't tell what's causing BSODs (dumps attached) BSOD Help and Support
BSOD (dumps attached) BSOD Help and Support
Solved BSOD - Crashes Constantly / Dumps attached BSOD Help and Support
need bsod help (dumps attached) BSOD Help and Support
Strange crashes no blue screen - dumps attached BSOD Help and Support
Bsod 3 dumps and info attached 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 10:46 AM.
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