Hallo, ich bekomm seit einigen Tagen unregelmäßig ein bluescreen meißt kurz nach dem Hochfahren des Rechners.
Kenn mich lkeider nicht so genau aus mit dem debuggen und hab das Ergebnis angehängt. Wär euch echt dankbar für Tips worans liegen könnte. Danke schonmal
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010614-8751-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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`032626d0
Debug session time: Mon Jan 6 16:44:49.778 2014 (UTC + 1:00)
System Uptime: 0 days 0:02:15.606
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {370, 5, 0, fffff880014d37ca}
*** WARNING: Unable to verify timestamp for asahci64.sys
*** ERROR: Module load completed but symbols could not be loaded for asahci64.sys
Probably caused by : asahci64.sys ( asahci64+845a )
Followup: MachineOwner
---------
3: 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: 0000000000000370, memory referenced
Arg2: 0000000000000005, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880014d37ca, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cc100
GetUlongFromAddress: unable to read from fffff800032cc1c0
0000000000000370 Nonpaged pool
CURRENT_IRQL: 5
FAULTING_IP:
SCSIPORT!ScsiPortNotification+2d2
fffff880`014d37ca 488b8370030000 mov rax,qword ptr [rbx+370h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: IAStorDataMgrS
TRAP_FRAME: fffff8800a0cb0f0 -- (.trap 0xfffff8800a0cb0f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000102 rbx=0000000000000000 rcx=fffff8800a0cb330
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880014d37ca rsp=fffff8800a0cb280 rbp=fffffa80069a8cf0
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
SCSIPORT!ScsiPortNotification+0x2d2:
fffff880`014d37ca 488b8370030000 mov rax,qword ptr [rbx+370h] ds:00000000`00000370=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003094169 to fffff80003094bc0
STACK_TEXT:
fffff880`0a0cafa8 fffff800`03094169 : 00000000`0000000a 00000000`00000370 00000000`00000005 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a0cafb0 fffff800`03092de0 : fffffa80`06d37f68 fffff880`0197e2ec 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0a0cb0f0 fffff880`014d37ca : 00000000`00000000 fffff880`04e1a884 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a0cb280 fffff880`00ff145a : 00000002`00000001 00000000`00000000 fffff880`0a0cb7f0 00000000`00000000 : SCSIPORT!ScsiPortNotification+0x2d2
fffff880`0a0cb320 00000002`00000001 : 00000000`00000000 fffff880`0a0cb7f0 00000000`00000000 00000000`00000012 : asahci64+0x845a
fffff880`0a0cb328 00000000`00000000 : fffff880`0a0cb7f0 00000000`00000000 00000000`00000012 fffff880`03f7c800 : 0x00000002`00000001
STACK_COMMAND: kb
FOLLOWUP_IP:
asahci64+845a
fffff880`00ff145a ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: asahci64+845a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: asahci64
IMAGE_NAME: asahci64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5252626b
FAILURE_BUCKET_ID: X64_0xD1_asahci64+845a
BUCKET_ID: X64_0xD1_asahci64+845a
Followup: MachineOwner
---------
