Får stadig bluescreen

idenb · 22. januar 2010

Hei!

Som topicen sier så får jeg stadig bluescreen. Det begynt helt plutselig, jeg lukket alle programmene jeg hadde oppe, og tok meg en pause. Når jeg kom tilbake ble jeg møt med bluescreen.Jeg restartet pcen,og alt gikk som normalt.

Jeg gikk inn og tullet litt rundt på internet, men etter 10 min fikk jeg et nytt bluescreen... Jeg restartet pcen på nytt, men fikk denne gangen bluescreen under oppstart.

Det vil si at jeg noen ganger klarte å komme inn til desktop før bluescreen, men andre ganger kom det under oppstart.

Jeg bestemte meg da for å formatere pcen for å se om det hjalp. Det skal også sies at jeg hadde litt problemer å formatere siden jeg stadig fikk bluescreen.

Etter jeg var ferdig md formateringen, la jeg inn alle driverene jeg fikk med på cd og alt det der.

Når jeg var ferdig med det, så skulle jeg legge inn Antivirusprogram, og det var da jeg fikk et nytt bluescreen. Og det er det jeg sliter med ennå...

Det virker som om jeg kan være toppen 10 min med pcen på før problemet oppstår. Jeg gjør ikke noe spesielt, det kommer bare helt uten videre...

PC spec som jeg husker nå i farta:

windows vista ultimate x64

4Gb ram

Nvidia 8600gt

Er laptop hvis det skal være nyttig info

Feilmeldingen som kommer opp er:

*** STOP: 0X0000003B (0X00000000C0000005, 0XFFFFF9600002405E, 0XFFFFF9801992D5D0,0X000000000000000000)

*** win32k.sys - Adress FFFFF9600002405E base at FFFFF96000000000, Datestamp

49edb9fa

Så mitt spørsmål til dere der ute er om noen har peiling på hva dette kan skyldes?

Har prøvd å fortelle det så grundig så mulig, men om dere trenger mer info, så skal jeg prøve å adde mer.

Endret 22. januar 2010 av idenb

Mechablast · 22. januar 2010

Last ned memtest, brenn det som image og boot maskinen fra cden, post resultatet her.

idenb · 22. januar 2010

skal prøve...

Fant også ut at jeg skulle prøve med degugging tools, men når jeg instalerer det kommer det opp en feilmerlding som sier at " debugging tools støtter ikke denne prosessortypen" eller noe i den duren..

EDIT:

Du må nok forklare litt videre(i detalj) hva jeg skal gjøre angående Memtesten. Hva skal jeg gjøre med ISO-filen? Hvordan åpner jeg den?

Endret 22. januar 2010 av idenb

Mechablast · 22. januar 2010

Last ned iso brenner her

Pakk ut filen (memtest) med winrar eller det du programet du bruker til å pakke ut rarfiler, åpne iso filen i brennerprogramet og brenn iso filen til cd.

Memtest bør kjøres en stund, gjerne over natten.

Endret 22. januar 2010 av arjato

idenb · 22. januar 2010

Ok, skal gjøre det i natt

Fikk foresten lastet ned Debugging tools, men når jeg kjører programmet og skal åpne minidump-filene, så står det at jeg ikke er den rettmessige eieren eller er administrator (noe jeg er(?) . Med andre ord, jeg får ikke åpnet den i Windbg. Noen som vet hva jeg kan gjøre?

EDIT: Klarte nå å kjøre dumpfilene i Wnindbg nå og fikk dette opp:

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Loading Dump File [C:\Windows\Minidump\Mini012210-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/downloads/symbols

Windows Vista Kernel Version 6000 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 6000.16901.amd64fre.vista_gdr.090805-0102

Machine Name:

Kernel base = 0xfffff800`02400000 PsLoadedModuleList = 0xfffff800`0259af70

Debug session time: Fri Jan 22 16:00:55.332 2010 (GMT+1)

System Uptime: 0 days 0:08:02.305

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

....

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, c, fffffa8003c7bb50, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2de4 )

Followup: MachineOwner

---------

0: kd> !analyze-v

No export analyze-v found

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)

A device driver attempting to corrupt the system has been caught. This is

because the driver was specified in the registry as being suspect (by the

administrator) and the kernel has enabled substantial checking of this driver.

If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will

be among the most commonly seen crashes.

Arguments:

Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by

the operating system. The only supported way to extend a kernel

mode stack is by using KeExpandKernelStackAndCallout.

Arg2: 000000000000000c

Arg3: fffffa8003c7bb50

Arg4: 0000000000000000

Debugging Details:

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

BUGCHECK_STR: 0xc4_91

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: c

EXCEPTION_RECORD: fffff980014df9c8 -- (.exr 0xfffff980014df9c8)

