Witam mam asus f3sg jest nowy nie dokładano żadnych pamjęci system wgrany od nowa z recovery cd lecz męczy go podczas zwyczajnej pracy bluescreen i reset prawie za każdym razem inny błąd co zrobić a oto błędy z folderu minidump odczytane Debugging Tools for Windows
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Piotr\Desktop\Nowy folder (4)\Mini042909-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/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x81835000 PsLoadedModuleList = 0x8194cc70
Debug session time: Wed Apr 29 19:33:16.041 2009 (GMT+2)
System Uptime: 0 days 0:58:30.556
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {be947e9d, 2, 1, 818f2101}
Unable to load image \SystemRoot\System32\Drivers\dvb7700all.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dvb7700all.sys
*** ERROR: Module load completed but symbols could not be loaded for dvb7700all.sys
Probably caused by : ks.sys ( ks!CKsPin::TransferKsIrp+77 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: be947e9d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 818f2101, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8196c868
Unable to read MiSystemVaType memory at 8194c420
be947e9d
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiReplenishBitMap+1c3
818f2101 e8b3fdffff call nt!RtlAreBitsClear (818f1eb9)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 803ec868 -- (.trap 0xffffffff803ec868)
ErrCode = 00000002
eax=00000200 ebx=81947ea0 ecx=0002da00 edx=fffffe00 esi=00000200 edi=00000001
eip=818f2101 esp=803ec8dc ebp=803ec9b0 iopl=0 nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
nt!MiReplenishBitMap+0x1c3:
818f2101 e8b3fdffff call nt!RtlAreBitsClear (818f1eb9)
Resetting default scope
LAST_CONTROL_TRANSFER: from 818f2101 to 8188fd84
STACK_TEXT:
803ec868 818f2101 badb0d00 fffffe00 00000000 nt!KiTrap0E+0x2ac
803ec9b0 818f160d 00000003 00000000 00000003 nt!MiReplenishBitMap+0x1c3
803eca08 818c1b51 c05a0cd0 00000003 8621ad58 nt!MiInsertCachedPte+0x1e9
803eca40 818a8e6e b419aa00 8621ad58 8621ad58 nt!MmUnmapLockedPages+0xc2
803eca94 8186f353 8621ad58 84a66008 849edbc0 nt!MmUnlockPages+0x2d
803ecac4 8d79e33f 84c72e00 858d8f04 803ecaec nt!IopfCompleteRequest+0x388
803ecad4 8d79db8a 849edbc0 858d8e00 803ecaf4 ks!CKsPin::TransferKsIrp+0x77
803ecaec 8d79d2de 849edbc0 858d8e00 84a66008 ks!KspTransferKsIrp+0x15
803ecb10 8d79d183 858d8e00 858d8f04 00000000 ks!CKsQueue::ForwardIrp+0x126
803ecb2c 8d79e729 84a66008 81805ec0 85b79530 ks!CKsQueue::ForwardWaitingIrps+0x29
803ecb48 8d79e7fd 84a66008 02b79530 00000002 ks!CKsQueue::UnlockStreamPointer+0xc9
803ecb68 8d79d1af 02a66008 00000000 803ecbb4 ks!CKsQueue::DeleteStreamPointer+0xa2
803ecb78 8e918b44 85b79568 85b79568 84c513c8 ks!KsStreamPointerDelete+0x15
WARNING: Stack unwind information not available. Following frames may be wrong.
803ecbb4 8e91b758 00001e00 00000000 8469581f dvb7700all+0x5b44
803ecbf4 8186f0e4 00000000 84695740 013c9000 dvb7700all+0x8758
803ecc28 8d6c8b37 818894f4 85bed008 00000000 nt!IopfCompleteRequest+0x11d
803ecc64 8d6cb9fd 86641028 84695740 a5a40cf0 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6cb
803ecc94 8d6cd06a 86641028 39585043 86641bf8 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x4f5
803eccc0 8d6c6274 86641028 86641bf8 86641002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x122
803ecce8 818eb510 86641c04 34776478 00000000 USBPORT!USBPORT_Xdpc_Worker+0x274
803ecd50 818e9f9d 00000000 0000000e ffffee60 nt!KiRetireDpcList+0x147
803ecd54 00000000 0000000e ffffee60 d5e8086a nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_IP:
ks!CKsPin::TransferKsIrp+77
8d79e33f 8b4510 mov eax,dword ptr [ebp+10h]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: ks!CKsPin::TransferKsIrp+77
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ks
IMAGE_NAME: ks.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918f61
FAILURE_BUCKET_ID: 0xA_ks!CKsPin::TransferKsIrp+77
BUCKET_ID: 0xA_ks!CKsPin::TransferKsIrp+77
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Piotr\Desktop\Nowy folder (4)\Mini043009-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/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x81846000 PsLoadedModuleList = 0x8195dc70
Debug session time: Thu Apr 30 09:42:12.947 2009 (GMT+2)
System Uptime: 0 days 0:00:22.868
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 4a63fbc1, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 4a63fbc1
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41287
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: 8ab4b9c4 -- (.trap 0xffffffff8ab4b9c4)
ErrCode = 00000000
eax=00000000 ebx=0000000e ecx=0000000f edx=00000000 esi=83f683e8 edi=92040000
eip=81a6b9d7 esp=8ab4ba38 ebp=8ab4ba78 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!CcMapData+0xaf:
81a6b9d7 8a17 mov dl,byte ptr [edi] ds:0023:92040000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 818a0bb4 to 818eb155
STACK_TEXT:
8ab4b7ac 818a0bb4 00000000 4a63fbc1 00000000 nt!MmAccessFault+0x10a
8ab4b7ac 818e2310 00000000 4a63fbc1 00000000 nt!KiTrap0E+0xdc
8ab4b848 818cd6c4 83f683e8 864d9bf4 864d9bc0 nt!MiDetermineUserGlobalPteMask+0x67
8ab4b874 818cadc0 00000000 8195e7e0 92040000 nt!MiCompleteProtoPteFault+0x14c
8ab4b930 818ec0f3 92040000 8d235008 00000000 nt!MiDispatchFault+0xdc7
8ab4b9ac 818a0bb4 00000000 92040000 00000000 nt!MmAccessFault+0x10ac
8ab4b9ac 81a6b9d7 00000000 92040000 00000000 nt!KiTrap0E+0xdc
8ab4ba78 8a095987 89894238 8ab4bab0 00000400 nt!CcMapData+0xaf
8ab4baa0 8a051848 8f1feb38 8980ce40 00000000 Ntfs!NtfsMapStream+0x4a
8ab4bca0 8a09f963 8f1feb38 8eb8c150 8ab4bcc0 Ntfs!NtfsMountVolume+0xb1b
8ab4bcc4 8a01203e 8f1feb38 8eb8c150 00b0d67f Ntfs!NtfsCommonFileSystemControl+0x80
8ab4bd44 8187e41d 00000000 00000000 83f683e8 Ntfs!NtfsFspDispatch+0x264
8ab4bd7c 81a1ba1c 8f1feb38 b7017bf6 00000000 nt!ExpWorkerThread+0xfd
8ab4bdc0 81874a3e 8187e320 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+dc
818a0bb4 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+dc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12
FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc
BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Piotr\Desktop\Nowy folder (4)\Mini043009-02.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/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x8183e000 PsLoadedModuleList = 0x81955c70
Debug session time: Thu Apr 30 14:49:07.635 2009 (GMT+2)
System Uptime: 0 days 0:00:13.494
Loading Kernel Symbols
...............................................................
.........................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {bc9383a0, 1c, 1, 818f632c}
Probably caused by : intelppm.sys ( intelppm!C1Halt+4 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: bc9383a0, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 818f632c, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81975868
Unable to read MiSystemVaType memory at 81955420
bc9383a0
CURRENT_IRQL: 1c
FAULTING_IP:
nt!KeUpdateRunTime+df
818f632c c786801a000002000000 mov dword ptr [esi+1A80h],2
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 81933bd8 -- (.trap 0xffffffff81933bd8)
ErrCode = 00000002
eax=819383a5 ebx=00000000 ecx=81933c74 edx=00026161 esi=81936920 edi=8193a640
eip=818f632c esp=81933c4c ebp=81933c64 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!KeUpdateRunTime+0xdf:
818f632c c786801a000002000000 mov dword ptr [esi+1A80h],2 ds:0023:819383a0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 818f632c to 81898d84
STACK_TEXT:
81933bd8 818f632c badb0d00 00026161 84d7e7c0 nt!KiTrap0E+0x2ac
81933c64 818f602d ffffff02 000000d1 81933cf8 nt!KeUpdateRunTime+0xdf
81933c64 8a1e3406 ffffff02 000000d1 81933cf8 nt!KeUpdateSystemTime+0xed
81933ce4 8a1e434d 818f9e64 8690c600 81938790 intelppm!C1Halt+0x4
81933ce8 818f9e64 8690c600 81938790 81933d50 intelppm!C1Idle+0x5
81933cf8 818f9db2 868f1e70 00000000 83f8d2d8 nt!PpmCallIdleHandler+0x2e
81933d50 818f2f61 00000000 0000000e 00000000 nt!PoIdle+0x2d1
81933d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm!C1Halt+4
8a1e3406 c3 ret
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: intelppm!C1Halt+4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918a38
FAILURE_BUCKET_ID: 0xA_intelppm!C1Halt+4
BUCKET_ID: 0xA_intelppm!C1Halt+4
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Piotr\Desktop\Nowy folder (4)\Mini043009-03.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/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x81c07000 PsLoadedModuleList = 0x81d1ec70
Debug session time: Thu Apr 30 15:05:42.153 2009 (GMT+2)
System Uptime: 0 days 0:11:31.078
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {16, 2, 0, 8a13e104}
Probably caused by : hardware ( NETIO!RtlGetNextExpiredTimerWheelEntry+64 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8a13e104, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 81d3e868
Unable to read MiSystemVaType memory at 81d1e420
00000016
CURRENT_IRQL: 2
FAULTING_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+64
8a13e104 0b00 or eax,dword ptr [eax]
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: WerFault.exe
TRAP_FRAME: 8039dd2c -- (.trap 0xffffffff8039dd2c)
ErrCode = 00000000
eax=00000016 ebx=00000000 ecx=85b4e008 edx=00000041 esi=0000003f edi=8510af70
eip=8a13e104 esp=8039dda0 ebp=8039ddb0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
NETIO!RtlGetNextExpiredTimerWheelEntry+0x64:
8a13e104 0b00 or eax,dword ptr [eax] ds:0023:00000016=????????
Resetting default scope
MISALIGNED_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+64
8a13e104 0b00 or eax,dword ptr [eax]
LAST_CONTROL_TRANSFER: from 8a13e104 to 81c61d84
STACK_TEXT:
8039dd2c 8a13e104 badb0d00 00000041 8515fa18 nt!KiTrap0E+0x2ac
8039ddb0 8a272fc1 00000000 00000000 00000048 NETIO!RtlGetNextExpiredTimerWheelEntry+0x64
8039ddd0 8a273836 8510af70 8039de34 8039def0 tcpip!TcpProcessExpiredTcbTimers+0x21
8039de08 81cbdd00 85b59c98 00000000 5db932a5 tcpip!TcpPeriodicTimeoutHandler+0x17d
8039df28 81cbd8c0 8039df70 81cff902 8039df78 nt!KiTimerListExpire+0x367
8039df88 81cbd483 00000000 00000000 0000ad0b nt!KiTimerExpiration+0x22a
8039dff4 81cbb9f5 b310bd10 00000000 00000000 nt!KiRetireDpcList+0xba
8039dff8 b310bd10 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
WARNING: Frame IP not in any known module. Following frames may be wrong.
81cbb9f5 00000000 0000001b 00c7850f bb830000 0xb310bd10
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+64
8a13e104 0b00 or eax,dword ptr [eax]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+64
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_NETIO.SYS
BUCKET_ID: IP_MISALIGNED_NETIO.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\Piotr\Desktop\Nowy folder (4)\Mini043009-04.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/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x81c06000 PsLoadedModuleList = 0x81d1dc70
Debug session time: Thu Apr 30 15:34:21.872 2009 (GMT+2)
System Uptime: 0 days 0:25:03.843
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 8dc34081, b1476b24, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkRender+3b9 )
Followup: MachineOwner
---------
0: 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: c000001d, The exception code that was not handled
Arg2: 8dc34081, The address that the exception occurred at
Arg3: b1476b24, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {WYJ
FAULTING_IP:
dxgkrnl!DxgkRender+3b9
8dc34081 53 push ebx
TRAP_FRAME: b1476b24 -- (.trap 0xffffffffb1476b24)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=8dc34074 edi=00000000
eip=8dc34081 esp=b1476b98 ebp=b1476d58 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!DxgkRender+0x3b9:
8dc34081 53 push ebx
Resetting default scope
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: ehshell.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81c5da7a to 8dc34081
FAILED_INSTRUCTION_ADDRESS:
dxgkrnl!DxgkRender+3b9
8dc34081 53 push ebx
STACK_TEXT:
b1476d58 81c5da7a 000000d5 042eecb0 77709a94 dxgkrnl!DxgkRender+0x3b9
b1476d58 77709a94 000000d5 042eecb0 77709a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
042eecb0 00000000 00000000 00000000 00000000 0x77709a94
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DxgkRender+3b9
8dc34081 53 push ebx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgkrnl!DxgkRender+3b9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64
FAILURE_BUCKET_ID: 0x8E_BAD_IP_dxgkrnl!DxgkRender+3b9
BUCKET_ID: 0x8E_BAD_IP_dxgkrnl!DxgkRender+3b9
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Nowy folder (4)\Mini043009-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81c37000 PsLoadedModuleList = 0x81d4ec70
Debug session time: Thu Apr 30 17:09:30.278 2009 (GMT+2)
System Uptime: 0 days 0:13:07.201
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {1, 1b, 1, 81cee125}
Probably caused by : hardware ( nt!KiTrap0E+2ac )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000001, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81cee125, address which referenced memory
Debugging Details:
------------------
WORKER_ROUTINE:
+6912952f0277d834
00000001 ?? ???
WORK_ITEM: 81cee125
CURRENT_IRQL: 1b
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: ehshell.exe
TRAP_FRAME: 8c3f9be4 -- (.trap 0xffffffff8c3f9be4)
ErrCode = 00000002
eax=00000001 ebx=803d2b00 ecx=00000002 edx=00000000 esi=803d1120 edi=803d1120
eip=81cee125 esp=8c3f9c58 ebp=8c3f9c94 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiSwapThread+0x275:
81cee125 0000 add byte ptr [eax],al ds:0023:00000001=??
Resetting default scope
MISALIGNED_IP:
nt!KiSwapThread+275
81cee125 0000 add byte ptr [eax],al
LAST_CONTROL_TRANSFER: from 81cee125 to 81c91d24
STACK_TEXT:
8c3f9be4 81cee125 badb0d00 00000000 00000008 nt!KiTrap0E+0x2ac
8c3f9c94 81c8bcc8 85dae030 00000000 85d6e4a8 nt!KiSwapThread+0x275
8c3f9ce8 81e80421 85d6e4a8 00000006 81c0b501 nt!KeWaitForSingleObject+0x492
8c3f9d50 81c8ea1a 000008a0 00000000 00000000 nt!NtWaitForSingleObject+0xbe
8c3f9d50 77579a94 000008a0 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0bcdfb0c 00000000 00000000 00000000 00000000 0x77579a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+2ac
81c91d24 833d645cd68100 cmp dword ptr [nt!KiFreezeFlag (81d65c64)],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+2ac
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Nowy folder (4)\Mini043009-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81c18000 PsLoadedModuleList = 0x81d2fc70
Debug session time: Thu Apr 30 17:17:57.631 2009 (GMT+2)
System Uptime: 0 days 0:06:19.537
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
..
Unable to load image \SystemRoot\System32\Drivers\AsDsm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AsDsm.sys
*** ERROR: Module load completed but symbols could not be loaded for AsDsm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8234389f, 9d701230, 0}
Unable to load image \??\C:\Program Files\Common Files\Symantec Shared\SPBBC\SPBBCDrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SPBBCDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for SPBBCDrv.sys
Probably caused by : AsDsm.sys ( AsDsm+189f )
Followup: MachineOwner
---------
0: 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: 8234389f, The address that the exception occurred at
Arg3: 9d701230, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
AsDsm+189f
8234389f 3938 cmp dword ptr [eax],edi
TRAP_FRAME: 9d701230 -- (.trap 0xffffffff9d701230)
ErrCode = 00000000
eax=00000063 ebx=84f64540 ecx=8234649c edx=a6865248 esi=823465a0 edi=85021be0
eip=8234389f esp=9d7012a4 ebp=9d7012ac iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
AsDsm+0x189f:
8234389f 3938 cmp dword ptr [eax],edi ds:0023:00000063=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: SearchProtocolH
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82347c00 to 8234389f
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9d7012ac 82347c00 85021be0 84f64550 86c21248 AsDsm+0x189f
9d7012c0 81cd3fd3 86c21248 84f64540 85021be0 AsDsm+0x5c00
9d7012d8 81e37120 00000000 00000000 85021bc8 nt!IofCallDriver+0x63
9d70131c 81e5c5e7 85021be0 81fd8110 85021bc8 nt!IopDeleteFile+0x178
9d701338 81c698c9 85021be0 00000000 849068b0 nt!ObpRemoveObjectRoutine+0x13d
9d701360 81e354ca 8ac00058 849068b0 00001bb8 nt!ObfDereferenceObject+0xa1
9d7013a0 81e356c0 8ac00058 ab224770 84343248 nt!ObpCloseHandleTableEntry+0x24e
9d7013d0 81e358e5 84343248 00000000 00000000 nt!ObpCloseHandle+0x73
9d7013e4 81c6fa1a 80001bb8 9d70147c 81c6d419 nt!NtClose+0x20
9d7013e4 81c6d419 80001bb8 9d70147c 81c6d419 nt!KiFastCallEntry+0x12a
9d701460 8231f81d 80001bb8 85028b80 84f9fc80 nt!ZwClose+0x11
9d70147c 8231ff07 84f90000 85028b80 85c2e6bc fltmgr!FltpGetNormalizedFileNameWorker+0xc7
9d701494 8231d1a1 84f9fc80 85028b80 84f9fc80 fltmgr!FltpGetNormalizedFileName+0x19
9d7014ac 82307e3b 84f9fc80 00000000 84f9fc80 fltmgr!FltpCreateFileNameInformation+0x81
9d7014cc 82307f88 86ac4b48 00000000 00000000 fltmgr!HandleStreamListNotSupported+0x125
9d7014fc 82308654 c00000bb b1b7e4a8 9d70178c fltmgr!FltpGetFileNameInformation+0xc6
9d701524 9345f746 00028b88 00000101 9d7017b4 fltmgr!FltGetFileNameInformation+0x120
9d701544 93468fb3 00000006 9d701560 9346984e SPBBCDrv+0x15746
9d701550 9346984e 9d701658 00000006 9d701598 SPBBCDrv+0x1efb3
9d701560 93469b34 9d701658 00000005 00000006 SPBBCDrv+0x1f84e
9d701598 9346979f 9d701698 b4d417a8 b1b7e480 SPBBCDrv+0x1fb34
9d7015b8 934698c9 9d701698 b4d417a8 b1b7e010 SPBBCDrv+0x1f79f
9d7015d8 934587a2 00000002 9d701698 b1b7e000 SPBBCDrv+0x1f8c9
9d701634 93459dd6 9d70178c 00701754 00000002 SPBBCDrv+0xe7a2
9d701724 9345a9cb 9d70178c 9d701754 9d70178c SPBBCDrv+0xfdd6
9d701758 9345e89e 00000000 85028b88 89bcab60 SPBBCDrv+0x109cb
9d701774 9345c945 9d70178c 85028b88 00000001 SPBBCDrv+0x1489e
9d7017d0 9345ccd5 00028b88 9d701810 aa7e8038 SPBBCDrv+0x12945
9d7017f0 82302809 aa7e8038 9d701810 9d701830 SPBBCDrv+0x12cd5
9d70184c 82304ff8 9d70188c 00000000 85c599e8 fltmgr!FltpPerformPreCallbacks+0x2e5
9d701860 82317fc0 9d70188c 8231688c 00000000 fltmgr!FltpPassThroughInternal+0x32
9d701874 82318631 9d70188c 82346520 86c21248 fltmgr!FltpCreateInternal+0x24
9d7018b8 81cd3fd3 86ac4cd0 86ac4858 85c59810 fltmgr!FltpCreate+0x28f
9d7018d0 823479bc 85c488a0 86c21248 85c59810 nt!IofCallDriver+0x63
9d7018f0 81cd3fd3 ab204a50 000014b4 84ddb244 AsDsm+0x59bc
9d701908 81e38ce1 d6ec1726 84d770ac 866885b0 nt!IofCallDriver+0x63
9d7019d8 81e5e3cf 866885c8 00000000 84d77008 nt!IopParseDevice+0xf61
9d701a68 81e360c6 00000000 9d701ac0 00000240 nt!ObpLookupObjectName+0x5a8
9d701ac8 81e37bc3 9d701c40 00000000 00000000 nt!ObOpenObjectByName+0x13c
9d701b3c 81e28627 9d701c6c 80000001 9d701c40 nt!IopCreateFile+0x63b
9d701b84 81c6fa1a 9d701c6c 80000001 9d701c40 nt!NtOpenFile+0x2a
9d701b84 81c6dee1 9d701c6c 80000001 9d701c40 nt!KiFastCallEntry+0x12a
9d701c14 823437a4 9d701c6c 80000001 9d701c40 nt!ZwOpenFile+0x11
9d701c70 8234399a 86c45c00 85c48890 00000000 AsDsm+0x17a4
9d701c88 82347e89 b5c10c00 01294946 00000010 AsDsm+0x199a
9d701cd8 81cd3fd3 00c21248 01294870 85c48890 AsDsm+0x5e89
9d701cf0 81e645e5 000004fc 01048488 81e28d90 nt!IofCallDriver+0x63
9d701d10 81e28deb 86c21248 85c43b28 00000001 nt!IopSynchronousServiceTail+0x1d9
9d701d30 81c6fa1a 000004fc 00000000 00000000 nt!NtQueryDirectoryFile+0x5b
9d701d30 77009a94 000004fc 00000000 00000000 nt!KiFastCallEntry+0x12a
010484c4 00000000 00000000 00000000 00000000 0x77009a94
STACK_COMMAND: kb
FOLLOWUP_IP:
AsDsm+189f
8234389f 3938 cmp dword ptr [eax],edi
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: AsDsm+189f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AsDsm
IMAGE_NAME: AsDsm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46bc5723
FAILURE_BUCKET_ID: 0x8E_AsDsm+189f
BUCKET_ID: 0x8E_AsDsm+189f
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Nowy folder (4)\Mini043009-07.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81c4b000 PsLoadedModuleList = 0x81d62c70
Debug session time: Thu Apr 30 17:39:55.763 2009 (GMT+2)
System Uptime: 0 days 0:00:11.606
Loading Kernel Symbols
...............................................................
.........................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81e4e945, 8af6b820, 0}
Probably caused by : pci.sys ( pci!PciGetInterruptConnectionData+32 )
Followup: MachineOwner
---------
0: 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: 81e4e945, The address that the exception occurred at
Arg3: 8af6b820, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!CmpGetValueListFromCache+4f
81e4e945 a14408d881 mov eax,dword ptr [nt!CmpCacheTable (81d80844)]
TRAP_FRAME: 8af6b820 -- (.trap 0xffffffff8af6b820)
ErrCode = 00000000
eax=00000001 ebx=3b0fca07 ecx=8438e020 edx=00204863 esi=8da19908 edi=8ac26008
eip=81e4e945 esp=8af6b894 ebp=8af6b8a4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
nt!CmpGetValueListFromCache+0x4f:
81e4e945 a14408d881 mov eax,dword ptr [nt!CmpCacheTable (81d80844)] ds:0023:81d80844=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 7
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81e4f5f0 to 81e4e945
STACK_TEXT:
8af6b8a4 81e4f5f0 8af6b8d0 8af6b8e4 8af6b8e0 nt!CmpGetValueListFromCache+0x4f
8af6b908 81e508ec 8af6b998 8af6b94c 8af6b940 nt!CmpFindValueByNameFromCache+0x47
8af6b97c 81e50e35 8da3d520 00000001 8da3c588 nt!CmQueryValueKey+0x311
8af6ba30 81ca2a1a 80000180 8af6baf0 00000001 nt!NtQueryValueKey+0x2e5
8af6ba30 81ca1409 80000180 8af6baf0 00000001 nt!KiFastCallEntry+0x12a
8af6bac0 81e1d00b 80000180 8af6baf0 00000001 nt!ZwQueryValueKey+0x11
8af6bafc 81de2207 80000180 81e85f70 8af6bb28 nt!IopGetRegistryValue+0x9c
8af6bb30 81dd079f 85130b70 806ee2cc 00000000 nt!PnpGetDevicePropertyData+0xb0
8af6bb68 806fe476 85130b70 806ee2cc 00000000 nt!IoGetDevicePropertyData+0x4d
8af6bba8 806fec12 85130c28 8af6bbcc 00000000 pci!PciGetInterruptConnectionData+0x32
8af6bbd4 806f8149 85130c28 00000000 8da008c8 pci!PciProcessStartResources+0x72
8af6bce4 806e70bf 86b61b88 86b61bf8 85130c28 pci!PciDevice_Start+0xd7
8af6bd08 81d06fd3 85130c28 86b61b88 843646b8 pci!PciDispatchPnpPower+0xaf
8af6bd20 806b9dd3 81d4d13c 8438e020 843646cc nt!IofCallDriver+0x63
8af6bd44 81c83445 843646b8 00000000 8438e020 acpi!ACPIFilterIrpStartDeviceWorker+0x67
8af6bd7c 81e20b18 843646cc 1cd51608 00000000 nt!ExpWorkerThread+0xfd
8af6bdc0 81c79a2e 81c83348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
pci!PciGetInterruptConnectionData+32
806fe476 3d230000c0 cmp eax,0C0000023h
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: pci!PciGetInterruptConnectionData+32
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: pci
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b89
FAILURE_BUCKET_ID: 0x8E_pci!PciGetInterruptConnectionData+32
BUCKET_ID: 0x8E_pci!PciGetInterruptConnectionData+32
Followup: MachineOwner
---------
podczas diagnostyki pamięci znika obraz i laptop nie odpowiada więc nie mam wyniku, ale wnioskuje że to chyba pamięć
proszę o pomoc
// wpakowane w code:box, bo przewinięcie do odpowiedzi zajmowało pół godziny - n