Blue screen
Résolu
magricop
-
john -
john -
Bonjour,
depuis que j'ai ma nouvelle config il arrive une fois sur trois que windows plante pendant que je joue et ce quelque soit
le jeu en m'affichant un ecran bleu, je ne sais plus quoi faire.
voici ma config: asus p5e
core 2 quad q9450
2 x 2 go de ddr 6400 g skill
hd 4870 512 mo power color
boitier antec p 182
ALimentation HKC 630 Watt modulaire
Voici aussi ce que j'ai pu tirer de deux fichier dump generer par windows apres les crash.
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ammouri family\AppData\Local\Temp\WERABCD.tmp\Mini083008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81c3d000 PsLoadedModuleList = 0x81d54c70
Debug session time: Sat Aug 30 06:41:41.940 2008 (GMT+2)
System Uptime: 0 days 11:58:31.306
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {a298e314, 1, 8a77753b, 0}
Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a298e314, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8a77753b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
AUTOBUG_OS_SKU: 1
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d74868
Unable to read MiSystemVaType memory at 81d54420
a298e314
FAULTING_IP:
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
8a77753b 895104 mov dword ptr [ecx+4],edx
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: iw3sp.exe
CURRENT_IRQL: 0
TRAP_FRAME: d833c954 -- (.trap 0xffffffffd833c954)
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 81c97bb4 to 81ce2155
STACK_TEXT:
d833c93c 81c97bb4 00000001 a298e314 00000000 nt!MmAccessFault+0x10a
d833c93c 8a77753b 00000001 a298e314 00000000 nt!KiTrap0E+0xdc
d833c9d4 8a77815b a8c56560 00000000 86259da0 dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0
d833c9f0 8a7778eb 86259da0 00000000 893006a0 dxgkrnl!VIDMM_GLOBAL::NotifyAllocationEviction+0x37
d833ca58 8a7760ea d833cb88 d833cb28 d833cb54 dxgkrnl!VIDMM_GLOBAL::ProcessDeferredCommand+0x392
d833ca70 8a77613d d833cb4c 893006a0 893006a0 dxgkrnl!VidMmiProcessSystemCommand+0x20
d833ca8c 8a76c94a 89304be0 86b658b8 d833cacc dxgkrnl!VidSchiSubmitSystemCommand+0x2d
d833ca9c 8a74e9a1 893006a0 893006a0 86b76a18 dxgkrnl!VidSchiSubmitQueueCommand+0x7b
d833cacc 8a76c876 86b84000 d833caf0 86b658b8 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
d833caf4 8a777e74 013006a0 86c5e000 86c5e000 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
d833cb0c 8a777d97 86b658b8 8a7760ca d833cb4c dxgkrnl!VidSchSubmitSystemCommand+0xa6
d833cb38 8a77802e d833cb4c a8c56560 86259da0 dxgkrnl!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x40
d833cb70 8a777c6f d833cb88 00000000 a29131a8 dxgkrnl!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c
d833cbac 8a7783bd 00000000 00000000 a388d5b8 dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x8d
d833cbcc 8a779154 a29131a8 00000000 00000000 dxgkrnl!VIDMM_GLOBAL::CloseAllocation+0x37
d833cc38 8a779955 00000000 00000000 a6bf0890 dxgkrnl!DXGDEVICE::DestroyAllocations+0x176
d833cc94 8a779eb2 d833ccf0 00000001 52455f69 dxgkrnl!DXGDEVICE::DestroyAllocation+0x28a
d833cd58 81c94a7a 0fa4fe68 0fa4fe78 76e19a94 dxgkrnl!DxgkDestroyAllocation+0x538
d833cd58 76e19a94 0fa4fe68 0fa4fe78 76e19a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0fa4fe78 00000000 00000000 00000000 00000000 0x76e19a94
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
8a77753b 895104 mov dword ptr [ecx+4],edx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64
FAILURE_BUCKET_ID: 0x50_W_dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
BUCKET_ID: 0x50_W_dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
Followup: MachineOwner
---------
3: kd> .trap 0xffffffffd833c954
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
3: kd> lmvm dxgkrnl
start end module name
8a74b000 8a7ea000 dxgkrnl (pdb symbols) c:\symbols\dxgkrnl.pdb\2F308EDE36614CBAAE4C5F47132D6D312\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Mapped memory image file: c:\symbols\dxgkrnl.sys\47918C649f000\dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Sat Jan 19 06:36:36 2008 (47918C64)
CheckSum: 0009A1A8
ImageSize: 0009F000
File version: 6.0.6001.18000
Product version: 6.0.6001.18000
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgkrnl.sys
OriginalFilename: dxgkrnl.sys
ProductVersion: 6.0.6001.18000
FileVersion: 6.0.6001.18000 (longhorn_rtm.080118-1840)
FileDescription: DirectX Graphics Kernel
LegalCopyright: © Microsoft Corporation. All rights reserved.
3: kd> .trap 0xffffffffd833c954
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
depuis que j'ai ma nouvelle config il arrive une fois sur trois que windows plante pendant que je joue et ce quelque soit
le jeu en m'affichant un ecran bleu, je ne sais plus quoi faire.
voici ma config: asus p5e
core 2 quad q9450
2 x 2 go de ddr 6400 g skill
hd 4870 512 mo power color
boitier antec p 182
ALimentation HKC 630 Watt modulaire
Voici aussi ce que j'ai pu tirer de deux fichier dump generer par windows apres les crash.
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ammouri family\AppData\Local\Temp\WERABCD.tmp\Mini083008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81c3d000 PsLoadedModuleList = 0x81d54c70
Debug session time: Sat Aug 30 06:41:41.940 2008 (GMT+2)
System Uptime: 0 days 11:58:31.306
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {a298e314, 1, 8a77753b, 0}
Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a298e314, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8a77753b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
AUTOBUG_OS_SKU: 1
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d74868
Unable to read MiSystemVaType memory at 81d54420
a298e314
FAULTING_IP:
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
8a77753b 895104 mov dword ptr [ecx+4],edx
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: iw3sp.exe
CURRENT_IRQL: 0
TRAP_FRAME: d833c954 -- (.trap 0xffffffffd833c954)
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 81c97bb4 to 81ce2155
STACK_TEXT:
d833c93c 81c97bb4 00000001 a298e314 00000000 nt!MmAccessFault+0x10a
d833c93c 8a77753b 00000001 a298e314 00000000 nt!KiTrap0E+0xdc
d833c9d4 8a77815b a8c56560 00000000 86259da0 dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0
d833c9f0 8a7778eb 86259da0 00000000 893006a0 dxgkrnl!VIDMM_GLOBAL::NotifyAllocationEviction+0x37
d833ca58 8a7760ea d833cb88 d833cb28 d833cb54 dxgkrnl!VIDMM_GLOBAL::ProcessDeferredCommand+0x392
d833ca70 8a77613d d833cb4c 893006a0 893006a0 dxgkrnl!VidMmiProcessSystemCommand+0x20
d833ca8c 8a76c94a 89304be0 86b658b8 d833cacc dxgkrnl!VidSchiSubmitSystemCommand+0x2d
d833ca9c 8a74e9a1 893006a0 893006a0 86b76a18 dxgkrnl!VidSchiSubmitQueueCommand+0x7b
d833cacc 8a76c876 86b84000 d833caf0 86b658b8 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
d833caf4 8a777e74 013006a0 86c5e000 86c5e000 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
d833cb0c 8a777d97 86b658b8 8a7760ca d833cb4c dxgkrnl!VidSchSubmitSystemCommand+0xa6
d833cb38 8a77802e d833cb4c a8c56560 86259da0 dxgkrnl!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x40
d833cb70 8a777c6f d833cb88 00000000 a29131a8 dxgkrnl!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c
d833cbac 8a7783bd 00000000 00000000 a388d5b8 dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x8d
d833cbcc 8a779154 a29131a8 00000000 00000000 dxgkrnl!VIDMM_GLOBAL::CloseAllocation+0x37
d833cc38 8a779955 00000000 00000000 a6bf0890 dxgkrnl!DXGDEVICE::DestroyAllocations+0x176
d833cc94 8a779eb2 d833ccf0 00000001 52455f69 dxgkrnl!DXGDEVICE::DestroyAllocation+0x28a
d833cd58 81c94a7a 0fa4fe68 0fa4fe78 76e19a94 dxgkrnl!DxgkDestroyAllocation+0x538
d833cd58 76e19a94 0fa4fe68 0fa4fe78 76e19a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0fa4fe78 00000000 00000000 00000000 00000000 0x76e19a94
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
8a77753b 895104 mov dword ptr [ecx+4],edx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64
FAILURE_BUCKET_ID: 0x50_W_dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
BUCKET_ID: 0x50_W_dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+a0
Followup: MachineOwner
---------
3: kd> .trap 0xffffffffd833c954
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
3: kd> lmvm dxgkrnl
start end module name
8a74b000 8a7ea000 dxgkrnl (pdb symbols) c:\symbols\dxgkrnl.pdb\2F308EDE36614CBAAE4C5F47132D6D312\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Mapped memory image file: c:\symbols\dxgkrnl.sys\47918C649f000\dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Sat Jan 19 06:36:36 2008 (47918C64)
CheckSum: 0009A1A8
ImageSize: 0009F000
File version: 6.0.6001.18000
Product version: 6.0.6001.18000
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: dxgkrnl.sys
OriginalFilename: dxgkrnl.sys
ProductVersion: 6.0.6001.18000
FileVersion: 6.0.6001.18000 (longhorn_rtm.080118-1840)
FileDescription: DirectX Graphics Kernel
LegalCopyright: © Microsoft Corporation. All rights reserved.
3: kd> .trap 0xffffffffd833c954
ErrCode = 00000002
eax=a8c56674 ebx=00000000 ecx=a298e310 edx=9fa08434 esi=8ea0a278 edi=a8c56560
eip=8a77753b esp=d833c9c8 ebp=d833c9d4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
dxgkrnl!VIDMM_SEGMENT::MarkResourcesForEviction+0xa0:
8a77753b 895104 mov dword ptr [ecx+4],edx ds:0023:a298e314=????????
A voir également:
- Ntoskrnl.exe
- Blue screen windows 10 - Guide
- Screen whatsapp - Accueil - Messagerie instantanée
- Blue griffon - Télécharger - HTML
- Apowersoft screen recorder - Télécharger - Capture d'écran
- Blue iris - Télécharger - Divers Utilitaires
5 réponses
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ammouri family\AppData\Local\Temp\WER5051.tmp\Mini090108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81c1f000 PsLoadedModuleList = 0x81d36c70
Debug session time: Mon Sep 1 02:17:49.183 2008 (GMT+2)
System Uptime: 0 days 8:10:21.954
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81e7781a, c5bc28d8, 0}
Probably caused by : ntkrpamp.exe ( nt!CmpCallbackFetchCallContext+7e )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81e7781a, The address that the exception occurred at
Arg3: c5bc28d8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
AUTOBUG_OS_SKU: 1
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!CmpCallbackFetchCallContext+7e
81e7781a 894810 mov dword ptr [eax+10h],ecx
TRAP_FRAME: c5bc28d8 -- (.trap 0xffffffffc5bc28d8)
ErrCode = 00000002
eax=0000001d ebx=a8a61ca0 ecx=00000000 edx=00000005 esi=8cbcd540 edi=0000001d
eip=81e7781a esp=c5bc294c ebp=c5bc294c iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
nt!CmpCallbackFetchCallContext+0x7e:
81e7781a 894810 mov dword ptr [eax+10h],ecx ds:0023:0000002d=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: AssassinsCreed_
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81e76c44 to 81e7781a
STACK_TEXT:
c5bc294c 81e76c44 0000001d bcc0974b c5bc2a10 nt!CmpCallbackFetchCallContext+0x7e
c5bc29c8 81e22791 0000001d c5bc29f4 8cbcd540 nt!CmpCallCallBacks+0x4ba
c5bc2a10 81e33c21 0000001d 00000000 c5bc2aac nt!CmPostCallbackNotification+0x55
c5bc2b78 81e64f48 bc3f7918 8435ba80 84f42c30 nt!CmpParseKey+0xc7f
c5bc2c08 81e3d0ca 00000018 c5bc2c60 00000040 nt!ObpLookupObjectName+0x11e
c5bc2c68 81e340a4 03f8fc58 8435ba80 00000001 nt!ObOpenObjectByName+0x13c
c5bc2d34 81e34163 03f8fd34 00020019 03f8fc58 nt!CmOpenKey+0x1b1
c5bc2d50 81c76a7a 03f8fd34 00020019 03f8fc58 nt!NtOpenKey+0x16
c5bc2d50 77d79a94 03f8fd34 00020019 03f8fc58 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
03f8fc94 00000000 00000000 00000000 00000000 0x77d79a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpCallbackFetchCallContext+7e
81e7781a 894810 mov dword ptr [eax+10h],ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpCallbackFetchCallContext+7e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4812bd71
FAILURE_BUCKET_ID: 0x8E_nt!CmpCallbackFetchCallContext+7e
BUCKET_ID: 0x8E_nt!CmpCallbackFetchCallContext+7e
Followup: MachineOwner
---------
3: kd> .trap 0xffffffffc5bc28d8
ErrCode = 00000002
eax=0000001d ebx=a8a61ca0 ecx=00000000 edx=00000005 esi=8cbcd540 edi=0000001d
eip=81e7781a esp=c5bc294c ebp=c5bc294c iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
nt!CmpCallbackFetchCallContext+0x7e:
81e7781a 894810 mov dword ptr [eax+10h],ecx ds:0023:0000002d=????????
3: kd> lmvm nt
start end module name
81c1f000 81fd8000 nt (pdb symbols) c:\symbols\ntkrpamp.pdb\BA057DABC623462B9EF1D336E0F6BDAD2\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: c:\symbols\ntkrnlpa.exe\4812BD713b9000\ntkrnlpa.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Sat Apr 26 07:28:17 2008 (4812BD71)
CheckSum: 003772A9
ImageSize: 003B9000
File version: 6.0.6001.18063
Product version: 6.0.6001.18063
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 6.0.6001.18063
FileVersion: 6.0.6001.18063 (vistasp1_gdr.080425-1930)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ammouri family\AppData\Local\Temp\WER5051.tmp\Mini090108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81c1f000 PsLoadedModuleList = 0x81d36c70
Debug session time: Mon Sep 1 02:17:49.183 2008 (GMT+2)
System Uptime: 0 days 8:10:21.954
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81e7781a, c5bc28d8, 0}
Probably caused by : ntkrpamp.exe ( nt!CmpCallbackFetchCallContext+7e )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81e7781a, The address that the exception occurred at
Arg3: c5bc28d8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
AUTOBUG_OS_SKU: 1
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!CmpCallbackFetchCallContext+7e
81e7781a 894810 mov dword ptr [eax+10h],ecx
TRAP_FRAME: c5bc28d8 -- (.trap 0xffffffffc5bc28d8)
ErrCode = 00000002
eax=0000001d ebx=a8a61ca0 ecx=00000000 edx=00000005 esi=8cbcd540 edi=0000001d
eip=81e7781a esp=c5bc294c ebp=c5bc294c iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
nt!CmpCallbackFetchCallContext+0x7e:
81e7781a 894810 mov dword ptr [eax+10h],ecx ds:0023:0000002d=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: AssassinsCreed_
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81e76c44 to 81e7781a
STACK_TEXT:
c5bc294c 81e76c44 0000001d bcc0974b c5bc2a10 nt!CmpCallbackFetchCallContext+0x7e
c5bc29c8 81e22791 0000001d c5bc29f4 8cbcd540 nt!CmpCallCallBacks+0x4ba
c5bc2a10 81e33c21 0000001d 00000000 c5bc2aac nt!CmPostCallbackNotification+0x55
c5bc2b78 81e64f48 bc3f7918 8435ba80 84f42c30 nt!CmpParseKey+0xc7f
c5bc2c08 81e3d0ca 00000018 c5bc2c60 00000040 nt!ObpLookupObjectName+0x11e
c5bc2c68 81e340a4 03f8fc58 8435ba80 00000001 nt!ObOpenObjectByName+0x13c
c5bc2d34 81e34163 03f8fd34 00020019 03f8fc58 nt!CmOpenKey+0x1b1
c5bc2d50 81c76a7a 03f8fd34 00020019 03f8fc58 nt!NtOpenKey+0x16
c5bc2d50 77d79a94 03f8fd34 00020019 03f8fc58 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
03f8fc94 00000000 00000000 00000000 00000000 0x77d79a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpCallbackFetchCallContext+7e
81e7781a 894810 mov dword ptr [eax+10h],ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpCallbackFetchCallContext+7e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4812bd71
FAILURE_BUCKET_ID: 0x8E_nt!CmpCallbackFetchCallContext+7e
BUCKET_ID: 0x8E_nt!CmpCallbackFetchCallContext+7e
Followup: MachineOwner
---------
3: kd> .trap 0xffffffffc5bc28d8
ErrCode = 00000002
eax=0000001d ebx=a8a61ca0 ecx=00000000 edx=00000005 esi=8cbcd540 edi=0000001d
eip=81e7781a esp=c5bc294c ebp=c5bc294c iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
nt!CmpCallbackFetchCallContext+0x7e:
81e7781a 894810 mov dword ptr [eax+10h],ecx ds:0023:0000002d=????????
3: kd> lmvm nt
start end module name
81c1f000 81fd8000 nt (pdb symbols) c:\symbols\ntkrpamp.pdb\BA057DABC623462B9EF1D336E0F6BDAD2\ntkrpamp.pdb
Loaded symbol image file: ntkrpamp.exe
Mapped memory image file: c:\symbols\ntkrnlpa.exe\4812BD713b9000\ntkrnlpa.exe
Image path: ntkrpamp.exe
Image name: ntkrpamp.exe
Timestamp: Sat Apr 26 07:28:17 2008 (4812BD71)
CheckSum: 003772A9
ImageSize: 003B9000
File version: 6.0.6001.18063
Product version: 6.0.6001.18063
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrpamp.exe
OriginalFilename: ntkrpamp.exe
ProductVersion: 6.0.6001.18063
FileVersion: 6.0.6001.18063 (vistasp1_gdr.080425-1930)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
j'ai fait un mem test avec ultimate boot cd et il s'avere que ma ram est defectueuse je la rapporte demain.
Ps: Merci pour rien
Ps: Merci pour rien
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question