WinDpg

I need help knowing whats wrong with my pc it keeps restarting and i got this in WinDpg on my dump file. Anyone plz help

Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.



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

Kernel Bitmap Dump File: Full address space is available


Symbol search path is: srv*

Executable search path is: 

Windows 10 Kernel Version 18362 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff807`16a00000 PsLoadedModuleList = 0xfffff807`16e48190

Debug session time: Tue Feb 18 13:04:36.821 2020 (UTC - 8:00)

System Uptime: 0 days 0:05:39.513

Loading Kernel Symbols

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

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

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

Loading User Symbols


Loading unloaded module list

......

For analysis of this file, run !analyze -v

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

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception


Debugging Details:

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



KEY_VALUES_STRING: 1



PROCESSES_ANALYSIS: 1


SERVICE_ANALYSIS: 1


STACKHASH_ANALYSIS: 1


TIMELINE_ANALYSIS: 1



DUMP_CLASS: 1


DUMP_QUALIFIER: 402


BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202


SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.


SYSTEM_PRODUCT_NAME:  B450 AORUS ELITE


SYSTEM_SKU:  Default string


SYSTEM_VERSION:  Default string


BIOS_VENDOR:  American Megatrends Inc.


BIOS_VERSION:  F51


BIOS_DATE:  12/18/2019


BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.


BASEBOARD_PRODUCT:  B450 AORUS ELITE


BASEBOARD_VERSION:  x.x


DUMP_TYPE:  0


BUGCHECK_P1: ffffffffc0000005


BUGCHECK_P2: fffff80716a4b007


BUGCHECK_P3: 0


BUGCHECK_P4: ffffffffffffffff


READ_ADDRESS:  ffffffffffffffff 


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.


FAULTING_IP: 

nt!KiTryUnwaitThread+187

fffff807`16a4b007 483901          cmp     qword ptr [rcx],rax


EXCEPTION_PARAMETER2:  ffffffffffffffff


BUGCHECK_STR:  0x1E_c0000005_R


CPU_COUNT: c


CPU_MHZ: d42


CPU_VENDOR:  AuthenticAMD


CPU_FAMILY: 17


CPU_MODEL: 8


CPU_STEPPING: 2


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  System


CURRENT_IRQL:  2


ANALYSIS_SESSION_HOST:  DESKTOP-OQI31UU


ANALYSIS_SESSION_TIME:  02-18-2020 15:54:26.0173


ANALYSIS_VERSION: 10.0.18362.1 amd64fre


LAST_CONTROL_TRANSFER:  from fffff80716ca663e to fffff80716bc1510


STACK_TEXT:  

ffff808e`79a36648 fffff807`16ca663e : 00000000`0000001e ffffffff`c0000005 fffff807`16a4b007 00000000`00000000 : nt!KeBugCheckEx

ffff808e`79a36650 fffff807`16bca342 : fffff807`16f11000 fffff807`16a00000 0005e530`00ab6000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22

ffff808e`79a36690 fffff807`16ac2f15 : 00000000`00000000 00000000`00000000 ffff808e`79a36c00 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12

ffff808e`79a366c0 fffff807`16ac74ae : ffff808e`79a375f8 ffff808e`79a37340 ffff808e`79a375f8 ffff8501`fca40180 : nt!RtlDispatchException+0x4a5

ffff808e`79a36e10 fffff807`16bd351d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e

ffff808e`79a374c0 fffff807`16bcf2a2 : fffff807`16a00000 00000000`00000000 ffff808e`79a37748 fffff807`16960b2a : nt!KiExceptionDispatch+0x11d

ffff808e`79a376a0 fffff807`16a4b007 : ffff2889`ffffffff ffffffff`267d7000 00000007`00000000 00000000`00000003 : nt!KiGeneralProtectionFault+0x322

ffff808e`79a37830 fffff807`16a6be16 : ffffda04`2477b188 00000000`00000000 ffffda04`2477b250 ffffda04`2477b180 : nt!KiTryUnwaitThread+0x187

ffff808e`79a37890 fffff807`16a6b9f2 : ffffda04`2477b180 00000000`ca5d37bd 00000001`00000004 ffffda04`1e88b010 : nt!KiTimerWaitTest+0x1b6

ffff808e`79a37940 fffff807`16a6a7e9 : 00000000`00000000 00000000`00989680 00000000`00003297 00000000`000000af : nt!KiProcessExpiredTimerList+0xd2

ffff808e`79a37a30 fffff807`16bc5054 : ffffffff`00000000 ffff8501`fc8f9180 ffff8501`fc90a340 ffffda04`245f7080 : nt!KiRetireDpcList+0x4e9

ffff808e`79a37c60 00000000`00000000 : ffff808e`79a38000 ffff808e`79a32000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84



THREAD_SHA1_HASH_MOD_FUNC:  8836b4b9bc26ee65351ed3452fce2c016d4846c9


THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a0580901ff41c49a9bd544c250bcc7bec78abeff


THREAD_SHA1_HASH_MOD:  dc844b1b94baa204d070855e43bbbd27eee98b94


FOLLOWUP_IP: 

nt!KiTryUnwaitThread+187

fffff807`16a4b007 483901          cmp     qword ptr [rcx],rax


FAULT_INSTR_CODE:  f013948


SYMBOL_STACK_INDEX:  7


SYMBOL_NAME:  nt!KiTryUnwaitThread+187


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


IMAGE_NAME:  ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP:  4269a790


STACK_COMMAND:  .thread ; .cxr ; kb


