Antwort schreiben 
 
Themabewertung:
  • 0 Bewertungen - 0 im Durchschnitt
  • 1
  • 2
  • 3
  • 4
  • 5
Baumstrukturmodus | Linearer Modus
Windows 7 Bluescreen - fxobjecthandlegetptrqi
12-02-2012, 11:30
Beitrag: #1
Windows 7 Bluescreen - fxobjecthandlegetptrqi
Hallo liebes Forum!

Bin zur Zeit etwas ratlos.

Habe Freitag neue Platte bekommen und sogleich die anderen ausgebaut und die neue rein, windows drauf, lief auch problemlos. Sonntag gings dann los mit Bluesscreens. u.a APC_INDEX_MISMATCH oder so. Denke mal liegt am RAM, oder? D:

System:
OS: Wind´7 HomePremium 64 bit
CPU: AMD Phenom x4 955 BE
Board: Gagabyte 880GA-UD3H
RAM: ValueRAM Kit 4x 2 GB

-------------------------------------
Minidump auswertung:




Microsoft ® Windows Debugger Version 6.4.0007.2
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\021312-31059-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 Longhorn Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Kernel base = 0xfffff800`0321b000 PsLoadedModuleList = 0xfffff800`03460670
Debug session time: Mon Feb 13 16:43:08.862 2012 (GMT+1)
System Uptime: 0 days 0:02:18.017
Loading Kernel Symbols
.................................................. .................................................. .................................................. .....
Loading unloaded module list
....
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {7725154a, 0, ffff0000, fffff88007bb9ca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

APC_INDEX_MISMATCH (1)
This is a kernel internal error which can occur only on a checked build.
The most common reason to see such a bugcheck would occur when a
filesystem had a mismatched number of KeEnterCriticalRegion calls compared
to KeLeaveCriticalRegion calls. This check is made on exit from a system
call.
Arguments:
Arg1: 000000007725154a, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex KernelApcDicable
Arg4: fffff88007bb9ca0, Previous KernelApcDisable

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x1

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800032971e9 to fffff80003297c40

STACK_TEXT:
fffff880`07bb9a68 fffff800`032971e9 : 00000000`00000001 00000000`7725154a 00000000`00000000 00000000`ffff0000 : nt!KeBugCheckEx
fffff880`07bb9a70 fffff800`03297120 : ffffffff`ffffffff fffffa80`06f0ab60 fffffa80`0000007c 00000000`000ae028 : nt!KiBugCheckDispatch+0x69
fffff880`07bb9bb0 00000000`7725154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`000ae008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7725154a


FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`03297120 4883ec50 sub rsp,0x50

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiSystemServiceExit+245

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

STACK_COMMAND: kb

FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245

BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245

Followup: MachineOwner
---------




Festplatte mit HD Tune gecheckt, keine probleme, rennt wie sau. Also eher RAM..?
Vielen Dank schon mal vorab. Besten Dank und viele Grüße
Alle Beiträge dieses Benutzers finden
Diese Nachricht in einer Antwort zitieren
12-02-2012, 13:25
Beitrag: #2
Re: Windows 7 Bluescreen - page_fault_in_nonpaged_area athurx.sys
RAM einzeln mithttp://www.computerbase.de/downloads/software/systemueberwachung/memtest86/ überprüfen
Alle Beiträge dieses Benutzers finden
Diese Nachricht in einer Antwort zitieren
12-02-2012, 13:29
Beitrag: #3
Re: Windows 7 Bluescreen - page_fault_in_nonpaged_area athurx.sys
Memtest86+ hat nix gefunden soweit, alle riegeln einzelnd getestet. hab windows neu drauf gemacht, kriege jetzt aber ab und zu BS, hier mal paar Bugchecks:

************************************************** *****************************
* *
* 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: fffff95ff80f4a50, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff95ff80f4a50, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

OVERLAPPED_MODULE: athurx

WRITE_ADDRESS: unable to get MiSystemVaType - probably bad symbols
fffff95ff80f4a50

FAULTING_IP:
+fffff95ff80f4a50
fffff95f`f80f4a50 ?? ???

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800031567a1 to fffff800030d75c0

STACK_TEXT:
fffff880`079093e8 fffff800`031567a1 : 00000000`00000050 fffff95f`f80f4a50 00000000`00000008 fffff880`07909550 : nt!KeBugCheckEx
fffff880`079093f0 fffff800`030d56ae : 00000000`00000008 00000000`013603d9 ffffffff`98010e00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x40d4b
fffff880`07909550 fffff95f`f80f4a50 : fffff960`000f72b8 00000000`02a9e900 fffffa80`07e19b60 fffff880`079098a0 : nt!KiPageFault+0x16e
fffff880`079096e8 fffff960`000f72b8 : 00000000`02a9e900 fffffa80`07e19b60 fffff880`079098a0 fffff960`00135f8a : 0xfffff95f`f80f4a50
fffff880`079096f0 fffff960`000fcded : 00000000`013603d9 fffff880`079098a0 00000000`00000000 fffff960`0026fb90 : win32k!HMValidateHandle+0xd8
fffff880`07909720 fffff800`030d6813 : fffffa80`07e19b60 00000000`00000000 00000000`00000020 00000000`3f010eb7 : win32k!NtUserSetCursorIconData+0x4d
fffff880`07909820 00000000`76f3152a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02a9e8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f3152a


FOLLOWUP_IP:
win32k!HMValidateHandle+d8
fffff960`000f72b8 85c0 test eax,eax

SYMBOL_STACK_INDEX: 4

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!HMValidateHandle+d8

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f10fe35

STACK_COMMAND: kb

FAILURE_BUCKET_ID: X64_0x50_W_win32k!HMValidateHandle+d8

BUCKET_ID: X64_0x50_W_win32k!HMValidateHandle+d8

Followup: MachineOwner
---------


************************************************** *****************************
* *
* 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: 000000000865e6a0, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000da86da, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: unable to get MiSystemVaType - probably bad symbols
000000000865e6a0

CURRENT_IRQL: 6

FAULTING_IP:
Wdf01000!FxObjectHandleGetPtrQI+2a
fffff880`00da86da 488b01 mov rax,[rcx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff800030c0b29 to fffff800030c15c0

STACK_TEXT:
fffff880`0906da68 fffff800`030c0b29 : 00000000`0000000a 00000000`0865e6a0 00000000`00000006 00000000`00000000 : nt!KeBugCheckEx
fffff880`0906da70 fffff800`030bf7a0 : fffff980`0906df01 00000000`0000fb00 fffff980`16db4c10 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0906dbb0 fffff880`00da86da : 00000000`00000008 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0906dd48 fffff880`00d8f1c3 : 00000000`0000fb00 fffffa80`0865d1a0 fffff880`0376f000 fffffa80`0865d1a0 : Wdf01000!FxObjectHandleGetPtrQI+0x2a
fffff880`0906ddb8 00000000`00000001 : fffff880`00e05fd8 00000000`0000fb00 00000000`00000001 fffffa80`07bf4760 : Wdf01000!imp_WdfIoQueueGetDevice+0x7f
fffff880`0906ddf8 fffff880`00e05fd8 : 00000000`0000fb00 00000000`00000001 fffffa80`07bf4760 fffff800`030dd156 : 0x1
fffff880`0906de00 fffff880`00fde6cc : fffff800`0324e440 fffff800`030f9dc2 00000000`000010f0 00000000`00000000 : ataport!AtaPortGetPhysicalAddress+0x2c
fffff880`0906de70 fffff880`00fde137 : fffffa80`07bf4a78 00000000`00000001 fffffa80`07bf4ac0 fffffa80`0865e6a8 : atapi!AtapiSetupPrdTable+0xec
fffff880`0906dec0 fffff880`00fddee1 : fffff6fc`40009750 fffffa80`07bf4a78 00000000`00000001 fffffa80`0866ecc0 : atapi!AtapiSendAtaCommand+0x11b
fffff880`0906df30 fffff880`00fdd656 : fffffa80`07bf4a78 fffff880`012e0011 fffff800`033c4e01 fffff800`0324e440 : atapi!AtapiHandleAtaCommand+0x45
fffff880`0906df60 fffff880`00e0bf37 : 00000000`0000003c 00000000`00000001 fffffa80`0866ecc0 fffff781`c0000000 : atapi!AtapiHwStartIo+0x66
fffff880`0906df90 fffff800`030bce0b : 00000000`0000003c fffff880`00e01c74 fffffa80`0866ecc0 fffff880`012e2786 : ataport!IdeStartCrbSynchronized+0x7b
fffff880`0906e000 fffff880`00e0be7d : fffffa80`07bf4778 fffff880`00e0bebc fffffa80`07bf4690 fffffa80`0865d1a0 : nt!KeSynchronizeExecution+0x3b
fffff880`0906e040 fffff800`0300c9ce : fffffa80`07bf4778 00000000`00000018 00000000`00000000 00000000`00000001 : ataport!IdeStartIoCallBack+0x2d5
fffff880`0906e1b0 fffff800`0300d13d : fffffa80`08585ac0 fffffa80`0854e860 fffff880`0906e201 00000000`00000000 : hal!HalpAllocateAdapterCallback+0x146
fffff880`0906e250 fffff800`0300c71f : fffffa80`07bf4730 00000000`00001000 fffffa80`0854e860 fffffa80`07a3fb60 : hal!HalAllocateAdapterChannel+0x101
fffff880`0906e290 fffff880`00fb30d3 : fffffa80`07bf4690 fffff880`00fb312c 00000000`000000a0 fffff880`0906e380 : hal!HalBuildScatterGatherList+0x2f3
fffff880`0906e300 fffff880`00e0bb3b : fffffa80`07bf4690 fffffa80`07bf4690 fffffa80`0865d1a0 fffffa80`07bf4690 : PCIIDEX!BmSetup+0x6b
fffff880`0906e360 fffff880`00e0a7eb : fffffa80`0865e500 fffffa80`07bf4690 fffffa80`0865e500 fffffa80`0865d1a0 : ataport!IdeDispatchChannelRequest+0xef
fffff880`0906e390 fffff880`00e0a650 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : ataport!IdeStartChannelRequest+0x113
fffff880`0906e410 fffff880`00e0b9e2 : fffffa80`0865d1a0 00000000`00000000 00000000`00000103 fffff880`00e86787 : ataport!IdeStartDeviceRequest+0x2c4
fffff880`0906e4d0 fffff880`00e074ee : fffff980`16084e50 fffffa80`07bf4690 00000000`00000002 fffffa80`08672060 : ataport!IdePortPdoDispatch+0xb6
fffff880`0906e500 fffff800`03567c16 : fffff980`16084e50 00000000`00000002 fffffa80`074bdd50 fffff880`00e8c016 : ataport!IdePortDispatch+0x16
fffff880`0906e530 fffff880`00e86787 : fffff980`16084e50 fffffa80`085a59b0 fffff980`16084e50 fffffa80`07a4aad0 : nt!IovCallDriver+0x566
fffff880`0906e590 fffff880`00e8e751 : fffff880`00eacb50 00000000`00000000 00000000`00001000 fffff980`16084fb0 : ACPI!ACPIDispatchForwardIrp+0x37
fffff880`0906e5c0 fffff880`00e86a1f : fffff880`00eacb50 fffffa80`074bdd50 fffff980`16084e50 fffff980`16084e50 : ACPI!ACPIIrpDispatchDeviceControl+0x75
fffff880`0906e5f0 fffff800`03567c16 : fffff980`16084e50 00000000`00000002 fffff980`16084e50 00000000`00000002 : ACPI!ACPIDispatchIrp+0x12b
fffff880`0906e670 fffff880`018f1445 : 00000000`00000000 00000000`00000001 fffffa80`09a37d90 fffffa80`0ada0f40 : nt!IovCallDriver+0x566
fffff880`0906e6d0 fffff880`018f1695 : fffffa80`08747010 fffffa80`085a59b0 fffff880`00020000 fffff800`00000001 : CLASSPNP!ServiceTransferRequest+0x355
fffff880`0906e770 fffff800`03567c16 : fffff980`14900c10 00000000`00000002 fffffa80`08678060 00000000`00000002 : CLASSPNP!ClassReadWrite+0xd5
fffff880`0906e7c0 fffff880`00f260af : fffff980`14900c10 00000000`00000002 fffff980`14900e48 fffffa80`0a8d2ba0 : nt!IovCallDriver+0x566
fffff880`0906e820 fffff800`03567c16 : fffff980`14900c10 fffffa80`086789f0 fffff980`14900ed8 00000000`00000001 : partmgr!PmGlobalDispatch+0x9f
fffff880`0906e850 fffff880`00f3b12c : fffffa80`085c3a90 00000000`00000002 fffff980`14900c10 fffffa80`080e2170 : nt!IovCallDriver+0x566
fffff880`0906e8b0 fffff800`03567c16 : 00000000`00000002 fffffa80`0950bb40 fffff980`14900c10 fffff800`03563bcc : volmgr!VmReadWrite+0x11c
fffff880`0906e8f0 fffff880`00e362ca : fffff980`14900c10 00000000`00000002 fffffa80`085d7a40 fffffa80`0950bb40 : nt!IovCallDriver+0x566
fffff880`0906e950 fffff880`00e3654c : fffffa80`085d7b90 00000000`00000001 fffffa80`085d7a40 00000000`00000002 : fvevol!FveReadWrite+0x52
fffff880`0906e990 fffff880`00e365a3 : fffff980`14900f20 fffff980`14900c10 fffff980`14900f20 fffffa80`081a82f0 : fvevol!FveFilterRundownReadWrite+0x1dc
fffff880`0906e9f0 fffff800`03567c16 : fffff980`14900c10 00000000`00000002 00000000`00000000 00000000`00000000 : fvevol!FveFilterRundownWrite+0x2f
fffff880`0906ea20 00000000`00000000 : fffff980`14900c10 00000000`00000002 00000000`00000000 00000000`00000000 : nt!IovCallDriver+0x566


FOLLOWUP_IP:
Wdf01000!FxObjectHandleGetPtrQI+2a
fffff880`00da86da 488b01 mov rax,[rcx]

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Wdf01000!FxObjectHandleGetPtrQI+2a

MODULE_NAME: Wdf01000

IMAGE_NAME: Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc19f

STACK_COMMAND: kb

FAILURE_BUCKET_ID: X64_0xD1_VRF_Wdf01000!FxObjectHandleGetPtrQI+2a

BUCKET_ID: X64_0xD1_VRF_Wdf01000!FxObjectHandleGetPtrQI+2a

Followup: MachineOwner
--------- Bis dann!
Alle Beiträge dieses Benutzers finden
Diese Nachricht in einer Antwort zitieren
12-02-2012, 15:18
Beitrag: #4
Re: Windows 7 Bluescreen - page_fault_in_nonpaged_area athurx.sys
Hallo

Hier kannst die Bedeutung der Fehlermeldungen nachlesen
http://www.jasik.de/shutdown/stop_fehler.htm
Tschüß.
Vinzenz99055711
Alle Beiträge dieses Benutzers finden
Diese Nachricht in einer Antwort zitieren
12-02-2012, 15:23
Beitrag: #5
Re: Windows 7 Bluescreen - page_fault_in_nonpaged_area athurx.sys
Nun belästigt er mich teils mit ntfs.sys blueescreens. ich mach einfach nochmal n chkdsk und prüf dann nochmal alle riegel per memtest..

Beste Grüße,
Suey
Alle Beiträge dieses Benutzers finden
Diese Nachricht in einer Antwort zitieren
12-02-2012, 17:17
Beitrag: #6
Re: Windows 7 Bluescreen - page_fault_in_nonpaged_area athurx.sys
Tschau
Bei NTFS.SYS ist eigentlich die Dateistruktur oder wichtige Systemdateien hinüber.


Wenn auch ein chkdsk c: /f /r nichts mehr bewirkt, wirst um eine Neuinstallation nicht herumkommen.
Alle Beiträge dieses Benutzers finden
Diese Nachricht in einer Antwort zitieren
Tags
fxobjecthandlegetptrqi, page_fault_in_nonpaged_area athurx.sys, &esrc=s&sa=u&ei=jte_u8k0i8ny8qxz9ihwaw&ved=0ccyqfjad&usg=afqjcnelncfpmhb2rghv5t9fwrxeo8ohtw, cyberlink power dvd kann nicht auf das speichergerät zugreifen, miniaturansicht mp3 windows7, altgr geht nicht windows 7, compaq laptop auf werkseinstellung zurücksetzen, medion akoya p4020d touchscreen problem, internet dame deinstallieren, windows 7 sicherung fehler e/a, device media is write-protected hp usb disk storage, sites
« Ein Thema zurück | Ein Thema vor »
Antwort schreiben 


  • Druckversion anzeigen
  • Thema einem Freund senden
  • Thema abonnieren
Gehe zu:




Kontakt | Windows Forum | Nach oben | Zum Inhalt | Archiv-Modus | RSS-Synchronisation| Impressum