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 1e Win 7 x64

22 Jul 2011   #1
ari277

WINDOWS 7 HOME PREMIUM X64
 
 
BSOD 1e Win 7 x64

Hi evreyone! I bought a new laptop! But today he give me this BSOD:


Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7601.2.1.0.768.3
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8000339CF80
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\072211-19500-01.dmp
C:\Users\user\AppData\Local\Temp\WER-39951-0.sysdata.xml
My laptop is TOSHIBA Satellite L755
System Specs:
OS - windows 7 home premium 64bit
all hardware is OEM
the laptop is about 1 week old

This BSOD appear when i play game how CRYSIS 2 or TEST DRIVE UNLIMITED 2. BUT NOT EVREY TIME
THANKS FOR HELP!
Attachment 166277


My System SpecsSystem Spec
.
22 Jul 2011   #2
yowanvista

Windows 10 Pro x64, Arch Linux
 
 

Remove any UASSOFT.com HID (mouse) Driver used by a Kensington Mouse, this device is old and the driver it uses is obsolete

Download the latest Toshiba Generic IO & Memory Access and Toshiba Bluetooth drivers
Toshiba Support - Homepage

Run a RAM test RAM - Test with Memtest86+
Remove IObit smart defrag, it has known issues with Windows 7
Code:
SmartDefragDriver.sys        fffff880`01afa000    fffff880`01b01000    0x00007000    0x4d64c764    23/02/2011 12:37:56
Code:
*******************************************************************************
*                                                                             *
*                        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: fffff8000339cf80, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, 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!PspWow64GetContextThreadOnAmd64+10
fffff800`0339cf80 0300            add     eax,dword ptr [rax]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330d100
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x1E

PROCESS_NAME:  TestDrive2.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a3ae660 -- (.trap 0xfffff8800a3ae660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80058dcb60
rdx=0000000008a8dd30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000339cf80 rsp=fffff8800a3ae7f0 rbp=fffff8800a3aeb60
 r8=fffffa80057d4f01  r9=0000000000000201 r10=fffff800033caba0
r11=fffff800030dcf78 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!PspWow64GetContextThreadOnAmd64+0x10:
fffff800`0339cf80 0300            add     eax,dword ptr [rax] ds:e701:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800031295d8 to fffff800030ddd00

STACK_TEXT:  
fffff880`0a3addd8 fffff800`031295d8 : 00000000`0000001e ffffffff`c0000005 fffff800`0339cf80 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a3adde0 fffff800`030dd382 : fffff880`0a3ae5b8 00000000`000002cc fffff880`0a3ae660 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0a3ae480 fffff800`030dbefa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000002cc : nt!KiExceptionDispatch+0xc2
fffff880`0a3ae660 fffff800`0339cf80 : fffff880`0a3ae120 00000000`08f7fa70 00000000`08f7fa50 00000000`08f7f580 : nt!KiPageFault+0x23a
fffff880`0a3ae7f0 fffffa80`0821c010 : fffffa80`0858dbb0 fffffa80`085ed070 00000000`00000000 fffffa80`0a308878 : nt!PspWow64GetContextThreadOnAmd64+0x10
fffff880`0a3ae830 fffffa80`0858dbb0 : fffffa80`085ed070 00000000`00000000 fffffa80`0a308878 fffff680`00045468 : 0xfffffa80`0821c010
fffff880`0a3ae838 fffffa80`085ed070 : 00000000`00000000 fffffa80`0a308878 fffff680`00045468 00000000`08a8ee01 : 0xfffffa80`0858dbb0
fffff880`0a3ae840 00000000`00000000 : fffffa80`0a308878 fffff680`00045468 00000000`08a8ee01 00000000`08a8ee01 : 0xfffffa80`085ed070


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
5 errors : !nt (fffff8000339cf45-fffff8000339cf7d)
fffff8000339cf40  8d  10  03  00  00 *08  33  cd  e8  03  82  d3  ff *08  8b  9d ......3.........
...
fffff8000339cf60  5d  41  5c  5f  5e *5f  c3  90  90  90  90  90  90 *92  90  90 ]A\_^_..........
fffff8000339cf70  ff  f5  56  57  41  54  41  55  41  56  41  57  48 *83  ec  70 ..VWATAUAVAWH..p

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8000339cf80, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, 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!PspWow64GetContextThreadOnAmd64+10
fffff800`0339cf80 0300            add     eax,dword ptr [rax]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS:  0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x1E

