Hvordan DU kan feilsøke Windows! (Guider)

Raste · 22. mai 2008

Hei.

Fikk ny pc idag etter min forrige måtte byttes da ikke verkstedet ikke greide å reparere det.

Men fikk bluescreen problem idag, og syns det er temmelig irriterende. Det skal jo ikke komme på en ny maskin.

Jeg mistenker kanskje at det er noe med nettverksgreier eller noe sånt, leste i stickyen, men skjønte litt lite hva som sto der.

Den feilkoden jeg får er denne: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)! Noen som har en anelse på hvordan jeg kan få fikset dette problemet?

Kan jo ta med problemdetaljene som jeg fikk nå:

Problemsignatur:

Navn på problemhendelse: BlueScreen

Tilleggsinformasjon om problemet:

BCCode: d1

BCP1: FFFFD24C

BCP2: 00000009

BCP3: 00000008

BCP4: FFFFD24C

OS Version: 6_0_6000

Service Pack: 0_0

Product: 768_1

Filer som bidrar til å beskrive problemet:

C:\Windows\Minidump\Mini052008-10.dmp

C:\Users\Joachim\AppData\Local\Temp\WER-137764-0.sysdata.xml

C:\Users\Joachim\AppData\Local\Temp\WER59E2.tmp.version.txt

Raste · 25. mai 2008

Ingen som vet hvordan jeg kan fikse problemet?

fenderebest · 26. mai 2008

Det er nok umulig å si noe om problemet før man vet litt mere konkret hva det er.

Som du ser referer Windows til en minidump fil:

C:\Windows\Minidump\Mini052008-10.dmp

Denne kan da åpnes i Windbg og feilsøkes for å få mere informasjon om hva som egentlig er problemet.

Raste · 27. mai 2008

Skal søke den opp i Windbg nå, men når jeg skal velge krasj-dump-filen så står det at jeg ikke har tillatelse til å gjøre det. Hvordan kan jeg fikse det?

Jeg har meg selv som admin på Vista.

rAPEd · 10. juni 2008

Skal søke den opp i Windbg nå, men når jeg skal velge krasj-dump-filen så står det at jeg ikke har tillatelse til å gjøre det. Hvordan kan jeg fikse det?
Jeg har meg selv som admin på Vista.

Legg en snarvei av Windbg på skrivebordet, høyre klikk snarveien og velg " Kjør som administrator"

Mitt problem:

Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Complete Dump File: Full address space is available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

Unable to read PsLoadedModuleList

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

KdDebuggerData.KernBase < SystemRangeStart