ExceptionAddress: fffff8000244fd1d (nt!KiSwapContext+0x00000000000000ed)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff980014dfa70 -- (.trap 0xfffff980014dfa70)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=fffff980014dfbd0

rdx=0000000000124000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8000244fd1d rsp=fffff980014dfc08 rbp=fffff8000254a980

r8=0000000000000000 r9=0000000000007e00 r10=000000000000000f

r11=fffffa8003c7a5cc r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!KiSwapContext+0xed:

fffff800`0244fd1d c3 ret

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000241673d to fffff8000244db90

STACK_TEXT:

fffff980`014deb78 fffff800`0241673d : 00000000`000000c4 00000000`00000091 00000000`0000000c fffffa80`03c7bb50 : nt!KeBugCheckEx

fffff980`014deb80 fffff800`0248cfa5 : 00000000`00000000 00000000`00000000 00000000`00000003 fffff800`028e8e5c : nt! ?? ::FNODOBFM::`string'+0x2de4

fffff980`014debc0 fffff800`024321d2 : fffff980`014df9c8 fffff980`014df3a0 fffff980`014dfa70 fffff980`014da000 : nt!RtlDispatchException+0x35

fffff980`014df290 fffff800`0244d9ee : fffff980`014df9c8 fffff800`0254a980 fffff980`014dfa70 00000000`00000000 : nt!KiDispatchException+0xc2

fffff980`014df890 fffff800`0244c5cd : fffffa80`03c7bb50 fffffa80`0412bbb0 01fff800`0254a980 00fff800`024500cf : nt!KiExceptionDispatch+0xae

fffff980`014dfa70 fffff800`0244fd1d : fffff800`0245cf55 fffffa80`03c7b010 fffffa80`00000000 00000000`00000040 : nt!KiGeneralProtectionFault+0xcd

fffff980`014dfc08 fffff800`0245cf55 : fffffa80`03c7b010 fffffa80`00000000 00000000`00000040 00000000`00000000 : nt!KiSwapContext+0xed

fffff980`014dfc10 fffff800`0245cc9d : 00000000`00000001 fffff800`0000000f 00000000`0000000f fffff800`0254a980 : nt!KiSwapThread+0x125

fffff980`014dfc70 fffff800`0269051d : 00000000`000000c3 00000000`00000000 00000000`00000000 800000f8`00000000 : nt!KeWaitForSingleObject+0x5f5

fffff980`014dfcf0 fffff800`026e202b : ffffffff`ff676980 fffffa80`03c7bb50 00000000`00000080 fffffa80`03c7b010 : nt!EtwpLogger+0xdd

fffff980`014dfd50 fffff800`024344f6 : fffff800`0254a980 fffffa80`03c7bb50 fffffa80`03ca5bb0 fffffa80`03c7b1e0 : nt!PspSystemThreadStartup+0x5b

fffff980`014dfd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+2de4

fffff800`0241673d cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2de4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a7970dc

FAILURE_BUCKET_ID: X64_0xc4_91_nt!_??_::FNODOBFM::_string_+2de4

BUCKET_ID: X64_0xc4_91_nt!_??_::FNODOBFM::_string_+2de4

Followup: MachineOwner

---------

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Loading Dump File [C:\Windows\Minidump\Mini110709-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/downloads/symbols

Windows Vista Kernel Version 6000 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 6000.16901.amd64fre.vista_gdr.090805-0102

Machine Name:

Kernel base = 0xfffff800`02400000 PsLoadedModuleList = 0xfffff800`0259af70

Debug session time: Fri Oct 30 03:25:55.384 2009 (GMT+1)

System Uptime: 0 days 0:02:31.290

Loading Kernel Symbols

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

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

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff98005080f46, 0, ffffffffffffffff}

Probably caused by : usbhub.sys ( usbhub!UsbhReferenceListRemove+5a )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

KMODE_EXCEPTION_NOT_HANDLED (1e)

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.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff98005080f46, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

FAULTING_IP:

usbhub!UsbhReferenceListRemove+5a

fffff980`05080f46 813972664c53 cmp dword ptr [rcx],534C6672h

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800025fa0b0

ffffffffffffffff

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: Idle

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800024bac37 to fffff8000244db90

STACK_TEXT:

fffff800`03cb5198 fffff800`024bac37 : 00000000`0000001e ffffffff`c0000005 fffff980`05080f46 00000000`00000000 : nt!KeBugCheckEx

fffff800`03cb51a0 fffff800`0244d9ee : fffff800`03cb58d8 fffffa80`07fbcaa0 fffff800`03cb5980 fffffa80`0898d480 : nt! ?? ::FNODOBFM::`string'+0x12707

