Windows 10: Bsod

I Opened the dmp file and this is what i get can someone help me to figure out what it wrong?




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


Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20190101-1600.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`42817000 PsLoadedModuleList = 0xfffff800`42bc5150
Debug session time: Tue Jan 1 16:00:58.394 2019 (UTC - 5:00)
System Uptime: 0 days 0:25:48.139
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
watchdog!WdDbgReportRecreate+0x10c:
fffff80b`f42ad66c 488b4f38 mov rcx,qword ptr [rdi+38h] ds:002b:ffffb904`3acc9638=????????????????
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffb90435f671b0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80bf66ec7e4, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000001044, Optional internal context dependent data.

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

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17134.472 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: ffffb90435f671b0

BUGCHECK_P2: fffff80bf66ec7e4

BUGCHECK_P3: 0

BUGCHECK_P4: 1044

FAULTING_IP:
nvlddmkm+19c7e4
fffff80b`f66ec7e4 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_ENGINE_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


CPU_COUNT: c

CPU_MHZ: ce3

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

BUGCHECK_STR: 0x141

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-AM87KUU

ANALYSIS_SESSION_TIME: 01-08-2019 23:21:31.0426

ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

STACK_TEXT:
ffffab0f`7c853640 fffff80b`f417cd37 : ffffb904`35f671b0 ffffb904`35f671b0 ffffab0f`7c8537e0 ffffb904`3acc9600 : watchdog!WdDbgReportRecreate+0x10c
ffffab0f`7c853690 fffff80b`f566c665 : ffffb904`00000000 ffffb904`369e8570 ffffb904`35f671b0 ffffb904`38d21000 : dxgkrnl!TdrUpdateDbgReport+0xe7
ffffab0f`7c8536e0 fffff80b`f56fc98a : ffffb904`38d21000 00000000`00000002 00000000`00000001 ffffb904`38d1d001 : dxgmms2!VidSchiResetEngine+0x73d
ffffab0f`7c8539d0 fffff80b`f56d9f68 : ffffb904`38d21000 00000000`00000001 00000000`00000000 ffffb904`38d1d558 : dxgmms2!VidSchiResetEngines+0xaa
ffffab0f`7c853a20 fffff80b`f564a412 : ffffb904`3e0dc010 00000000`00018304 00000000`003128dd 00000000`00000102 : dxgmms2!VidSchiCheckHwProgress+0x23498
ffffab0f`7c853a90 fffff80b`f56c0e90 : ffffb904`3d714a00 ffffb904`3e0c8a00 ffffb904`3d714a70 ffffb904`3e0c8ac0 : dxgmms2!VidSchiScheduleCommandToRun+0x52
ffffab0f`7c853b80 fffff80b`f56c0e4e : ffffb904`38d1d500 fffff80b`f56c0dc0 ffffb904`38d1d000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x30
ffffab0f`7c853bd0 fffff800`429472d7 : ffffb904`38721700 fffff80b`f56c0dc0 cc1b4db1`ed844082 448940c1`f799ad6b : dxgmms2!VidSchiWorkerThread+0x8e
ffffab0f`7c853c10 fffff800`429c8516 : fffff800`416b7180 ffffb904`38721700 fffff800`42947290 83ab5aee`aa536fc3 : nt!PspSystemThreadStartup+0x47
ffffab0f`7c853c60 00000000`00000000 : ffffab0f`7c854000 ffffab0f`7c84e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: e1a26c6676c55424f4bd297d10ebd5e22b220be3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 30930449b0b83785023e4c834ef329037857d187

THREAD_SHA1_HASH_MOD: 37ae093ee944c9a8b7ed616b649a8553fd3125df

FOLLOWUP_IP:
nvlddmkm+19c7e4
fffff80b`f66ec7e4 ?? ???

SYMBOL_NAME: nvlddmkm+19c7e4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5c0f578b

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys

BUCKET_ID: LKD_0x141_IMAGE_nvlddmkm.sys

PRIMARY_PROBLEM_CLASS: LKD_0x141_IMAGE_nvlddmkm.sys

TARGET_TIME: 2019-01-01T21:00:58.000Z

OSBUILD: 17134

OSSERVICEPACK: 472

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: 2018-12-14 01:53:05

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17134.472

ANALYSIS_SESSION_ELAPSED_TIME: 717

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:lkd_0x141_image_nvlddmkm.sys

FAILURE_ID_HASH: {341dd0b3-9ebd-47a8-9de8-23f4b00fabbc}

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

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.