Windows Server 2008 Kernel Version 6001 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff800`01c11db0

Debug session time: Sun Jun 10 17:14:54.447 2001 (GMT+2)

System Uptime: 0 days 0:52:08.725

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

Unable to read PsLoadedModuleList

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

KdDebuggerData.KernBase < SystemRangeStart

Loading Kernel Symbols

Unable to read PsLoadedModuleList

GetContextState failed, 0xD0000147

CS descriptor lookup failed

GetContextState failed, 0xD0000147

Unable to get program counter

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffffa60017d2180, 3}

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

ReadControl failed - kernel symbols must be loaded first

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

ReadControl failed - kernel symbols must be loaded first

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

---------

GetContextState failed, 0xD0000147

?: kd> !analyze -v

GetContextState failed, 0xD0000147

Unable to get program counter

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an

MP system within the allocated interval. This indicates that the specified

processor is hung and not processing interrupts.

Arguments:

Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: fffffa60017d2180, The PRCB address of the hung processor.

Arg4: 0000000000000003, 0.

Debugging Details:

------------------

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

ReadControl failed - kernel symbols must be loaded first

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

ReadControl failed - kernel symbols must be loaded first

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x101

STACK_TEXT:

GetContextState failed, 0xD0000147

Unable to get current machine context, NTSTATUS 0xC0000147

STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

Followup: MachineOwner

---------

GetContextState failed, 0xD0000147

?: kd> !analyse -v

No export analyse found

GetContextState failed, 0xD0000147

Jeg tror jeg sliter med å få lasta inn symbolene..

Skal kjøre dumpen igjen neste "BSoD" (blir ikke lenge til) kommer pga:

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

Men tips om symbolene hadde vert topp

Brian · 19. juli 2008

Fikk en ganske uventet blåskjerm i dag, og har da minnedumpen her. Jeg får fortsatt ikke til programmet slik at jeg kan åpne fila selv, så jeg legger den ut her. Det skjedde mens jeg holdt på å rippe en cd, og jeg har ikke vært plaget av blåskjermer i den siste tiden.

Mini071908_01.zip

anonymouse · 12. august 2008

Alle som opplever å ha ustabil PC med Asus hovedkort, eventuelt bygd av komplett som nå bare selger noen av sine gamer maskiner osv. med Asus kort, burde avinstallere AI Suite - som liksom skal spare prossessorkraft og strøm. Alt den gjør er å gjøre maskinen ustabil.

Etter å ha avinstallert AI Suite og NVIDIA network manager eller noe slikt dill (som inneholdt bla. "nvfilterapp.dll" eller noe slikt, så er maskinen min plutselig dønn stabil igjen.

odderling · 15. august 2008

Heisann, jeg har begynt å få MANGE BSOD'er i det siste på en av maskinene mine, og det er litt ironisk siden det er denne som bare skal stå i et hjørne å dele filer ut på nettverket.

Men det er ikke så lett for den å gjøre når den ender opp i en boot-loop som ikke stopper før jeg starter windows i sikkermodus.

Dumpfil:

Klikk for å se/fjerne innholdet nedenfor

Microsoft ® Windows Debugger Version 6.9.0003.113 X86

Loading Dump File [C:\WINDOWS\Minidump\Mini081508-02.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp.080413-2111

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Fri Aug 15 15:51:55.625 2008 (GMT+2)

System Uptime: 0 days 0:00:45.203

Loading Kernel Symbols

..........................................................................................

....................................

Loading User Symbols

Loading unloaded module list

.............

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 1b4b001, 646, c0883000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )

Followup: MachineOwner

---------

1: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 00041284, A PTE or the working set list is corrupt.

Arg2: 01b4b001

Arg3: 00000646

Arg4: c0883000

Debugging Details:

------------------

OVERLAPPED_MODULE: Address regions for 'atksgt' and 'Parport.SYS' overlap

BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: avgwdsvc.exe

LAST_CONTROL_TRANSFER: from 80523309 to 804f9f33

STACK_TEXT:

aaaa7c7c 80523309 0000001a 00041284 01b4b001 nt!KeBugCheckEx+0x1b

aaaa7cb4 805241b1 00000646 c0600068 c000da58 nt!MiLocateWsle+0xc1

aaaa7cf8 805204ab 01b4b000 001f6a00 00f2f430 nt!MiCopyOnWrite+0x6f

aaaa7d4c 80544578 00000001 01b4b000 00000001 nt!MmAccessFault+0xae9

aaaa7d4c 01e6d2f7 00000001 01b4b000 00000001 nt!KiTrap0E+0xd0

WARNING: Frame IP not in any known module. Following frames may be wrong.

00f2f430 00000000 00000000 00000000 00000000 0x1e6d2f7

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!MiLocateWsle+c1

80523309 2b45f0 sub eax,dword ptr [ebp-10h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiLocateWsle+c1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1

BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c1

Followup: MachineOwner

---------

Raste · 31. august 2008

Denne som er feilen trolig: avgwdsvc.exe.

Otter_3 · 17. september 2008

Takk for godt forklart hjelp.

Hjalp meg å finne en innkompatibel nettverksdriver.

Hadde lastet ned feil versjon fra Atheros.

*******************************************************************************

* *

* 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: ffffe2df2a3fffea, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, 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: fffff8000103667d, address which referenced memory

Debugging Details:

------------------

READ_ADDRESS: ffffe2df2a3fffea

CURRENT_IRQL: 2

FAULTING_IP:

nt!MiRemovePageByColor+4c

fffff800`0103667d 408a7b1a mov dil,byte ptr [rbx+1Ah]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffffadf29e63590 -- (.trap 0xfffffadf29e63590)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=fffffadf2a5f5a20 rcx=ffffff7fffffffff

rdx=0000000000000012 rsi=fffff80001000000 rdi=fffff80001109db7

rip=fffff8000103667d rsp=fffffadf29e63720 rbp=fffffadf29e63780

r8=0000000000000000 r9=0000000000000000 r10=fffffadf30d00000

r11=fffffadf30d00600 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe cy

nt!MiRemovePageByColor+0x4c:

fffff800`0103667d 408a7b1a mov dil,byte ptr [rbx+1Ah] ds:fffffadf`2a5f5a3a=00

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000102e5b4 to fffff8000102e890

STACK_TEXT:

fffffadf`29e63408 fffff800`0102e5b4 : 00000000`0000000a ffffe2df`2a3fffea 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffffadf`29e63410 fffff800`0102d547 : fffffadf`29e63590 fffffadf`32e40cf0 fffffadf`29e63500 fffffadf`29e635d0 : nt!KiBugCheckDispatch+0x74

fffffadf`29e63590 fffff800`0103667d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x207

fffffadf`29e63720 fffff800`01022537 : 00000001`17c80000 fffffa80`18328480 00000000`dba90000 00000000`00000000 : nt!MiRemovePageByColor+0x4c

fffffadf`29e637d0 fffff800`010195f6 : 00000000`00000001 00000000`00000000 fffff981`94f50000 fa801832`84800400 : nt!MiResolveMappedFileFault+0x5f2

fffffadf`29e63860 fffff800`0104a534 : 00000000`00000000 00000000`000005af fffff6fc`c0ca7a80 00000000`00000000 : nt!MiResolveProtoPteFault+0x2fd

fffffadf`29e638f0 fffff800`01043d34 : fffffadf`00000000 fffff981`94f50000 fffff6fc`c0ca7a80 fffffa80`18328480 : nt!MiDispatchFault+0x1062