PROCESS_NAME:  TestDrive2.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a3ae660 -- (.trap 0xfffff8800a3ae660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80058dcb60
rdx=0000000008a8dd30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000339cf80 rsp=fffff8800a3ae7f0 rbp=fffff8800a3aeb60
 r8=fffffa80057d4f01  r9=0000000000000201 r10=fffff800033caba0
r11=fffff800030dcf78 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!PspWow64GetContextThreadOnAmd64+0x10:
fffff800`0339cf80 0300            add     eax,dword ptr [rax] ds:e701:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800031295d8 to fffff800030ddd00

STACK_TEXT:  
fffff880`0a3addd8 fffff800`031295d8 : 00000000`0000001e ffffffff`c0000005 fffff800`0339cf80 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a3adde0 fffff800`030dd382 : fffff880`0a3ae5b8 00000000`000002cc fffff880`0a3ae660 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0a3ae480 fffff800`030dbefa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000002cc : nt!KiExceptionDispatch+0xc2
fffff880`0a3ae660 fffff800`0339cf80 : fffff880`0a3ae120 00000000`08f7fa70 00000000`08f7fa50 00000000`08f7f580 : nt!KiPageFault+0x23a
fffff880`0a3ae7f0 fffffa80`0821c010 : fffffa80`0858dbb0 fffffa80`085ed070 00000000`00000000 fffffa80`0a308878 : nt!PspWow64GetContextThreadOnAmd64+0x10
fffff880`0a3ae830 fffffa80`0858dbb0 : fffffa80`085ed070 00000000`00000000 fffffa80`0a308878 fffff680`00045468 : 0xfffffa80`0821c010
fffff880`0a3ae838 fffffa80`085ed070 : 00000000`00000000 fffffa80`0a308878 fffff680`00045468 00000000`08a8ee01 : 0xfffffa80`0858dbb0
fffff880`0a3ae840 00000000`00000000 : fffffa80`0a308878 fffff680`00045468 00000000`08a8ee01 00000000`08a8ee01 : 0xfffffa80`085ed070


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
5 errors : !nt (fffff8000339cf45-fffff8000339cf7d)
fffff8000339cf40  8d  10  03  00  00 *08  33  cd  e8  03  82  d3  ff *08  8b  9d ......3.........
...
fffff8000339cf60  5d  41  5c  5f  5e *5f  c3  90  90  90  90  90  90 *92  90  90 ]A\_^_..........
fffff8000339cf70  ff  f5  56  57  41  54  41  55  41  56  41  57  48 *83  ec  70 ..VWATAUAVAWH..p

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8000339cf80, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, 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!PspWow64GetContextThreadOnAmd64+10
fffff800`0339cf80 0300            add     eax,dword ptr [rax]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS:  0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x1E

PROCESS_NAME:  TestDrive2.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a3ae660 -- (.trap 0xfffff8800a3ae660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80058dcb60
rdx=0000000008a8dd30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000339cf80 rsp=fffff8800a3ae7f0 rbp=fffff8800a3aeb60
 r8=fffffa80057d4f01  r9=0000000000000201 r10=fffff800033caba0
r11=fffff800030dcf78 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!PspWow64GetContextThreadOnAmd64+0x10:
fffff800`0339cf80 0300            add     eax,dword ptr [rax] ds:e701:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800031295d8 to fffff800030ddd00

STACK_TEXT:  
fffff880`0a3addd8 fffff800`031295d8 : 00000000`0000001e ffffffff`c0000005 fffff800`0339cf80 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a3adde0 fffff800`030dd382 : fffff880`0a3ae5b8 00000000`000002cc fffff880`0a3ae660 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`0a3ae480 fffff800`030dbefa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000002cc : nt!KiExceptionDispatch+0xc2
fffff880`0a3ae660 fffff800`0339cf80 : fffff880`0a3ae120 00000000`08f7fa70 00000000`08f7fa50 00000000`08f7f580 : nt!KiPageFault+0x23a
fffff880`0a3ae7f0 fffffa80`0821c010 : fffffa80`0858dbb0 fffffa80`085ed070 00000000`00000000 fffffa80`0a308878 : nt!PspWow64GetContextThreadOnAmd64+0x10
fffff880`0a3ae830 fffffa80`0858dbb0 : fffffa80`085ed070 00000000`00000000 fffffa80`0a308878 fffff680`00045468 : 0xfffffa80`0821c010
fffff880`0a3ae838 fffffa80`085ed070 : 00000000`00000000 fffffa80`0a308878 fffff680`00045468 00000000`08a8ee01 : 0xfffffa80`0858dbb0
fffff880`0a3ae840 00000000`00000000 : fffffa80`0a308878 fffff680`00045468 00000000`08a8ee01 00000000`08a8ee01 : 0xfffffa80`085ed070


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
5 errors : !nt (fffff8000339cf45-fffff8000339cf7d)
fffff8000339cf40  8d  10  03  00  00 *08  33  cd  e8  03  82  d3  ff *08  8b  9d ......3.........
...
fffff8000339cf60  5d  41  5c  5f  5e *5f  c3  90  90  90  90  90  90 *92  90  90 ]A\_^_..........
fffff8000339cf70  ff  f5  56  57  41  54  41  55  41  56  41  57  48 *83  ec  70 ..VWATAUAVAWH..p

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
My System SpecsSystem Spec
22 Jul 2011   #3
ari277

WINDOWS 7 HOME PREMIUM X64
 
 
Hi

Hi i already unistall Smart defrag 2! and update the bluetooth driver from TOSHIBA website.
I run the memory test from windows but he say me nothing problem is founded.
Now i go to test with memtest 86+
Thanks for help!
My System SpecsSystem Spec
.

22 Jul 2011   #4
ari277

WINDOWS 7 HOME PREMIUM X64
 
 
Unistall and update

I unistall Mouse driver HUD and update some driver. I hope the problem is solved! thanks!
My System SpecsSystem Spec
Reply

 BSOD 1e Win 7 x64




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 12:35.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App