Problemer med bluescreen og får ikke installert WinDbg

Hoikka · 9. august 2011

Hei, de siste tre dagene har jeg hatt tre blåskjermer. Jeg fikk en blåskjerm for noen uker siden. Alle fire blåskjermene har inntruffet mens jeg har spillt League of Legends. Har ikke hatt noen problemer med pcen får disse blåskjermene. Jeg reinstallerte spillet etter den første blåskjermen. Har ikke spillt noen andre spill etter at den første blåskjermen inntraff, så vet ikke om LoL har noe med saken å gjøre. Blåskjermen har kommet etter 4-6 timers spilling i ett.

Etter den andre blåskjermen leste jeg fenderebest sin fine guide om blåskjermer, og lastet ned WinDbg, men når jeg skulle installere programmet kom denne feilmeldingen:

Lastet ned denne. Det funker ikke å laste ned 32-bits versjonen heller.

Kan også nevne at jeg reformaterte pcen rett etter påske og satt inn en SSD, men dette er eneste problemet jeg har hatt. Noen genier der ute som har en løsning??

Hoikka · 12. august 2011

Ingen som kan hjelpe??

Sceptic · 12. august 2011

Hei,

Løsningen på problemet ditt står i meldingen du fikk.

.NET 4 Framwork

Du trenger sannsynligvis også debuggingsymboler til ditt OS.

Sceptic

Hoikka · 3. september 2011

Sånn, da fikk jeg endelig WinDbg oppe å kjører med symboler.

Kjørte WinDbg med de tre kjerneminnedumpene jeg hadde. Fikk blåskjermer i går, men finner ikke kjerneminnedumpene for dem.

Noen som kan ta en liten titt, og eventuelt hjelpe??

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [H:\Krasjdumper\082011-13026-01.dmp]

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

Symbol search path is: srv*H:\Krasjdumper\Symboler*http://msdl.microsoft.com/download/symbols

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

Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506

Machine Name:

Kernel base = 0xfffff800`01c52000 PsLoadedModuleList = 0xfffff800`01e97670

Debug session time: Sat Aug 20 01:56:12.196 2011 (UTC + 2:00)

System Uptime: 0 days 0:04:07.336

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

....

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88007623fc5, fffff880099ae6c8, fffff880099adf20}

Probably caused by : atikmdag.sys ( atikmdag+376fc5 )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

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: ffffffffc0000005, The exception code that was not handled

Arg2: fffff88007623fc5, The address that the exception occurred at

Arg3: fffff880099ae6c8, Exception Record Address

Arg4: fffff880099adf20, Context Record Address

Debugging Details:

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

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

FAULTING_IP:

atikmdag+376fc5

fffff880`07623fc5 488b4118 mov rax,qword ptr [rcx+18h]

EXCEPTION_RECORD: fffff880099ae6c8 -- (.exr 0xfffff880099ae6c8)

ExceptionAddress: fffff88007623fc5 (atikmdag+0x0000000000376fc5)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

CONTEXT: fffff880099adf20 -- (.cxr 0xfffff880099adf20)

rax=fffff8a0097c3600 rbx=fffff8a000f41df8 rcx=ff7ff8a009a17b08

rdx=fffff880099ae9f0 rsi=fffff8a000f41000 rdi=000000000000009a

rip=fffff88007623fc5 rsp=fffff880099ae908 rbp=0000000000000095

r8=fffffa800a661580 r9=0000000000000800 r10=00000000ffffffff

r11=fffff8a009837bb8 r12=fffff8a000f1c440 r13=000000000000009a

r14=fffffa800a661580 r15=fffffa800a5ad670

iopl=0 nv up ei ng nz na pe nc

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

atikmdag+0x376fc5:

fffff880`07623fc5 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:ff7ff8a0`09a17b20=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_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 fffff80001f01100

ffffffffffffffff

FOLLOWUP_IP:

atikmdag+376fc5

fffff880`07623fc5 488b4118 mov rax,qword ptr [rcx+18h]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff8800766a07f to fffff88007623fc5