fffffadf`29e63a30 fffff800`010446b7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0xbb3

fffffadf`29e63b00 fffff800`010090c3 : fffff981`94f50000 fffff800`01032a00 00000000`dba90000 fffff800`01032a20 : nt!MmCheckCachedPageState+0x76a

fffffadf`29e63b80 fffff800`01008b37 : fffffadf`3838b700 fffffadf`38be91c0 00000000`0000000c 00000000`00000000 : nt!CcPerformReadAhead+0x299

fffffadf`29e63c60 fffff800`010375ca : fffffadf`38be91c0 fffffadf`38be91c0 fffffadf`38c05040 fffff800`011cd9c0 : nt!CcWorkerThread+0xa3e

fffffadf`29e63d00 fffff800`0124a972 : fffffadf`38c05040 00000000`00000080 fffffadf`38c05040 fffffadf`29a93680 : nt!ExpWorkerThread+0x13b

fffffadf`29e63d70 fffff800`01020226 : fffffadf`29a8b180 fffffadf`38c05040 fffffadf`29a93680 fffff800`011b4dc0 : nt!PspSystemThreadStartup+0x3e

fffffadf`29e63dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!MiRemovePageByColor+4c

fffff800`0103667d 408a7b1a mov dil,byte ptr [rbx+1Ah]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiRemovePageByColor+4c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 460280f7

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiRemovePageByColor+4c

BUCKET_ID: X64_0xA_nt!MiRemovePageByColor+4c

Followup: MachineOwner

---------

Gledet meg visst litt for tidlig.

Noen som vet hva dette kan være?

Har forsøkt å rulle tilbake skjermdriver, og planer om å kjøre memtest.

Endret 19. september 2008 av Otter_3

Mozzad · 17. november 2008

Jeg har et Problem med min nye pc. når jeg Sitter og Spiller WoW så får jeg en blueScreen. jeg istallerte derfor Windbg og dette er hva jeg fikk som Text

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 7faacd70, af46c81c, 0}

*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll

PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

Probably caused by : hardware

Followup: MachineOwner

---------

*** Possible invalid call from bfaf7743 ( nv4_disp+0xe3743 )

*** Expected target bfaacd70 ( nv4_disp+0x98d70 )

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)

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: 7faacd70, The address that the exception occurred at

Arg3: af46c81c, Trap Frame

Arg4: 00000000

Debugging Details:

------------------

PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i "0x%08lx" refererte til adresse "0x%08lx". Minnet kunne ikke v re "%s".

FAULTING_IP:

+7faacd70

7faacd70 ?? ???

TRAP_FRAME: af46c81c -- (.trap 0xffffffffaf46c81c)

ErrCode = 00000010

eax=00000000 ebx=00000000 ecx=00000000 edx=00000201 esi=af46cc50 edi=00000001

eip=7faacd70 esp=af46c890 ebp=af46cc50 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

7faacd70 ?? ???

Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Wow.exe

LAST_CONTROL_TRANSFER: from bfaf7748 to 7faacd70

POSSIBLE_INVALID_CONTROL_TRANSFER: from bfaf7743 to bfaacd70

TWO_BIT_ERROR: 1

STACK_TEXT:

WARNING: Frame IP not in any known module. Following frames may be wrong.

af46c88c bfaf7748 bfb12f50 af46cc50 af46cb74 0x7faacd70

af46cc50 e1636ba8 00000000 00000000 00000690 nv4_disp+0xe3748

af46cd50 8054162c 1c400008 12400007 0019fb5c 0xe1636ba8

af46cd50 7c90e4f4 1c400008 12400007 0019fb5c nt!KiFastCallEntry+0xfc

0019fc98 00000000 00000000 00000000 00000000 0x7c90e4f4

STACK_COMMAND: .trap 0xffffffffaf46c81c ; kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: TWO_BIT_CPU_CALL_ERROR

Followup: MachineOwner

---------

*** Possible invalid call from bfaf7743 ( nv4_disp+0xe3743 )

*** Expected target bfaacd70 ( nv4_disp+0x98d70 )

Trenger Hjelp=)

Lilleenga · 31. desember 2008

Microsoft ® Windows Debugger Version 6.10.0003.233 AMD64

Loading Dump File [C:\Windows\Minidump\Mini123008-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612

Machine Name:

Kernel base = 0xfffff800`02060000 PsLoadedModuleList = 0xfffff800`02225db0

Debug session time: Tue Dec 30 22:10:13.045 2008 (GMT+1)

System Uptime: 0 days 3:37:36.439

Loading Kernel Symbols

...............................................................

................................................................

...................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff800053cef89, 8, fffff800053cef89, 2}

Could not read faulting driver name

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+119 )

Followup: MachineOwner

---------

1: kd> !analyze -v

*******************************************************************************

* *

* 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: fffff800053cef89, memory referenced.

Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.

Arg3: fffff800053cef89, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002289080

fffff800053cef89

FAULTING_IP:

+fffff800053cef89

