Jump to content

My Card Keeps Crashing

MadKodaKumi
By MadKodaKumi
in Graphics Cards
 Share
Posted

I'm not really sure if I should put this in graphics cards or trouble shooting sorry if it's the wrong place but here goes 

My system keeps freezing now but before that I keep getting blue screen error 

I started using Windbg but if I'm honest I don't really know how to use it really 

please help 

 

This is what it says

  

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
WARNING: Mismatch between nt!KdDebuggerDataBlock and nt!KdVersionBlock - KernBase (Kernel Base Address)
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`1f400000 PsLoadedModuleList = 0xfffff802`2002a2b0
Debug session time: Thu Dec  1 16:31:36.426 2022 (UTC - 5:00)
System Uptime: 0 days 1:15:34.803
Page 5003400330 too large to be in the dump file.
Page fdf017ec43 too large to be in the dump file.
Page 86c2a605ec too large to be in the dump file.
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147

Image path too long, possible corrupt data.
Loading unloaded module list
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
...Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.
WARNING: .reload failed, module list may be incomplete
For analysis of this file, run !analyze -v
00007fff`20848c75 ??              ???
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff8024628c15e, The address that the exception occurred at
Arg3: ffff858c5b6e62e8, Exception Record Address
Arg4: ffff858c5b6e5b20, Context Record Address

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

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

Unable to read KTHREAD address ffffc40c85e32138
Unable to read KTHREAD address ffffc40c85e32138
Unable to read KTHREAD address ffffc40c85e32138
Page 502aadb6e6 too large to be in the dump file.
Unable to read KTHREAD address ffffc40c85e32138
Unable to read KTHREAD address ffffc40c85e32138
Unable to read KTHREAD address ffffc40c85e32138
Unable to read KTHREAD address ffffc40c85e32138
Page 30424026ce too large to be in the dump file.
Page 2007400750 too large to be in the dump file.
Page 4a002e0 too large to be in the dump file.
Unable to read KTHREAD address ffffc40c85e32138
Unable to read KTHREAD address ffffc40c85e32138

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 62

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 68

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 203

    Key  : Analysis.Init.Elapsed.mSec
    Value: 30232

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x7e

    Key  : Bugcheck.Code.Register
    Value: 0xc

    Key  : WER.CorruptModuleList
    Value: 1

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8024628c15e

BUGCHECK_P3: ffff858c5b6e62e8

BUGCHECK_P4: ffff858c5b6e5b20

EXCEPTION_RECORD:  ffff858c5b6e62e8 -- (.exr 0xffff858c5b6e62e8)
Page 502aadb6e6 too large to be in the dump file.
Cannot read Exception record @ ffff858c5b6e62e8

CONTEXT:  ffff858c5b6e5b20 -- (.cxr 0xffff858c5b6e5b20)
Page 502aadb6e5 too large to be in the dump file.
Unable to read context, HRESULT 0x80004002

STACK_TEXT:  
000000b2`972f81e0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`20848c75


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_AV

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fc259191-ef0c-6215-476f-d32e5dcaf1b7}

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

Unable to read KTHREAD address ffffc40c85e32138
WARNING: Unable to reset page directories

Link to comment
https://linustechtips.com/topic/1471394-my-card-keeps-crashing/
Share on other sites
Link to post
Share on other sites
Posted

You can try BlueScreenView and WhoCrashed to get more info on the BSOD.

 

What are your system specs?

 

 

M.S.C.E. (M.Sc. Computer Engineering), IT specialist in a hospital, 32+ years of gaming, 20+ years of computer enthusiasm, Geek, Trekkie, anime fan

  • Main PC: AMD Ryzen 7 5800X3D - EK AIO 360 D-RGB - Arctic Cooling MX-4 - Asus Prime X570-P - 4x8GB DDR4 3200 HyperX Fury CL16 - Sapphire AMD Radeon 6950XT Nitro+ - 1TB Kingston Fury Renegade - 2TB Kingston Fury Renegade - 512GB ADATA SU800 - 960GB Kingston A400 - Seasonic PX-850 850W  - custom black ATX and EPS cables - Fractal Design Define R5 Blackout - Windows 11 x64 23H2 - 3 Arctic Cooling P14 PWM PST - 5 Arctic Cooling P12 PWM PST
  • Peripherals: LG 32GK650F - Dell P2319h - Logitech G Pro X Superlight with Tiger Ice - Madlions MAD 68HE Pro - EndGame Gear MPC890 - Genius HF 1250B - Akliam PD4 - Sennheiser HD 560s - Tripowin Vivace - Simgot EM6L - Truthear Zero - QKZ x HBB - 7Hz Salnotes Zero - Logitech C270 - Behringer PS400 - BM700  - Colormunki Smile - Speedlink Torid - Jysk Stenderup - LG 24x External DVD writer - Konig smart card reader
  • Laptop: Acer E5–575G-386R 15.6" 1080p (i3 6100U + 12GB DDR4 (4GB+8GB) + GeForce 940MX + 256GB nVME) Win 10 Pro x64 22H2 - Logitech G305 + AAA Lithium battery
  • Networking: Asus TUF Gaming AX6000 - Huawei OptiXstar EG8145X6-10 - 1000/500 Mbps fiber optic Internet access
  • TV and gadgets: TCL 50EP680 50" 4K LED + Sharp HT-SB100 75W RMS soundbar - Samsung Galaxy Tab A8 10.1" - OnePlus 13 16GB/512GB - OnePlus 9 256GB - Olymous Cameda C-160 - GameBoy Color - Miyoo A30 Spruce
  • Streaming/Server/Storage PC: AMD Ryzen 5 3600 - LC-Power LC-CC-120 - MSI B450 Tomahawk Max - 2x4GB ADATA 2666 DDR4 - 120GB Kingston V300 - Toshiba DT01ACA100 1TB - Toshiba DT01ACA200 2TB - 2x WD Green 2TB - Sapphire Pulse AMD Radeon R9 380X - 550W EVGA G3 SuperNova - Chieftec Giga DF-01B - White Shark Spartan X keyboard - Roccat Kone Pure Military Desert strike - Logitech S-220 - Philips 226L
  • Livingroom PC (dad uses): AMD FX 8300 - Arctic Freezer 64 - Asus M5A97 R2.0 Evo - 2x4 GB DDR3 1833 Kingston - MSI Radeon HD 7770 1GB OC - 120GB Adata SSD - 500W Fractal Design Essence - DVD-RW - Samsung SM 2253BW - Logitech G710+ - wireless vertical mouse - MS 2.0 speakers
Link to comment
https://linustechtips.com/topic/1471394-my-card-keeps-crashing/#findComment-15682883
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Graphics Cards

×