BUCKET_ID_FUNC_OFFSET:  187


FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!KiTryUnwaitThread


BUCKET_ID:  0x1E_c0000005_R_nt!KiTryUnwaitThread


PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_nt!KiTryUnwaitThread


TARGET_TIME:  2020-02-18T21:04:36.000Z


OSBUILD:  18362


OSSERVICEPACK:  0


SERVICEPACK_NUMBER: 0


OS_REVISION: 0


SUITE_MASK:  784


PRODUCT_TYPE:  1


OSPLATFORM_TYPE:  x64


OSNAME:  Windows 10


OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal


OS_LOCALE:  


USER_LCID:  0


OSBUILD_TIMESTAMP:  2005-04-22 18:40:32


BUILDDATESTAMP_STR:  190318-1202


BUILDLAB_STR:  19h1_release


BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202


ANALYSIS_SESSION_ELAPSED_TIME:  187a


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_nt!kitryunwaitthread


FAILURE_ID_HASH:  {4abda1ba-718c-fcea-57ff-6e531adb2ce2}


Followup:     MachineOwner


 

Question Info


Last updated May 21, 2020 Views 65 Applies to:
Answer
Answer
Hi Mark, I am Rob, an independent and a 14 time and dual award MVP specializing in Windows troubleshooting and Bluescreen analysis. Please remember as independents we are not responsible for the development of Windows or the computer hardware and drivers. If you will work with me I will be here to help until the issue is resolved.

The BugCheck is 1E with probably cause ntkrnlmp.exe - which is a Windows component which means something else drove it into Fault. If you post the minidumps for analysis I might the able to glean more information from it by performing a detailed analysis. Of course, sometimes that helps and sometimes not.

Below are methods to post the DMP files as well as troublshooting steps.

-------

Troubleshoot blue screen errors <-- read this link
http://windows.microsoft.com/en-us/windows-10/t...

We can analyze the minidumps if you make them available from the OneDrive
or other file sharing sites (such as MediaFire). If you have problems uploading
the minidumps copy them to the Desktop or the Documents folder and upload
them from there.

One-Drive - Share files and folders and change permissions
http://windows.microsoft.com/en-us/onedrive/sha...

Upload photos and files
http://windows.microsoft.com/en-us/onedrive/add...

Zip or upload the contents of C:\Windows\minidump

Use OneDrive to upload collected files
http://social.technet.microsoft.com/Forums/en-U...

=======================================================

Be sure to check with Gigabyte Support and all the major device makers' supports for known issues (this often saves a lot of frustration). Also, post in their forums for the ones that offer a forum.

Look for updates to BIOS, chipset drivers, and all major on-board and separate device drivers.

Troubleshoot blue screen errors <-- read this link
http://windows.microsoft.com/en-us/windows-10/t...

BCCode: 1E 0x0000001E

Remove ALL power and reseat all the cards, memory, and cables (both ends when
possible) - actually remove and replace - do not just snug. Those are for a PC and about all that can be done for a laptop is reseat the memory and clear the vents. Make sure the BIOS, low level chipset drivers, and major device drivers are all up to date by checking manually at the makers' sites.

BCCode: 1E 0x0000001E

BCCode: 1E 0x0000001E <-- read this link
http://www.faultwire.com/solutions-fatal_error/...*1045.html

==================================================

This utility makes it easy to see which versions are loaded :

Run DriverView - set VIEW to Hide Microsoft drivers - update those without
Dump in their names (and update BIOS and chipset drivers).

DriverView - Free - utility displays the list of all device drivers currently loaded
on your system. For each driver in the list, additional useful information is
displayed: load address of the driver, description, version, product name,
company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the
most current. Right Click the Start Button - Device Manager - Display Adapter -
write down the make and complete model of your video adapter - double click
- Driver's tab - write down the version info. Now click UPdate Driver (this may not
do anything as MS is far behind certifying drivers) - then Right Click - Uninstall -
REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard
if 3rd party with their own software and drivers and any other major device drivers
you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and
then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their
latest versions. (Look for BIOS, Chipset, and software updates at System Maker's
site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -
REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are
installing actually shows up. This is because some drivers rollback before the
latest is installed (sound drivers particularly do this) so install a driver - reboot
- check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER -
check manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht...

====================================================

Memory tests do not catch all errors such as mismatched memory (possible even
for sticks that appear to be identical) and when faster memory is placed in the system behind slower memory. So it is best to also swap sticks in and out to check for those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so. <-- best method
www.memtest.org

MemTestX86 - Test RAM With
http://www.tenforums.com/tutorials/14201-memtes...

For the Windows Memory Diagnostic Tool.

Type in Cortana's search box -> Windows Memory Diagnostics
........find at top of the list - click it. in Windows 8/8.1/10 the name is "Windows Memory Diagnostic".

================================================

After doing ALL the updates you can, and if the issue continues, then run
Driver Verifier.

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10
are essentially the same).
http://www.winvistaclub.com/t79.html

Using Driver Verifier
https://msdn.microsoft.com/en-us/library/window...

WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

If Driver Verifier creates a minidump upload it and post the link here so we can
analyze it.

Here to help,

Rob

------
Standard Disclaimer: Those may be non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Please let us know the results and if you need further assistance. Feedback definitely helps us help all.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Answer
Answer
Well that certainly sounds like hardware. Could be the GPU, though motherboard, PSU, and other hardware could be in play. Be sure all the connections are still tight (of course remove all power first).

Rob

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.