fffff800`03cb57a0 fffff800`0244c5cd : ffff0180`038c7853 fffff980`00467188 fffff800`0254dc80 fffff800`0253d99b : nt!KiExceptionDispatch+0xae

fffff800`03cb5980 fffff980`05080f46 : fffffa80`088ed050 fffff980`050613d0 fffffa80`089cd430 fffffa80`088edef8 : nt!KiGeneralProtectionFault+0xcd

fffff800`03cb5b10 fffff980`0507780d : fffffa80`07fbc050 fffffa80`07fbc1a0 00000001`088edd02 00000000`5a2d0831 : usbhub!UsbhReferenceListRemove+0x5a

fffff800`03cb5b50 fffff800`02447f12 : fffff800`03cb5c88 00000000`00000000 00000000`5a2d0831 00000000`5a2d0831 : usbhub!UsbhDmTimerDpc+0x39

fffff800`03cb5bc0 fffff800`0245037c : 00000053`501edfb9 00000000`0000000c fffff800`0254e102 fffff800`0254fc80 : nt!KiTimerExpiration+0x694

fffff800`03cb5d10 fffff800`0244fb2f : 00000000`00000001 fffff800`0254a980 00000000`00000001 fffff800`0254fc80 : nt!KiRetireDpcList+0xbf

fffff800`03cb5d80 fffff800`02600724 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5f

fffff800`03cb5db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1d4

STACK_COMMAND: kb

FOLLOWUP_IP:

usbhub!UsbhReferenceListRemove+5a

fffff980`05080f46 813972664c53 cmp dword ptr [rcx],534C6672h

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: usbhub!UsbhReferenceListRemove+5a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46d773fa

FAILURE_BUCKET_ID: X64_0x1E_usbhub!UsbhReferenceListRemove+5a

BUCKET_ID: X64_0x1E_usbhub!UsbhReferenceListRemove+5a

Followup: MachineOwner

---------

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Loading Dump File [C:\Windows\Minidump\Mini110709-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 Vista Kernel Version 6000 MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 6000.16901.amd64fre.vista_gdr.090805-0102

Machine Name:

Kernel base = 0xfffff800`02400000 PsLoadedModuleList = 0xfffff800`0259af70

Debug session time: Sat Nov 7 18:35:03.857 2009 (GMT+1)

System Uptime: 0 days 7:38:20.775

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

.....

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904ab, fffff980128f4c88, fffff980128f4660, fffff98000b23b4c}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+201 )

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

NTFS_FILE_SYSTEM (24)

If you see NtfsExceptionFilter on the stack then the 2nd and 3rd

parameters are the exception record and context record. Do a .cxr

on the 3rd parameter and then kb to obtain a more informative stack

trace.

Arguments:

Arg1: 00000000001904ab

Arg2: fffff980128f4c88

Arg3: fffff980128f4660

Arg4: fffff98000b23b4c

Debugging Details:

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

EXCEPTION_RECORD: fffff980128f4c88 -- (.exr 0xfffff980128f4c88)

ExceptionAddress: fffff98000b23b4c (Ntfs!NtfsFindPrefixHashEntry+0x0000000000000201)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

CONTEXT: fffff980128f4660 -- (.cxr 0xfffff980128f4660)

rax=000000000000007a rbx=2efff88011a59930 rcx=000000000000012a

rdx=0000000000000001 rsi=0000000000000000 rdi=fffffa8007c33c18

rip=fffff98000b23b4c rsp=fffff980128f4ec0 rbp=fffffa800b59c010

r8=0000000021a18c95 r9=0000000000000000 r10=fffff88000776000

r11=fffff980128f4f00 r12=fffff980128f51b0 r13=fffff980128f53c0

r14=fffff8800017fbd0 r15=0000000000000003

iopl=0 nv up ei pl nz na pe nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202

Ntfs!NtfsFindPrefixHashEntry+0x201:

fffff980`00b23b4c 44394310 cmp dword ptr [rbx+10h],r8d ds:002b:2efff880`11a59940=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msiexec.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800025fa0b0

ffffffffffffffff

FOLLOWUP_IP:

Ntfs!NtfsFindPrefixHashEntry+201

fffff980`00b23b4c 44394310 cmp dword ptr [rbx+10h],r8d

FAULTING_IP:

Ntfs!NtfsFindPrefixHashEntry+201

fffff980`00b23b4c 44394310 cmp dword ptr [rbx+10h],r8d

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from fffff98000b1eeff to fffff98000b23b4c

STACK_TEXT:

fffff980`128f4ec0 fffff980`00b1eeff : fffffa80`0b59c010 fffffa80`07c33c18 fffff880`0017fbd0 fffff980`00734901 : Ntfs!NtfsFindPrefixHashEntry+0x201

