Er mit grafikkort brændt sammen?

Brugeravatar
vandmelon
Indlæg: 204
Tilmeldt: 6. apr 2018, 21:21
Kort karma: 11
Likede indlæg: 131

Er mit grafikkort brændt sammen?

Indlægaf vandmelon » 28. maj 2020, 22:40

Hej, min pc vil ikke vise noget på skærmen og jeg skal genstarte flere gange før den viser noget. Ingen striber på skærmen eller noget. Bare sort skærm når den ikke kører, men når den kører er alt perf. Det er en stationær. Intet nyt hardware installeret eller sat i. Heller ikke over usb. Ingen ny windows updates installeret. Memory test lavet, ingen fejl. Dvs det er nok ikke RAM. Læsning af 2 dump filer her gennem WinDbg:

Hvis en af jer har et cirka bud hvad det kan være, så hører jeg gerne :))

1)

Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\052020-17456-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e8ec90
Debug session time: Mon May 18 18:33:45.507 2020 (UTC + 2:00)
System Uptime: 0 days 0:51:28.927
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002cf7155

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

fffff80002e370e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff80002ef2300

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on COMPUTER

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 1

Key : Analysis.Memory.CommitPeak.Mb
Value: 63

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: 80050031

BUGCHECK_P3: 6f8

BUGCHECK_P4: fffff80002cf7155

TRAP_FRAME: fffff80000ba6e70 -- (.trap 0xfffff80000ba6e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8006795710
rdx=0000000000000090 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cf7155 rsp=ffffffffffffffd1 rbp=0000000000000000
r8=fffffa80069830e8 r9=0000000000000000 r10=fffffffffffffffe
r11=fffffa8006b5e750 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiSystemServiceExit+0x1fa:
fffff800`02cf7155 c3 ret
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: iexplore.exe

BAD_STACK_POINTER: ffffffffffffffd1

UNALIGNED_STACK_POINTER: ffffffffffffffd1

STACK_TEXT:
fffff800`00ba6d28 fffff800`02cf72e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba6d30 fffff800`02cf3d51 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba6e70 fffff800`02cf7155 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x291
ffffffff`ffffffd1 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x1fa


SYMBOL_NAME: nt!KiDoubleFaultAbort+291

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 6.1.7601.24540

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: X64_0x7f_8_STACKPTR_ERROR_nt!KiDoubleFaultAbort+291

OS_VERSION: 7.1.7601.24540

BUILDLAB_STR: win7sp1_ldr_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {792688ce-3454-183e-76d3-e5441b016c29}

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

2) Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\041520-16473-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24540.amd64fre.win7sp1_ldr_escrow.191127-1706
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e96c90
Debug session time: Wed Apr 15 16:31:44.868 2020 (UTC + 2:00)
System Uptime: 0 days 0:06:04.288
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: fffffa8007f361a0, Device extension pointer of the host controller
Arg3: 0000000010de077b, PCI Vendor,Product id for the controller
Arg4: fffffa8009878838, Pointer to Endpoint data structure

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

*** WARNING: Unable to verify timestamp for sptd.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
fffff80002e3f0e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff80002efa300

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 1

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on COMPUTER

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 8

Key : Analysis.Memory.CommitPeak.Mb
Value: 67

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: fe

BUGCHECK_P1: 5

BUGCHECK_P2: fffffa8007f361a0

BUGCHECK_P3: 10de077b