STACK_TEXT:

fffff880`099ae908 fffff880`0766a07f : 00000000`00000000 00000000`00000001 00000000`0000009a fffffa80`0b22de60 : atikmdag+0x376fc5

fffff880`099ae910 00000000`00000000 : 00000000`00000001 00000000`0000009a fffffa80`0b22de60 fffffa80`0a5ad670 : atikmdag+0x3bd07f

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+376fc5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ddc6c20

STACK_COMMAND: .cxr 0xfffff880099adf20 ; kb

FAILURE_BUCKET_ID: X64_0x7E_atikmdag+376fc5

BUCKET_ID: X64_0x7E_atikmdag+376fc5

Followup: MachineOwner

---------

På de to andre kjerneminnedumpene fikk jeg denne meldingen når jeg skrev inn !analyze -v

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [H:\Krasjdumper\081011-13774-01.dmp]

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

Symbol search path is: srv*H:\Krasjdumper\Symboler*http://msdl.microsoft.com/download/symbols

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

Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631

Machine Name:

Kernel base = 0xfffff800`01c0c000 PsLoadedModuleList = 0xfffff800`01e51650

Debug session time: Wed Aug 10 18:46:23.532 2011 (UTC + 2:00)

System Uptime: 0 days 2:53:02.672

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

........

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1a14b1af, 2, 1, fffff8800941d393}

Probably caused by : hardware ( hidusb!HumReadReport+43 )

Followup: MachineOwner

---------

3: kd> !analyse -v

No export analyse found

Edit: Fikk ikke til å laste opp kjerneminnedumpene her på forumet.

Endret 3. september 2011 av Hoikka

The Crusher · 3. september 2011

Du kan laste de opp i et zippet arkiv, eller laste de opp på mediafire.com.

Det jeg ser her er at atikmdag.sys er synderen i den ene. Det er noe til grafikkortets driver. Den det står hardware i, kan liksegodt være pga at skjermkortet krasjet istedet for driveren.

Hoikka · 3. september 2011

Installerer nyeste grafikk kort driver nå. Burde jeg kryss sjekke PC'en og grafikk kortet mitt med et annet kort og pc??

Sånn, håper denne fungerer.

Krasjdumper.rar

Hoikka · 6. september 2011

I dag fikk jeg blåskjerm når jeg startet datamaskinen. Jeg fant minnedumpene for de to siste blåskjermene, hadde vært veldig fint hvis noen kunne tatt en kikk på dem.

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [H:\Krasjdumper\090311-13868-01.dmp]

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

Symbol search path is: srv*H:\Krasjdumper\Symboler*http://msdl.microsoft.com/download/symbols

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

Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506

Machine Name:

Kernel base = 0xfffff800`01e54000 PsLoadedModuleList = 0xfffff800`02099670

Debug session time: Sat Sep 3 16:39:21.350 2011 (UTC + 2:00)

System Uptime: 0 days 3:57:07.850

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8800738ea45, fffff8800c9ae770, 0}

Probably caused by : atikmdag.sys ( atikmdag+388a45 )

Followup: MachineOwner

---------

3: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the bugcheck

Arg2: fffff8800738ea45, Address of the instruction which caused the bugcheck

Arg3: fffff8800c9ae770, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

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

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

FAULTING_IP:

atikmdag+388a45

fffff880`0738ea45 488b4118 mov rax,qword ptr [rcx+18h]

CONTEXT: fffff8800c9ae770 -- (.cxr 0xfffff8800c9ae770)

rax=fffff880074a3c00 rbx=0000000000000005 rcx=ff7ff8a00b3d9128

rdx=fffffa800ab2cec0 rsi=fffff8a00b6a9268 rdi=fffff8a0041dc828

rip=fffff8800738ea45 rsp=fffff8800c9af158 rbp=fffff8a0041dc828

r8=fffff8a0041dc828 r9=00000000000158e4 r10=00000000fffffffe

r11=fffff8a00b6a9238 r12=0000000000000000 r13=fffff8a00b6a9268

r14=fffffa800ab2cec0 r15=fffff8800c9af430

iopl=0 nv up ei ng nz na po nc

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

atikmdag+0x388a45:

fffff880`0738ea45 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:ff7ff8a0`0b3d9140=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: League of Lege

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800738ea45

STACK_TEXT:

fffff880`0c9af158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x388a45