fffff980`128f4fe0 fffff980`00b1d594 : fffffa80`0b59c010 fffffa80`0c882010 fffff980`128f51b0 fffff980`128f51c8 : Ntfs!NtfsFindStartingNode+0x45f

fffff980`128f50b0 fffff980`00a98edd : fffffa80`0b59c010 fffffa80`0c882010 fffff980`128f53c0 00000000`00125900 : Ntfs!NtfsCommonCreate+0x9df

fffff980`128f5240 fffff800`02437c0f : fffff980`128f5330 fffff880`1292e9b0 fffff980`128f5730 fffff980`00a92c3f : Ntfs!NtfsCommonCreateCallout+0x1d

fffff980`128f5270 fffff980`00a9742a : fffff980`00a98ec0 fffff980`128f5330 00000000`00000000 fffffa80`0c882010 : nt!KeExpandKernelStackAndCalloutEx+0x2d1

fffff980`128f5300 fffff980`00b251e2 : 00000000`00000000 fffff980`128f53c0 fffffa80`0c882010 fffffa80`0c882010 : Ntfs!NtfsCommonCreateOnNewStack+0x3a

fffff980`128f5360 fffff980`0073021a : fffffa80`07c33030 fffffa80`0c882010 fffffa80`0b686000 fffffa80`0c882001 : Ntfs!NtfsFsdCreate+0x1b2

fffff980`128f5500 fffff980`0074c28d : fffffa80`07c8a040 fffffa80`07c958e0 fffffa80`0c882000 fffff980`128f55c0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20a

fffff980`128f5570 fffff800`026912e3 : 00000000`00000000 fffff800`02690a60 00000000`00000000 fffff880`03de70b0 : fltmgr!FltpCreate+0x27e

fffff980`128f5620 fffff800`0268fc91 : fffffa80`07bf3ce0 fffff980`128f5840 fffffa80`0cf46010 00000000`00000001 : nt!IopParseDevice+0x883

fffff980`128f57a0 fffff800`0269c361 : 00000000`00000000 fffff980`128f5928 fffff880`00000040 00000000`00000000 : nt!ObpLookupObjectName+0xa9f

fffff980`128f58b0 fffff800`026d947d : fffffa80`00000080 00000000`00000000 00000000`00000001 00000000`016fd138 : nt!ObOpenObjectByName+0x421

fffff980`128f5980 fffff800`0244d633 : fffffa80`0c9aa060 fffff980`128f5ca0 fffffa80`0c9aa060 00000000`00000004 : nt!NtQueryAttributesFile+0x13c

fffff980`128f5c20 00000000`7701064a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`016fcce8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7701064a

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Ntfs!NtfsFindPrefixHashEntry+201

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4764f452

STACK_COMMAND: .cxr 0xfffff980128f4660 ; kb

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsFindPrefixHashEntry+201

BUCKET_ID: X64_0x24_Ntfs!NtfsFindPrefixHashEntry+201

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

NTFS_FILE_SYSTEM (24)

If you see NtfsExceptionFilter on the stack then the 2nd and 3rd

parameters are the exception record and context record. Do a .cxr

on the 3rd parameter and then kb to obtain a more informative stack

trace.

Arguments:

Arg1: 00000000001904ab

Arg2: fffff980128f4c88

Arg3: fffff980128f4660

Arg4: fffff98000b23b4c

Debugging Details:

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

EXCEPTION_RECORD: fffff980128f4c88 -- (.exr 0xfffff980128f4c88)

ExceptionAddress: fffff98000b23b4c (Ntfs!NtfsFindPrefixHashEntry+0x0000000000000201)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

CONTEXT: fffff980128f4660 -- (.cxr 0xfffff980128f4660)

rax=000000000000007a rbx=2efff88011a59930 rcx=000000000000012a

rdx=0000000000000001 rsi=0000000000000000 rdi=fffffa8007c33c18

rip=fffff98000b23b4c rsp=fffff980128f4ec0 rbp=fffffa800b59c010

r8=0000000021a18c95 r9=0000000000000000 r10=fffff88000776000

r11=fffff980128f4f00 r12=fffff980128f51b0 r13=fffff980128f53c0

r14=fffff8800017fbd0 r15=0000000000000003

iopl=0 nv up ei pl nz na pe nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202

Ntfs!NtfsFindPrefixHashEntry+0x201:

fffff980`00b23b4c 44394310 cmp dword ptr [rbx+10h],r8d ds:002b:2efff880`11a59940=????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msiexec.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruksjonen i 0x%08lx refererte minne ved adressen 0x%08lx. Minnet kunne ikke v re %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff