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 Different Times and Different Errors

25 Feb 2012   #1

Windows 7 Ultimate x64
 
 
BSOD on Different Times and Different Errors

I bought a new laptop.

There are times I got BSOD and have different errors. I can't determine if the problem is in the software or in the hardware.

Sometimes, I get BSOD when I'm in the middle of transferring of files.
Sometimes, just after turning the laptop on from Hibernate.
Sometimes, after the windows load and before the desktop shows.
Sometimes, when I'm just installing a driver.

Please help me solve this.

My specs:



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.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800dbe5a68
Arg3: fffff8800dbe52d0
Arg4: fffff80002e5d725

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


EXCEPTION_RECORD:  fffff8800dbe5a68 -- (.exr 0xfffff8800dbe5a68)
ExceptionAddress: fffff80002e5d725 (nt!MmFlushSection+0x0000000000000105)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800dbe52d0 -- (.cxr 0xfffff8800dbe52d0)
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800779a4df
rdx=0000000000000000 rsi=ff6efa8007545320 rdi=fffff88002f64180
rip=fffff80002e5d725 rsp=fffff8800dbe5ca0 rbp=0000000000000000
 r8=0000000000000000  r9=fffff8800dbe5a88 r10=fffffa80090e6400
r11=fffff8800dbe5c70 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
nt!MmFlushSection+0x105:
fffff800`02e5d725 f00fba6e481f    lock bts dword ptr [rsi+48h],1Fh ds:002b:ff6efa80`07545368=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  2

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030a90e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsFlushUserStream+92
fffff880`014df642 389c24a0000000  cmp     byte ptr [rsp+0A0h],bl

FAULTING_IP: 
nt!MmFlushSection+105
fffff800`02e5d725 f00fba6e481f    lock bts dword ptr [rsi+48h],1Fh

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff80002e5d119 to fffff80002e5d725