fffff800`053cef89 ?? ???

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffffa60079f7310 -- (.trap 0xfffffa60079f7310)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=fffff8800f3d3980 rcx=0000000000000001

rdx=fffffa800396b88c rsi=0000000000000000 rdi=fffff8800f3d3958

rip=fffff800053cef89 rsp=fffffa60079f74a0 rbp=0000000000000064

r8=0000000000000000 r9=fffffa60079f76d9 r10=fffff8800f3d3930

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

fffff800`053cef89 ?? ???

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800020c3524 to fffff800020b5350

STACK_TEXT:

fffffa60`079f7218 fffff800`020c3524 : 00000000`00000050 fffff800`053cef89 00000000`00000008 fffffa60`079f7310 : nt!KeBugCheckEx

fffffa60`079f7220 fffff800`020b3ed9 : 00000000`00000008 00000000`00000008 00000000`00000000 00000000`00000064 : nt!MmAccessFault+0x534

fffffa60`079f7310 fffff800`053cef89 : 00000074`00000000 00000000`00000000 00000000`00000000 fffff880`0afd2210 : nt!KiPageFault+0x119

fffffa60`079f74a0 00000074`00000000 : 00000000`00000000 00000000`00000000 fffff880`0afd2210 00000000`00000000 : 0xfffff800`053cef89

fffffa60`079f74a8 00000000`00000000 : 00000000`00000000 fffff880`0afd2210 00000000`00000000 fffff880`0f3d3930 : 0x74`00000000

fffffa60`079f74b0 00000000`00000000 : fffff880`0afd2210 00000000`00000000 fffff880`0f3d3930 fffff880`0f3d3958 : 0x0

fffffa60`079f74b8 fffff880`0afd2210 : 00000000`00000000 fffff880`0f3d3930 fffff880`0f3d3958 fffff880`0f3d3974 : 0x0

fffffa60`079f74c0 00000000`00000000 : fffff880`0f3d3930 fffff880`0f3d3958 fffff880`0f3d3974 fffff880`0f3d3980 : 0xfffff880`0afd2210

fffffa60`079f74c8 fffff880`0f3d3930 : fffff880`0f3d3958 fffff880`0f3d3974 fffff880`0f3d3980 00000000`00000000 : 0x0

fffffa60`079f74d0 fffff880`0f3d3958 : fffff880`0f3d3974 fffff880`0f3d3980 00000000`00000000 00000000`00000000 : 0xfffff880`0f3d3930

fffffa60`079f74d8 fffff880`0f3d3974 : fffff880`0f3d3980 00000000`00000000 00000000`00000000 fffff800`00000001 : 0xfffff880`0f3d3958

fffffa60`079f74e0 fffff880`0f3d3980 : 00000000`00000000 00000000`00000000 fffff800`00000001 fffffa60`079f7518 : 0xfffff880`0f3d3974

fffffa60`079f74e8 00000000`00000000 : 00000000`00000000 fffff800`00000001 fffffa60`079f7518 fffff880`0afd2210 : 0xfffff880`0f3d3980

fffffa60`079f74f0 00000000`00000000 : fffff800`00000001 fffffa60`079f7518 fffff880`0afd2210 00000000`00000000 : 0x0

fffffa60`079f74f8 fffff800`00000001 : fffffa60`079f7518 fffff880`0afd2210 00000000`00000000 fffff800`00000064 : 0x0

fffffa60`079f7500 fffffa60`079f7518 : fffff880`0afd2210 00000000`00000000 fffff800`00000064 fffffa60`079f76d9 : 0xfffff800`00000001

fffffa60`079f7508 fffff880`0afd2210 : 00000000`00000000 fffff800`00000064 fffffa60`079f76d9 fffffa60`079f76f0 : 0xfffffa60`079f7518

fffffa60`079f7510 00000000`00000000 : fffff800`00000064 fffffa60`079f76d9 fffffa60`079f76f0 fffffa60`079f76f8 : 0xfffff880`0afd2210

fffffa60`079f7518 fffff800`00000064 : fffffa60`079f76d9 fffffa60`079f76f0 fffffa60`079f76f8 fffff880`0efae060 : 0x0

fffffa60`079f7520 fffffa60`079f76d9 : fffffa60`079f76f0 fffffa60`079f76f8 fffff880`0efae060 00000000`00000000 : 0xfffff800`00000064

fffffa60`079f7528 fffffa60`079f76f0 : fffffa60`079f76f8 fffff880`0efae060 00000000`00000000 00000000`00000000 : 0xfffffa60`079f76d9

fffffa60`079f7530 fffffa60`079f76f8 : fffff880`0efae060 00000000`00000000 00000000`00000000 fffff880`0d3ee554 : 0xfffffa60`079f76f0

fffffa60`079f7538 fffff880`0efae060 : 00000000`00000000 00000000`00000000 fffff880`0d3ee554 fffff800`02347803 : 0xfffffa60`079f76f8

