GizmoBoy
Lieutenant
- Dabei seit
- Okt. 2006
- Beiträge
- 927
Moin Leute,
das mal wieder aufm Freitag kurz vorm Feierabend... Dank google bin ich auf nichts gestoßen. Hoffe mal ihr könnt mir helfen...
Bin für alle antworten dankbar...
Board: Gigabyte P35 DS3
CPU: Q6600
RAM: Kingston Value RAM 4 GB (ist i.O.)
das mal wieder aufm Freitag kurz vorm Feierabend... Dank google bin ich auf nichts gestoßen. Hoffe mal ihr könnt mir helfen...
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\tj\Desktop\Mini040111-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\Windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Apr 1 13:10:25.539 2011 (GMT+2)
System Uptime: 0 days 3:59:26.268
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {1ff, 1c, 1, 80545c82}
Probably caused by : ntkrpamp.exe ( nt!ScPatchFxb+0 )
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: 000001ff, 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: 80545c82, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 000001ff
CURRENT_IRQL: 1c
FAULTING_IP:
nt!ScPatchFxb+0
80545c82 0fae01 fxsave [ecx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from 80545a1b to 80545c82
STACK_TEXT:
b547bca4 80545a1b b547bcec 88e78428 ffdff120 nt!ScPatchFxb
b547bcb8 80503850 88e78498 88e78428 804fb078 nt!KiSwapContext+0x2f
b547bcc4 804fb078 88e78594 88e78428 88e7845c nt!KiSwapThread+0x8a
b547bcec 80502f8c 00000000 00000005 00000000 nt!KeWaitForSingleObject+0x1c2
b547bd04 804ff8c4 00000000 00000000 00000000 nt!KiSuspendThread+0x18
b547bd4c 806e7ef2 00000001 00000000 b547bd64 nt!KiDeliverApc+0x124
b547bd4c 79e8e48c 00000001 00000000 b547bd64 hal!HalpApcInterrupt+0xc6
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x79e8e48c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ScPatchFxb+0
80545c82 0fae01 fxsave [ecx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ScPatchFxb+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d00d46f
FAILURE_BUCKET_ID: 0xA_nt!ScPatchFxb+0
BUCKET_ID: 0xA_nt!ScPatchFxb+0
Followup: MachineOwner
---------
Bin für alle antworten dankbar...
Board: Gigabyte P35 DS3
CPU: Q6600
RAM: Kingston Value RAM 4 GB (ist i.O.)