BUGCHECK_P4: fffffa8009878838

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff880`0311ba58 fffff880`040f22e2 : 00000000`000000fe 00000000`00000005 fffffa80`07f361a0 00000000`10de077b : nt!KeBugCheckEx
fffff880`0311ba60 fffff880`01befa45 : 00000000`f000e2c2 fffffa80`098785f0 00000000`00000000 fffff880`0380f000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`0311baa0 fffff880`01bf1737 : fffffa80`09878838 fffffa80`098785f0 00000000`00000000 fffffa80`07f361a0 : usbohci!OHCI_PollAsyncEndpoint+0x99
fffff880`0311bb00 fffff880`040c5e6b : 00000000`00000002 fffffa80`098785f0 fffffa80`07f361a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
fffff880`0311bb30 fffff880`040cabc1 : 00000000`00000040 00000000`00000004 fffffa80`098785f0 fffff880`01bf066f : USBPORT!MPf_PollEndpoint+0x9b
fffff880`0311bb60 fffff880`040d6303 : fffffa80`07f361a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`0311bbc0 fffff880`040c6f69 : fffffa80`07f36050 00000000`00000000 fffffa80`07f36a02 fffffa80`07f36a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`0311bc20 fffff880`01096c10 : fffffa80`07d77000 fffff880`040c6d90 fffffa80`07f36a00 fffff880`0311bcc8 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`0311bc50 fffffa80`07d77000 : fffff880`040c6d90 fffffa80`07f36a00 fffff880`0311bcc8 00000002`1fc37d09 : sptd+0x1dc10
fffff880`0311bc58 fffff880`040c6d8f : fffffa80`07f36a00 fffff880`0311bcc8 00000002`1fc37d09 fffffa80`00000000 : 0xfffffa80`07d77000
fffff880`0311bc60 fffffa80`07f36a00 : fffff880`0311bcc8 00000002`1fc37d09 fffffa80`00000000 43f00000`00000000 : USBPORT!USBPORT_Xdpc_End+0x26f
fffff880`0311bc68 fffff880`0311bcc8 : 00000002`1fc37d09 fffffa80`00000000 43f00000`00000000 fffff880`009fa000 : 0xfffffa80`07f36a00
fffff880`0311bc70 00000002`1fc37d09 : fffffa80`00000000 43f00000`00000000 fffff880`009fa000 00000000`00000000 : 0xfffff880`0311bcc8
fffff880`0311bc78 fffffa80`00000000 : 43f00000`00000000 fffff880`009fa000 00000000`00000000 fffffa80`07d7821d : 0x00000002`1fc37d09
fffff880`0311bc80 43f00000`00000000 : fffff880`009fa000 00000000`00000000 fffffa80`07d7821d fffff880`009e8180 : 0xfffffa80`00000000
fffff880`0311bc88 fffff880`009fa000 : 00000000`00000000 fffffa80`07d7821d fffff880`009e8180 fffffa80`07f36a18 : 0x43f00000`00000000
fffff880`0311bc90 00000000`00000000 : fffffa80`07d7821d fffff880`009e8180 fffffa80`07f36a18 fffffa80`07f36a30 : 0xfffff880`009fa000


SYMBOL_NAME: usbohci!OHCI_PollAsyncEndpoint+99

MODULE_NAME: usbohci

IMAGE_NAME: usbohci.sys

IMAGE_VERSION: 6.1.7601.24138

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollAsyncEndpoint+99

OS_VERSION: 7.1.7601.24540

BUILDLAB_STR: win7sp1_ldr_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {b24db5d3-ddda-0586-be17-4b1ffc415f10}

Followup: MachineOwner
---------
0
✂ ✂ ✂ ----------------------------------------------------------------------------------------------------------------------------------------
Brugeravatar
Kasper
Indlæg: 202
Tilmeldt: 1. sep 2015, 21:50
Kort karma: 55
Likede indlæg: 575

Re: Er mit grafikkort brændt sammen?

Indlægaf Kasper » 2. jun 2020, 23:20

vandmelon skrev:Hej, min pc vil ikke vise noget på skærmen og jeg skal genstarte flere gange før den viser noget. Ingen striber på skærmen eller noget. Bare sort skærm når den ikke kører, men når den kører er alt perf. Det er en stationær. Intet nyt hardware installeret eller sat i. Heller ikke over usb. Ingen ny windows updates installeret. Memory test lavet, ingen fejl. Dvs det er nok ikke RAM. Læsning af 2 dump filer her gennem WinDbg:

Hvis en af jer har et cirka bud hvad det kan være, så hører jeg gerne :))


Du bliver nok nødt til at bruge udelukkelsesmetoden. Det er nok enten din Windows-installation, hardwaren i computeren eller din skærm, der er noget galt med.

Viser skærmen SLET ikke noget, de gange, hvor det ikke virker?

Hvis du har mulighed for det, så prøv evt. at teste med en anden skærm (f.eks. et tv, hvis du bruger HDMI) og/eller et andet skærmkabel. Bare for at kunne udelukke at det er skærmen eller kablet. Hvor mange skærmudgange er der på din PC? Hvis der er flere, kan du prøve at teste nogle af de andre.

Hvis du har mod på det, kan du evt. åbne kabinettet og sikre dig, at de forskellige stykker hardware sidder som de skal. Hvis du har flere ram-blokke, kan du prøve at boote kun med én af dem siddende i (og teste alle ram-blokke efter tur på den måde).

Er der nogen forskel på computerens aktivitet de gange, hvor det virker, i forhold til de gange, hvor det ikke virker? Nogle gange kan man høre/fornemme at boot-processen går i stå f.eks. via lydene og lysene fra harddisken.

Gør det en forskel hvis du trykker flere gange på F8 lige når du tænder computeren? (for at boote i "safe mode" på Windows 7, som det ser ud til, at du bruger?).

For at teste om det er din Windows-installation, der er noget galt med, kan du prøve at lave et boot-drev på et USB-stick, og boote derfra flere gange i streg - og se, om det gør en forskel:

https://www.cnet.com/how-to/creating-a- ... heres-how/
0

Tilbage til "Videnskab og teknologi"