FOLLOWUP_IP:

atikmdag+388a45

fffff880`0738ea45 488b4118 mov rax,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+388a45

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e31d49f

STACK_COMMAND: .cxr 0xfffff8800c9ae770 ; kb

FAILURE_BUCKET_ID: X64_0x3B_atikmdag+388a45

BUCKET_ID: X64_0x3B_atikmdag+388a45

Followup: MachineOwner

---------

Denne er fra i dag, når jeg startet opp maskinen. Her har jeg oppdatert grafikkort driveren, det var noen måner gammel Catalyst under de andre blåskjermene.

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [H:\Krasjdumper\090611-13416-01.dmp]

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

Symbol search path is: srv*H:\Krasjdumper\Symboler*http://msdl.microsoft.com/download/symbols

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

Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506

Machine Name:

Kernel base = 0xfffff800`01e00000 PsLoadedModuleList = 0xfffff800`02045670

Debug session time: Tue Sep 6 20:21:53.558 2011 (UTC + 2:00)

System Uptime: 0 days 0:00:13.058

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

....

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000e1ad7, fffff8800a548fe0, 0}

Probably caused by : win32k.sys ( win32k!HMAllocObject+43 )

Followup: MachineOwner

---------

4: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the bugcheck

Arg2: fffff960000e1ad7, Address of the instruction which caused the bugcheck

Arg3: fffff8800a548fe0, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

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

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

FAULTING_IP:

win32k!HMAllocObject+43

fffff960`000e1ad7 488bbd58010000 mov rdi,qword ptr [rbp+158h]

CONTEXT: fffff8800a548fe0 -- (.cxr 0xfffff8800a548fe0)

rax=0000000000000000 rbx=0000000000000020 rcx=fffff960002cb1b0

rdx=0000000000000000 rsi=0000000000008802 rdi=0000000000000000

rip=fffff960000e1ad7 rsp=fffff8800a5499c0 rbp=0000000000000000

r8=0000000000000010 r9=0000000000000080 r10=fffff80002000c80

r11=fffffa80091a57a0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000080 r15=0000000000000010

iopl=0 nv up ei pl nz na pe nc

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

win32k!HMAllocObject+0x43:

fffff960`000e1ad7 488bbd58010000 mov rdi,qword ptr [rbp+158h] ss:0018:00000000`00000158=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: avgchsva.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960000e1ad7

STACK_TEXT:

fffff880`0a5499c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!HMAllocObject+0x43

FOLLOWUP_IP:

win32k!HMAllocObject+43

fffff960`000e1ad7 488bbd58010000 mov rdi,qword ptr [rbp+158h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HMAllocObject+43

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4df2dbd1

STACK_COMMAND: .cxr 0xfffff8800a548fe0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HMAllocObject+43

BUCKET_ID: X64_0x3B_win32k!HMAllocObject+43

Followup: MachineOwner

---------

Her er minnedump filene, hvis noen kan hjelpe.

Krasjdumper 2.rar

Vært fint om noen orket å hjelpe.

The Crusher · 6. september 2011

På de to siste du postet nå, så er den ene win32k.sys, og den andre skjermkort driveren. Jeg har ikek sett på dump filene selv, bare leste loggene du postet. Har desverre ikke muligheten til og se på dumpfilene før imorgen, bare for å bekrefte det.

Hoikka · 6. september 2011

Okei, takk for svar

Er det noe jeg kan gjøre med problemet?? Regner med at win32k.sys har noe med Windows å gjøre, har ikke noe problem med å formatere SSD'en og sette inn Windows på nytt hvis det er det som er må til eller er lettest.

Hoikka · 8. september 2011

Presterte å få blåskerm i går... Er det "atikmdag.sys" som er grafikk kortet?? Noen som vet om en mulig løsning, når det ser ut som det er to(?) ting som er problemet??

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [H:\Krasjdumper\090711-13228-01.dmp]

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

Symbol search path is: srv*H:\Krasjdumper\Symboler*http://msdl.microsoft.com/download/symbols

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

Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506

Machine Name:

Kernel base = 0xfffff800`01e00000 PsLoadedModuleList = 0xfffff800`02045670

Debug session time: Wed Sep 7 22:55:08.536 2011 (UTC + 2:00)

System Uptime: 0 days 0:59:36.036

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

.....

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880077ada45, fffff8800e565770, 0}