fffffa60`079f7540 00000000`00000000 : 00000000`00000000 fffff880`0d3ee554 fffff800`02347803 00000000`00000000 : 0xfffff880`0efae060

fffffa60`079f7548 00000000`00000000 : fffff880`0d3ee554 fffff800`02347803 00000000`00000000 00000000`00000004 : 0x0

fffffa60`079f7550 fffff880`0d3ee554 : fffff800`02347803 00000000`00000000 00000000`00000004 fffff880`0d3ee500 : 0x0

fffffa60`079f7558 fffff800`02347803 : 00000000`00000000 00000000`00000004 fffff880`0d3ee500 fffff800`02193f00 : 0xfffff880`0d3ee554

fffffa60`079f7560 fffff800`0233d76f : fffff880`0efae060 fffffa80`0396b840 00000000`000000c8 fffffa60`079f7b28 : nt!RtlpInheritAcl+0x183

fffffa60`079f7630 fffff800`0233ef71 : fffffa60`079f7990 00000000`00000000 fffffa80`0600cda0 fffff880`0efae060 : nt!RtlpNewSecurityObject+0xacf

fffffa60`079f78b0 fffff800`022fb85f : 00000000`00000000 00000000`0155f340 fffff880`089a39c0 fffff880`07ff9060 : nt!ObInsertObject+0x291

fffffa60`079f7ac0 fffff800`022fb981 : fffffa80`04263760 fffffa60`00000008 fffffa60`079f7c00 00000000`00000000 : nt!NtOpenThreadTokenEx+0x35f

fffffa60`079f7be0 fffff800`020b4df3 : fffffa80`04263760 00000000`03c07c80 00000000`00000000 fffffa80`08685560 : nt!NtOpenThreadToken+0x11

fffffa60`079f7c20 00000000`77d45cba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`0155f2f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d45cba

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!KiPageFault+119

fffff800`020b3ed9 85c0 test eax,eax

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiPageFault+119

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

FAILURE_BUCKET_ID: X64_0x50_nt!KiPageFault+119

BUCKET_ID: X64_0x50_nt!KiPageFault+119

Followup: MachineOwner

---------

Hva med denne? Jeg ser ikke hva som er feilen...

Hadde vært fint med et svar, har måtte levd med BlueScreen problemer VELDIG lenge...

Armalite66 · 26. januar 2009

Hei, har problemer med en gammel bærbar. Har aldri hatt problemer før, men har brukt linux i lang tid på den. Innstallerte nylig XP på nytt, og opplever en del crash etter det. Her er WinDbg analysen:

Microsoft ® Windows Debugger Version 6.10.0003.233 X86