STACK_TEXT:  
fffff880`0dbe5ca0 fffff800`02e5d119 : fffffa80`06d87e18 fffff880`0dbe5e00 00000000`00100000 fffffa80`00000000 : nt!MmFlushSection+0x105
fffff880`0dbe5d60 fffff880`014df642 : fffffa80`06d87e18 fffff880`00000000 fffffa80`00000000 00000000`00100000 : nt!CcFlushCache+0x5e9
fffff880`0dbe5e60 fffff880`014e06ba : fffff8a0`0a873c70 fffff8a0`0a873c70 fffff8a0`0a873c70 fffffa80`095c1370 : Ntfs!NtfsFlushUserStream+0x92
fffff880`0dbe5ee0 fffff880`014df88e : fffffa80`095c1370 fffff8a0`0a873c70 00000000`00000000 fffffa80`0a303060 : Ntfs!NtfsPerformOptimisticFlush+0x7a
fffff880`0dbe5f40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x12a


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  Ntfs!NtfsFlushUserStream+92

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff8800dbe52d0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFlushUserStream+92

BUCKET_ID:  X64_0x24_Ntfs!NtfsFlushUserStream+92

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000022, 
Arg2: 0091000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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

GetUlongFromAddress: unable to read from fffff8000302e1b0

BUGCHECK_STR:  0x19_22

POOL_ADDRESS:  0091000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002eddbb0 to fffff80002e885c0

STACK_TEXT:  
fffff880`0adbdfd8 fffff800`02eddbb0 : 00000000`00000019 00000000`00000022 00910000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0adbdfe0 fffff800`02fbd518 : 00000000`00000000 fffff880`0adbe130 fffff880`0adbe0a0 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x7288
fffff880`0adbe070 fffff800`02e74fb0 : 00000000`00000000 00000000`000000d0 fffffa80`093310d0 00000000`00000000 : nt!ExFreePoolWithTag+0x468
fffff880`0adbe120 fffff800`02e9db1e : 00000000`ffffffff fffff880`0adbe2a8 00000000`00000001 fffff8a0`0b1ca001 : nt!ExDeleteResourceLite+0x190
fffff880`0adbe180 fffff800`02e77f87 : fffffa80`074451a0 fffff880`0adbe2a8 00000000`00000000 fffffa80`074451a0 : nt!CcUnpinFileDataEx+0x3fe
fffff880`0adbe200 fffff800`02e7417b : fffffa80`074452d8 fffff880`0adbe3a0 00000000`00009000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0xa7
fffff880`0adbe250 fffff880`012ec665 : fffffa80`074452d8 00000000`00000000 fffffa80`00000000 fffffa80`00009000 : nt!CcFlushCache+0x64b
fffff880`0adbe350 fffff880`012b0b3e : fffffa80`075fe010 00000000`00000000 fffff880`ffffdf01 00000000`00000000 : Ntfs!NtfsFlushLsnStreams+0x295
fffff880`0adbe3f0 fffff880`01395038 : fffffa80`075fe010 fffffa80`074fc180 fffff880`0adbe900 00000000`00000001 : Ntfs!NtfsCheckpointVolume+0xe8e
fffff880`0adbe7f0 fffff880`012d438e : fffffa80`075fe010 00000000`00000000 fffff880`c0000188 00000000`00000001 : Ntfs!NtfsCheckpointForLogFileFull+0x48
fffff880`0adbe840 fffff880`011b223f : fffff880`0adbe990 fffffa80`09474010 fffff880`0adbe901 fffffa80`075fe010 : Ntfs!NtfsFsdFileSystemControl+0x1de
fffff880`0adbe8e0 fffff880`011d191e : fffffa80`09331990 fffffa80`06fcda30 fffffa80`09331900 fffffa80`09474010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0adbe970 fffff800`031a0597 : fffffa80`06fcda30 fffff880`0adbec60 fffffa80`094743b0 fffffa80`09474010 : fltmgr!FltpFsControl+0xee
fffff880`0adbe9d0 fffff800`031697da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0adbeb00 fffff800`02e87813 : ffffffff`ffffffff 00000000`0054d748 00000000`0054d760 00000000`00000004 : nt!NtFsControlFile+0x56
fffff880`0adbeb70 00000000`77b1fa4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0054d9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b1fa4a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+7288
fffff800`02eddbb0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+7288

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+7288

BUCKET_ID:  X64_0x19_22_nt!_??_::FNODOBFM::_string_+7288

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        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: fffff960001a55ed, Address of the instruction which caused the bugcheck
Arg3: fffff88006392180, 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: 
win32k!UserSurfaceAccessCheck+1d
fffff960`001a55ed 488b8078010000  mov     rax,qword ptr [rax+178h]

CONTEXT:  fffff88006392180 -- (.cxr 0xfffff88006392180)
rax=ff4ef900c1fab250 rbx=0000000000000000 rcx=0a3f1f2000000004
rdx=0000077ffdb0c9a0 rsi=0000000000000000 rdi=0a3f1f2000000004
rip=fffff960001a55ed rsp=fffff88006392b50 rbp=fffff88006392c60
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=ff4ef900c1fab250 r12=00000000002782d0 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!UserSurfaceAccessCheck+0x1d:
fffff960`001a55ed 488b8078010000  mov     rax,qword ptr [rax+178h] ds:002b:ff4ef900`c1fab3c8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff9600023bab3 to fffff960001a55ed

STACK_TEXT:  
fffff880`06392b50 fffff960`0023bab3 : 00000000`00000000 0000007f`00000060 00000000`00000000 0000007f`fffffff8 : win32k!UserSurfaceAccessCheck+0x1d
fffff880`06392b80 fffff800`02e85813 : fffffa80`0aca5980 00000001`ffffffff 00000000`03e9c601 00000000`00000001 : win32k!NtGdiDdDDIGetDeviceState+0x57
fffff880`06392be0 000007fe`ff3c131a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03e9f518 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff3c131a


FOLLOWUP_IP: 
win32k!UserSurfaceAccessCheck+1d
fffff960`001a55ed 488b8078010000  mov     rax,qword ptr [rax+178h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!UserSurfaceAccessCheck+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

STACK_COMMAND:  .cxr 0xfffff88006392180 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!UserSurfaceAccessCheck+1d

BUCKET_ID:  X64_0x3B_win32k!UserSurfaceAccessCheck+1d

Followup: MachineOwner

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ef5cd5, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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!MiResolveDemandZeroFault+135
fffff800`02ef5cd5 66833c0200      cmp     word ptr [rdx+rax],0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031100e0
 ffffffffffffffff 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88003b74758 -- (.exr 0xfffff88003b74758)
ExceptionAddress: fffff80002ef5cd5 (nt!MiResolveDemandZeroFault+0x0000000000000135)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88003b74800 -- (.trap 0xfffff88003b74800)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ff7ffa80068fb400 rbx=0000000000000000 rcx=000000000000003f
rdx=0000000000000060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ef5cd5 rsp=fffff88003b74990 rbp=fffff88003b74a00
 r8=0000000000000006  r9=fffff6800001ea90 r10=0000000000000000
r11=fffff88003b74be0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiResolveDemandZeroFault+0x135:
fffff800`02ef5cd5 66833c0200      cmp     word ptr [rdx+rax],0 ds:2000:ff7ffa80`068fb460=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f12919 to fffff80002ed85c0

STACK_TEXT:  
fffff880`03b73f88 fffff800`02f12919 : 00000000`0000001e ffffffff`c0000005 fffff800`02ef5cd5 00000000`00000000 : nt!KeBugCheckEx
fffff880`03b73f90 fffff800`02ed7c02 : fffff880`03b74758 00000000`00000002 fffff880`03b74800 fffffa80`0ac2aec8 : nt!KiDispatchException+0x1b9
fffff880`03b74620 fffff800`02ed650a : 00000000`00000000 000007fe`fa40a042 ffffffff`ffffffff fffffa80`06257010 : nt!KiExceptionDispatch+0xc2
fffff880`03b74800 fffff800`02ef5cd5 : fffffa80`0adea890 00000000`00000000 00000000`00001000 fffff880`03b74c60 : nt!KiGeneralProtectionFault+0x10a
fffff880`03b74990 fffff800`02ef2816 : 00000000`00000001 00000000`03d52ff8 fffff880`03b74be0 fffff680`0001ea90 : nt!MiResolveDemandZeroFault+0x135
fffff880`03b74a80 fffff800`02ed66ae : 00000000`00000001 00000000`000e0000 000007fe`00000001 fffffa80`0ade11e0 : nt!MmAccessFault+0x5c6
fffff880`03b74be0 00000000`76dc7958 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0226ea10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dc7958


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiResolveDemandZeroFault+135
fffff800`02ef5cd5 66833c0200      cmp     word ptr [rdx+rax],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiResolveDemandZeroFault+135

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiResolveDemandZeroFault+135

BUCKET_ID:  X64_0x1E_c0000005_nt!MiResolveDemandZeroFault+135

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

*******************************************************************************
*                                                                             *
*                        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: fffff9600079c1d0, Address of the instruction which caused the bugcheck
Arg3: fffff8800709d7f0, 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: 
cdd!CStagingPool::GetGdiSurface+100
fffff960`0079c1d0 48894808        mov     qword ptr [rax+8],rcx

CONTEXT:  fffff8800709d7f0 -- (.cxr 0xfffff8800709d7f0)
rax=ff7ff900c00c1250 rbx=fffffa800a4ef8d0 rcx=fffff900c00c12a0
rdx=fffff900c00c1278 rsi=0000000000000000 rdi=fffff900c00c0fa0
rip=fffff9600079c1d0 rsp=fffff8800709e1c0 rbp=fffff8800709e3a0
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff80003038e80 r12=0000000000000040 r13=fffff8800709e780
r14=0000000000000100 r15=0000000076edf70a
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
cdd!CStagingPool::GetGdiSurface+0x100:
fffff960`0079c1d0 48894808        mov     qword ptr [rax+8],rcx ds:002b:ff7ff900`c00c1258=????????????????
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 fffff9600079c1d0