Probably caused by : atikmdag.sys ( atikmdag+388a45 )

Followup: MachineOwner

---------

1: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the bugcheck

Arg2: fffff880077ada45, Address of the instruction which caused the bugcheck

Arg3: fffff8800e565770, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

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

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

FAULTING_IP:

atikmdag+388a45

fffff880`077ada45 488b4118 mov rax,qword ptr [rcx+18h]

CONTEXT: fffff8800e565770 -- (.cxr 0xfffff8800e565770)

rax=fffff880078c2c00 rbx=0000000000000005 rcx=ff7ff8a003c9d128

rdx=fffffa80075cb9c0 rsi=fffff8a003d1aa30 rdi=fffff8a002ec44c8

rip=fffff880077ada45 rsp=fffff8800e566158 rbp=fffff8a002ec44c8

r8=fffff8a002ec44c8 r9=0000000000016904 r10=00000000fffffffe

r11=fffff8a003d1aa00 r12=0000000000000000 r13=fffff8a003d1aa30

r14=fffffa80075cb9c0 r15=fffff8800e566430

iopl=0 nv up ei ng nz na po nc

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

atikmdag+0x388a45:

fffff880`077ada45 488b4118 mov rax,qword ptr [rcx+18h] ds:002b:ff7ff8a0`03c9d140=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: League of Lege

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880077ada45

STACK_TEXT:

fffff880`0e566158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x388a45

FOLLOWUP_IP:

atikmdag+388a45

fffff880`077ada45 488b4118 mov rax,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+388a45

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e31d49f

STACK_COMMAND: .cxr 0xfffff8800e565770 ; kb

FAILURE_BUCKET_ID: X64_0x3B_atikmdag+388a45

BUCKET_ID: X64_0x3B_atikmdag+388a45

Followup: MachineOwner

---------

Krasjdumper 3.rar

Endret 8. september 2011 av Hoikka

The Crusher · 8. september 2011

Siden jeg merkelig ikke får lastet ned dump filene får jeg ikke sjekket de. MEn ut ifra hva du poster var det spillet LoL og skjermkortdriveren igjen.

Hoikka · 8. september 2011

Hmm, er det letteste å reformatere SSD'en, hvor alt dette ligger på?? Eller vet du om det er noen annen mulighet for å få fikset dette??

The Crusher · 8. september 2011

Du har prøvd eldre skjermkort drivere? Noen opptateringer på spillene i det siste?

Hoikka · 8. september 2011

Har ikke prøvd eldre drivere, spillet oppdateres automatisk hele tiden. Skal prøve en eldre driver etter helga. Tusen takk for hjelpen så langt

Endret 8. september 2011 av Hoikka

Logg inn

Problemer med bluescreen og får ikke installert WinDbg

Anbefalte innlegg

Hoikka

Lenke til kommentar

Videoannonse

Hoikka

Lenke til kommentar

Sceptic

Lenke til kommentar

Hoikka

Lenke til kommentar

The Crusher

Lenke til kommentar

Hoikka

Lenke til kommentar

Hoikka

Lenke til kommentar

The Crusher

Lenke til kommentar

Hoikka

Lenke til kommentar

Hoikka

Lenke til kommentar

The Crusher

Lenke til kommentar

Hoikka

Lenke til kommentar

The Crusher

Lenke til kommentar

Hoikka

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Opprett konto

Logg inn

Hvem er aktive 0 medlemmer