Loading Dump File [C:\WINDOWS\Minidump\Mini011309-09.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 2600.xpsp_sp3_gdr.080814-1236

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0

Debug session time: Tue Jan 13 02:41:43.038 2009 (GMT+1)

System Uptime: 0 days 0:01:08.598

Loading Kernel Symbols

...............................................................

............................................................

Loading User Symbols

Loading unloaded module list

..........

Unable to load image w70n51.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for w70n51.sys

*** ERROR: Module load completed but symbols could not be loaded for w70n51.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {f895a500, 2, 1, 804d9b68}

Probably caused by : w70n51.sys ( w70n51+2a3be )

Followup: MachineOwner

---------

kd> !analyse -v

No export analyse found

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: f895a500, 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: 804d9b68, address which referenced memory

Debugging Details:

------------------

WRITE_ADDRESS: f895a500

CURRENT_IRQL: 2

FAULTING_IP:

nt!memcpy+130

804d9b68 89448ffc mov dword ptr [edi+ecx*4-4],eax

CUSTOMER_CRASH_COUNT: 9

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: ashServ.exe

LAST_CONTROL_TRANSFER: from f7f3e3be to 804d9b68

STACK_TEXT:

f8958dc4 f7f3e3be f895a500 81de3050 00000006 nt!memcpy+0x130

WARNING: Stack unwind information not available. Following frames may be wrong.

f895929c f7f3e640 81e27000 81de3008 81de300e w70n51+0x2a3be

f8959c00 f7f1f11a 81e27000 81e8ffd8 81e8f28c w70n51+0x2a640

f8959e30 f7f34abe 81e8f000 f8959e44 81fd4208 w70n51+0xb11a

f8959e4c f7f31037 81e8f000 81d64000 00000001 w70n51+0x20abe

f8959f3c f7f3077b 81eeaa60 8229c600 f8959f84 w70n51+0x1d037

f8959f90 f7f31cf6 81e8f000 f8959fab 00000000 w70n51+0x1c77b

f8959fac f7f31e4b 81e8f000 f8959fd0 f8396e99 w70n51+0x1dcf6

f8959fb8 f8396e99 81e8f000 81f47d98 81f47ffc w70n51+0x1de4b

f8959fd0 804dbbd4 81e8f2a0 81e8f28c 00000000 NDIS!ndisMDpcX+0x21

f8959ff4 804db89e ef579d54 00000000 00000000 nt!KiRetireDpcList+0x46

f8959ff8 ef579d54 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a

804db89e 00000000 00000009 bb835675 00000128 0xef579d54

STACK_COMMAND: kb

FOLLOWUP_IP:

w70n51+2a3be

f7f3e3be ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: w70n51+2a3be

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: w70n51

IMAGE_NAME: w70n51.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3ee71b51

FAILURE_BUCKET_ID: 0xA_w70n51+2a3be

BUCKET_ID: 0xA_w70n51+2a3be

Followup: MachineOwner

---------

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: f895a500, 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: 804d9b68, address which referenced memory

Debugging Details:

------------------

WRITE_ADDRESS: f895a500

CURRENT_IRQL: 2

FAULTING_IP:

nt!memcpy+130

804d9b68 89448ffc mov dword ptr [edi+ecx*4-4],eax

CUSTOMER_CRASH_COUNT: 9

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: ashServ.exe

LAST_CONTROL_TRANSFER: from f7f3e3be to 804d9b68

STACK_TEXT:

f8958dc4 f7f3e3be f895a500 81de3050 00000006 nt!memcpy+0x130

WARNING: Stack unwind information not available. Following frames may be wrong.

f895929c f7f3e640 81e27000 81de3008 81de300e w70n51+0x2a3be

f8959c00 f7f1f11a 81e27000 81e8ffd8 81e8f28c w70n51+0x2a640

f8959e30 f7f34abe 81e8f000 f8959e44 81fd4208 w70n51+0xb11a

f8959e4c f7f31037 81e8f000 81d64000 00000001 w70n51+0x20abe

f8959f3c f7f3077b 81eeaa60 8229c600 f8959f84 w70n51+0x1d037

f8959f90 f7f31cf6 81e8f000 f8959fab 00000000 w70n51+0x1c77b

f8959fac f7f31e4b 81e8f000 f8959fd0 f8396e99 w70n51+0x1dcf6

f8959fb8 f8396e99 81e8f000 81f47d98 81f47ffc w70n51+0x1de4b

f8959fd0 804dbbd4 81e8f2a0 81e8f28c 00000000 NDIS!ndisMDpcX+0x21

f8959ff4 804db89e ef579d54 00000000 00000000 nt!KiRetireDpcList+0x46

f8959ff8 ef579d54 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a

804db89e 00000000 00000009 bb835675 00000128 0xef579d54

STACK_COMMAND: kb

FOLLOWUP_IP:

w70n51+2a3be

f7f3e3be ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: w70n51+2a3be

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: w70n51

IMAGE_NAME: w70n51.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3ee71b51

FAILURE_BUCKET_ID: 0xA_w70n51+2a3be

BUCKET_ID: 0xA_w70n51+2a3be

Followup: MachineOwner

---------

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: f895a500, 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: 804d9b68, address which referenced memory

Debugging Details:

------------------

WRITE_ADDRESS: f895a500

CURRENT_IRQL: 2

FAULTING_IP:

nt!memcpy+130

804d9b68 89448ffc mov dword ptr [edi+ecx*4-4],eax

CUSTOMER_CRASH_COUNT: 9

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: ashServ.exe

LAST_CONTROL_TRANSFER: from f7f3e3be to 804d9b68

STACK_TEXT:

f8958dc4 f7f3e3be f895a500 81de3050 00000006 nt!memcpy+0x130

WARNING: Stack unwind information not available. Following frames may be wrong.

f895929c f7f3e640 81e27000 81de3008 81de300e w70n51+0x2a3be

f8959c00 f7f1f11a 81e27000 81e8ffd8 81e8f28c w70n51+0x2a640

f8959e30 f7f34abe 81e8f000 f8959e44 81fd4208 w70n51+0xb11a

f8959e4c f7f31037 81e8f000 81d64000 00000001 w70n51+0x20abe

f8959f3c f7f3077b 81eeaa60 8229c600 f8959f84 w70n51+0x1d037

f8959f90 f7f31cf6 81e8f000 f8959fab 00000000 w70n51+0x1c77b

f8959fac f7f31e4b 81e8f000 f8959fd0 f8396e99 w70n51+0x1dcf6

f8959fb8 f8396e99 81e8f000 81f47d98 81f47ffc w70n51+0x1de4b

f8959fd0 804dbbd4 81e8f2a0 81e8f28c 00000000 NDIS!ndisMDpcX+0x21

f8959ff4 804db89e ef579d54 00000000 00000000 nt!KiRetireDpcList+0x46

f8959ff8 ef579d54 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a

804db89e 00000000 00000009 bb835675 00000128 0xef579d54

STACK_COMMAND: kb

FOLLOWUP_IP:

w70n51+2a3be

f7f3e3be ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: w70n51+2a3be

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: w70n51

IMAGE_NAME: w70n51.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3ee71b51

FAILURE_BUCKET_ID: 0xA_w70n51+2a3be

BUCKET_ID: 0xA_w70n51+2a3be

Followup: MachineOwner

---------

fenderebest · 23. mars 2009

Som du kan se av analysen referer de siste "stakkrammene" til modulen w70n51.sys som da er en systemdriver under Windows.

Du kan dermed undersøke videre hvilken funksjon denne driveren har under Windows og når den sist ble oppdatert. Er den gammel kan du prøve å oppdatere.

Positive · 26. mars 2009

Hei! prøver meg her jeg.

Har en 3 år gammel pc som i det siste har trøblet mye med meg og gitt meg blåskjerm.

Jeg formaterte den for ett par dager siden med håp om at det var driverfeil bare.

Men nå har jeg lagt inn Vista Ultimate på den og blåskjermene kommer slik som før. Saken er det at jeg ikke får minidumps lengre!

Jeg har fulgt guider for å sikre at minidumps blir lagret. Men ikke pokker om det kommer noen. I det siste har jeg fått blåskjermer med feilmeldinger i win32.sys og fileinfo.sys.

Håper noen oppvakte kan gi meg en pekepinne på dette!

Hrodebert · 26. mars 2009

Vi forsatte her. Endret 26. mars 2009 av roberteh

w0o0t · 11. april 2009

Hei!

Har endelig fått til å nedgradere en Windows Vista PC til Windows XP med alle drivere og de fungerer som de skal til slutt etter nesten 3mnd søking

Men nå har jeg fått et veldig irriterende problem med min wd ekstern disk som er i et snedig og bråkete usb kabinet. Den fungerte helt fint tidligere i dag, men så tok jeg ut usb (2.0) kabelen av en eller annen grunn og satte den inn igjen og da skjedde det igjen ting!

Er med strømforskyning. Har prøvd å sette strømkontakten i veggkontakt også uten at det hjalp noe. Har også lastet ned Powertoys for Windows Xp som Microsoft har så det er et sikkert program. Skjekka for at alle harddisk bokstaver var merket men det hjalp heller ingenting. Leste også at man kunne prøve å deaktivere 1934 kortet, prøvde det også uten hell.

Greia er at jeg har Windows XP innstallert på harddisken da jeg har brukt den i en stasjonær pc som jeg har bestemt meg for å pakke bort pga plass sparing. Kan det ha

noe med saken og gjøre? at det ligger innstallerte usb drivere i opsen som krasjer med opset jeg bruker nå?

Setter veldig stor pris på all hjelp da jeg har en del musikk og softwares som jeg trenger på den.

Endret 11. april 2009 av w0o0t

fmfouram · 15. august 2009

Heisann folkens

Jeg fikk Bluescreen etter at jeg koblet den nye vifta mi, (cpu-vifte)

Bluescreenen kommer etter at windows baren har loada ferdig..

Jeg er helt ifra meg og ber du/dere på mine knær om hjelp!

Koden,som jeg har fått med meg i hvertfall er Stop 0x000000f4.

Noen ganger kommer jeg helt inn på maskinen,men da går det 5 sek så får jeg BS.

Andre ganger får jeg Bs i oppstart.

Jeg har nå kommet meg inn i pcen via Sikkerhetsmodus.

Jeg ber dere om hjelp.

LaCookie · 4. november 2009

Hallo, har i det siste fått utrolig mange DRIVER_IRQL_NOT_LESS_OR_EQUAL bsod's og har prøvd å feilsøke litt selv.

I det siste har de skjedd under en installasjon av ett spill.

Lasta ned og kjørte memtest86+ uten noen feil. Avinnstallert det jeg har installert siden jeg startet å få disse blåskjermene ofte. Avinstallerte og reinstallerte nVidia driverne men ingenting har fungert til nå.

Jeg fant til slutt denne tråden og prøvde å skjønne hva jeg lette etter på denne analysen men finner ikke noe konkret å jobbe med. Noen andre som kunne hjelpe meg litt på vei?

*******************************************************************************
* *

* 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: 0000000000001008, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, value 0 = read operation, 1 = write operation

Arg4: fffffa8003eba05f, address which referenced memory

Debugging Details:

------------------

Page c0518 not present in the dump file. Type ".hh dbgerr004" for details

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

WRITE_ADDRESS: 0000000000001008

CURRENT_IRQL: 2

FAULTING_IP:

+0

fffffa80`03eba05f c60201 mov byte ptr [rdx],1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Installer.exe

TRAP_FRAME: fffff800030e9da0 -- (.trap 0xfffff800030e9da0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=00000001a1bad12f rbx=0000000000000000 rcx=fffffa8003eba010

rdx=0000000000001008 rsi=0000000000000000 rdi=0000000000000000

rip=fffffa8003eba05f rsp=fffff800030e9f38 rbp=fffffa600cd9aca0

r8=0000000000000000 r9=0000000000000000 r10=fffffa8003c15bb0

r11=0000000000000246 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

fffffa80`03eba05f c60201 mov byte ptr [rdx],1 ds:040e:1008=??

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001c5b46e to fffff80001c5b6d0

STACK_TEXT:

fffff800`030e9c58 fffff800`01c5b46e : 00000000`0000000a 00000000`00001008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff800`030e9c60 fffff800`01c5a34b : 00000000`00000001 fffffa60`00b5073e fffffa60`009fe000 fffffa80`03eba010 : nt!KiBugCheckDispatch+0x6e

fffff800`030e9da0 fffffa80`03eba05f : fffff800`01c64cd7 fffffa80`03eba010 fffffa60`0cd9aca0 fffff800`01d7ea80 : nt!KiPageFault+0x20b

fffff800`030e9f38 fffff800`01c64cd7 : fffffa80`03eba010 fffffa60`0cd9aca0 fffff800`01d7ea80 00000000`00000000 : 0xfffffa80`03eba05f

fffff800`030e9f40 fffff800`01c5eba5 : fffffa80`03eba058 fffff800`01d7b680 fffffa60`0cd9aca0 00000000`03faf445 : nt!KiRetireDpcList+0x117

fffff800`030e9fb0 fffff800`01c5e9b7 : 00000000`00000bec 00000000`7efad000 00000000`027cfd20 00000000`027cf120 : nt!KyRetireDpcList+0x5

fffffa60`0cd9abf0 fffff800`01ca2c18 : 00000000`03ed0056 fffffa60`0cd9aca0 00000000`0001092a 00000000`03fac22c : nt!KiDispatchInterruptContinue

fffffa60`0cd9ac20 00000000`02ee79ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xf8

00000000`03229100 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2ee79ea

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!KiPageFault+20b

fffff800`01c5a34b 488d058e320000 lea rax,[nt!ExpInterlockedPopEntrySListResume (fffff800`01c5d5e0)]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiPageFault+20b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a796b09