STACK_TEXT:  
fffff880`0709e1c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!CStagingPool::GetGdiSurface+0x100


FOLLOWUP_IP: 
cdd!CStagingPool::GetGdiSurface+100
fffff960`0079c1d0 48894808        mov     qword ptr [rax+8],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cdd!CStagingPool::GetGdiSurface+100

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94

STACK_COMMAND:  .cxr 0xfffff8800709d7f0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_cdd!CStagingPool::GetGdiSurface+100

BUCKET_ID:  X64_0x3B_cdd!CStagingPool::GetGdiSurface+100

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        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: fffff80002c6bc3d, Address of the instruction which caused the bugcheck
Arg3: fffff8800a714e70, 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!AlpcpQueueIoCompletionPort+1ad
fffff800`02c6bc3d 48894108        mov     qword ptr [rcx+8],rax

CONTEXT:  fffff8800a714e70 -- (.cxr 0xfffff8800a714e70)
rax=fffffa8006a91168 rbx=fffffa800aaeac20 rcx=fffdfa800aaeac28
rdx=fffffa800a2a5168 rsi=fffff88002f64180 rdi=fffffa800ab12d30
rip=fffff80002c6bc3d rsp=fffff8800a715850 rbp=0000000000000000
 r8=fffffa8006a91168  r9=0000000000000000 r10=0000000000020000
r11=0000000000000000 r12=fffffa800aaeac28 r13=fffffa8009346060
r14=fffff8a001b9b400 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!AlpcpQueueIoCompletionPort+0x1ad:
fffff800`02c6bc3d 48894108        mov     qword ptr [rcx+8],rax ds:002b:fffdfa80`0aaeac30=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  lsm.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c6bc3d

STACK_TEXT:  
fffff880`0a715850 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!AlpcpQueueIoCompletionPort+0x1ad


FOLLOWUP_IP: 
nt!AlpcpQueueIoCompletionPort+1ad
fffff800`02c6bc3d 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!AlpcpQueueIoCompletionPort+1ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff8800a714e70 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpQueueIoCompletionPort+1ad

BUCKET_ID:  X64_0x3B_nt!AlpcpQueueIoCompletionPort+1ad

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

Windows 7 Ultimate x64
 
 

I already got errors without even completing a pass. Does this mean that the problem is in the laptop and not in the software?

So, do I need to open the laptop? I can't do that because if I did, the replacement/warranty period will be void. The only thing I can do if the problem is in the hardware is to turn the laptop over to the seller/manufacturer, right?
My System SpecsSystem Spec
.


25 Feb 2012   #4

Windows 7 Ultimate x64
 
 

That is correct
My System SpecsSystem Spec
25 Feb 2012   #5

Windows 7 Ultimate x64
 
 

Ok. Thanks!

Here's the result of memtest.



An error occurred during the test #4 of pass 0. I rerun the memtest and an error occurred again but it happened on the test 3 and it has the same failing address.
My System SpecsSystem Spec
25 Feb 2012   #6

Windows 7 Ultimate x64
 
 

Yep, any errors are a sign of failing memory. Now you'll want to contact the manufacturer directly and get an RMA sorted
My System SpecsSystem Spec
25 Feb 2012   #7

Windows 7 Ultimate x64
 
 

Thank you very much.
My System SpecsSystem Spec
25 Feb 2012   #8

Windows 7 Ultimate x64
 
 

My pleasure, let us know how things are working when the replacement sticks arrive
My System SpecsSystem Spec
23 Mar 2012   #9

Windows 7 Ultimate x64
 
 

Sorry, late reply. I run a memtest last night, the time I got the laptop with new RAM sticks, and I didn't got any errors but still, there's a blue screen. With the Driver Verifier, after logging on to windows but before the desktop appears, a BSOD will appear. It has an 0x0000000a error.

Here are the new reports.
My System SpecsSystem Spec
23 Mar 2012   #10

Windows 7 Ultimate x64
 
 

Verifier dumps showed the culprit as MBfilt64.sys, which is the Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver).

I'd recommend fully uninstalling your Realtek drivers via programs & features in the Control Pnael, and then update your Realtek drivers here.
My System SpecsSystem Spec
Reply

 BSOD on Different Times and Different Errors





Thread Tools




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 07:13 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