Schon wieder ein BSOD.
Obwohl ich VCORE um -10 angehoben hatte. Schon wieder im Idle (diesmal vielleicht nicht 100% idle). Kurz davor ahtte ich ohne Probs 90 Minuten BF3 laufen...
Hier der Error Code. Immer noch zu wenig VCORE?
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112211-15615-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0325a000 PsLoadedModuleList = 0xfffff800`0349f670
Debug session time: Tue Nov 22 01:06:02.792 2011 (UTC + 1:00)
System Uptime: 0 days 2:01:40.010
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc40006eb8, ffffffffc0000185, 1e6289860, fffff88000dd793c}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Unable to load image \SystemRoot\system32\drivers\ataport.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ataport.SYS
*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ataport.SYS ( ataport+1e93c )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40006eb8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000001e6289860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88000dd793c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ataport
FAULTING_MODULE: fffff8000325a000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79293
ERROR_CODE: (NTSTATUS) 0xc0000185 - Das E/A-Ger t hat einen E/A-Fehler gemeldet.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c0000185
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003347b52 to fffff800032d6c40
STACK_TEXT:
fffff880`031c41c8 fffff800`03347b52 : 00000000`0000007a fffff6fc`40006eb8 ffffffff`c0000185 00000001`e6289860 : nt+0x7cc40
fffff880`031c41d0 00000000`0000007a : fffff6fc`40006eb8 ffffffff`c0000185 00000001`e6289860 fffff880`00dd793c : nt+0xedb52
fffff880`031c41d8 fffff6fc`40006eb8 : ffffffff`c0000185 00000001`e6289860 fffff880`00dd793c ffffffff`ffffffff : 0x7a
fffff880`031c41e0 ffffffff`c0000185 : 00000001`e6289860 fffff880`00dd793c ffffffff`ffffffff 00000000`c0000185 : 0xfffff6fc`40006eb8
fffff880`031c41e8 00000001`e6289860 : fffff880`00dd793c ffffffff`ffffffff 00000000`c0000185 fffffa80`00000000 : 0xffffffff`c0000185
fffff880`031c41f0 fffff880`00dd793c : ffffffff`ffffffff 00000000`c0000185 fffffa80`00000000 fffff880`00dd793c : 0x1`e6289860
fffff880`031c41f8 ffffffff`ffffffff : 00000000`c0000185 fffffa80`00000000 fffff880`00dd793c fffff800`032febc5 : ataport+0x1e93c
fffff880`031c4200 00000000`c0000185 : fffffa80`00000000 fffff880`00dd793c fffff800`032febc5 fffffa80`079fcbc0 : 0xffffffff`ffffffff
fffff880`031c4208 fffffa80`00000000 : fffff880`00dd793c fffff800`032febc5 fffffa80`079fcbc0 fffffa80`079fcbc0 : 0xc0000185
fffff880`031c4210 fffff880`00dd793c : fffff800`032febc5 fffffa80`079fcbc0 fffffa80`079fcbc0 fffffa80`06d37b60 : 0xfffffa80`00000000
fffff880`031c4218 fffff800`032febc5 : fffffa80`079fcbc0 fffffa80`079fcbc0 fffffa80`06d37b60 fffffa80`05b279b0 : ataport+0x1e93c
fffff880`031c4220 fffffa80`079fcbc0 : fffffa80`079fcbc0 fffffa80`06d37b60 fffffa80`05b279b0 00000000`00002000 : nt+0xa4bc5
fffff880`031c4228 fffffa80`079fcbc0 : fffffa80`06d37b60 fffffa80`05b279b0 00000000`00002000 fffff6fc`40006eb8 : 0xfffffa80`079fcbc0
fffff880`031c4230 fffffa80`06d37b60 : fffffa80`05b279b0 00000000`00002000 fffff6fc`40006eb8 ffffffff`ffffffff : 0xfffffa80`079fcbc0
fffff880`031c4238 fffffa80`05b279b0 : 00000000`00002000 fffff6fc`40006eb8 ffffffff`ffffffff 00000000`00000000 : 0xfffffa80`06d37b60
fffff880`031c4240 00000000`00002000 : fffff6fc`40006eb8 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : 0xfffffa80`05b279b0
fffff880`031c4248 fffff6fc`40006eb8 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 fffffa80`07f3eca0 : 0x2000
fffff880`031c4250 ffffffff`ffffffff : 00000000`00000000 00000000`00000000 fffffa80`07f3eca0 fffff800`0350c500 : 0xfffff6fc`40006eb8
fffff880`031c4258 00000000`00000000 : 00000000`00000000 fffffa80`07f3eca0 fffff800`0350c500 fffffa80`05b279b0 : 0xffffffff`ffffffff
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport+1e93c
fffff880`00dd793c fc cld
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: ataport+1e93c
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ataport.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------