FAILURE_BUCKET_ID: X64_0xD1_nt!KiPageFault+20b

BUCKET_ID: X64_0xD1_nt!KiPageFault+20b

Followup: MachineOwner

---------

Aafloey · 20. desember 2010

Hei. En kamerat av meg har vært plaget med blåskjerm de siste dagene, spesielt når han skal spille black ops. Jeg fikk han til å sende meg dump fila, og jeg fikk ut dette av den:

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: 0000000000008000, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, 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: fffff8000310a0a2, address which referenced memory

Debugging Details:

------------------

WRITE_ADDRESS: 0000000000008000

CURRENT_IRQL: 2

FAULTING_IP:

nt!KxWaitForLockOwnerShip+12

fffff800`0310a0a2 48890a mov qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff880079a8f60 -- (.trap 0xfffff880079a8f60)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=00000000079a92d8 rbx=0000000000000000 rcx=fffff880079a91a8

rdx=0000000000008000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8000310a0a2 rsp=fffff880079a90f0 rbp=fffff880079a9180

r8=fffff88003163180 r9=0000000000000000 r10=fffff80003303840

r11=0000058000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!KxWaitForLockOwnerShip+0x12:

fffff800`0310a0a2 48890a mov qword ptr [rdx],rcx ds:0202:00000000`00008000=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030c8ca9 to fffff800030c9740

STACK_TEXT:

fffff880`079a8e18 fffff800`030c8ca9 : 00000000`0000000a 00000000`00008000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

fffff880`079a8e20 fffff800`030c7920 : 00000000`00000000 fffffa80`0229e7b0 00000000`00000000 fffff880`079a9d78 : nt!KiBugCheckDispatch+0x69

fffff880`079a8f60 fffff800`0310a0a2 : 00000000`00000000 00000000`00000001 fffffa80`039ef4b8 00000000`00000001 : nt!KiPageFault+0x260

fffff880`079a90f0 fffff800`030e2314 : fffffa80`0229e7b0 00000000`00000000 fffff880`079a9180 fffffa80`039ef3b0 : nt!KxWaitForLockOwnerShip+0x12

fffff880`079a9120 fffff800`0310fdc1 : 00000000`00000000 fffffa80`0229e7b0 0000000f`ffffffff 00000000`00000000 : nt!MiInsertPageInFreeOrZeroedList+0x4e4

fffff880`079a9220 fffff800`0310fac1 : 9fd00000`00000000 fffff680`00013538 00000000`00000200 000fffff`ffffffff : nt!MiDeletePteList+0x131

fffff880`079a92a0 fffff800`0310adee : 00000000`00000002 fffff880`00000000 fffffa80`06846b30 fffffa80`06846ec8 : nt!MiDecommitPages+0x1a1

fffff880`079a9b30 fffff800`030c8993 : ffffffff`ffffffff 00000000`0222ef08 00000000`0222ef00 00000000`00000001 : nt!NtFreeVirtualMemory+0x2de

fffff880`079a9c20 00000000`77c3ff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`0222ee58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c3ff3a

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!KxWaitForLockOwnerShip+12

fffff800`0310a0a2 48890a mov qword ptr [rdx],rcx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12

BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12

Followup: MachineOwner

---------

Noen av dere som vet hva som er galt her? Utifra det jeg ser så er det en driver, eller ram brikkene?

Hvordan DU kan feilsøke Windows! (Guider)

Anbefalte innlegg

Lenke til kommentar

Videoannonse

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Opprett konto

Logg inn

Hvem er aktive 0 medlemmer