New system testing

[Papa_D]

Hi everyone. I wasnt really sure where to put this thread, so I went with the lounge. As you know I am running a new system i built myself. I am seeing things that I have never seen before, they maybe part of WIN 10 as this is first time I have run WIN 10. Sometimes, the computer will “blue screen” and say something like Windows has encountered an error and must restart. For more information search system_service_exception_fltmgr.sys or something similiar, it happens kinda fast and I never seem to be able to write down the entire “path”.

I guess my question is, what is the method for trouble shooting the whole system? Do I need to do “burn ins” to stabilize things? I still experience graphic problems from time to time also, but that may just be AMD and thier AWESOME drivers…at least it isnt just shutting off. I am completely in the dark here, I feel like building the rig myself got me alot more hardware bang for the buck, but obviously leaves me with no support. I had no issues with last build, which is why I felt so confident building another. I dont know what I could have done wrong to cause problems. Perhaps I installed software that came with hardware that isnt needed, I just thought since it came with it it must have to be installed. For example, this mother board comes with Killer Networking, but my guess is I dont have to use thier software or drivers, I can prolly connct just fine with standard windows drivers. There is something in that software about adding my download and upload speeds so it can throttl my network, I think, but it only seemed to slow it down, so I set them back to 1000 each. Now I am wondering if I should just remove it. I kept finding errors in event viewer related to engine tune, which came with software suite so I just uninstalled it. I am not sure what I actually need and what is just fluff. I will continue to look up errors and try to figure this out, but any guidance is appreciated.

THanks for reading, talk to y’all soon!

Papa D

[Papa_D]

foreign to me, but I am goggling it…

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

C:\Windows\system32>

[Papa_D]

The CBS log is too large to upload…

[Papa_D]

Here is a MTB file, if its any help…

[jmarket]

Hi again Papa D,

You seem to have the bad end of luck don’t ya? Just kidding lol

First and foremost, please enable dumping of files as we previously discussed in your last thread That way the DMP files can be uploaded and reviewed Disable automatic reboot when the BSOD occurs and enable dumping of minidumps. You can do this by doing the following:

1.) Open Settings and in the search box, put advanced system settings.

2.) Click View advanced system settings.

3.) In Startup and Recovery, click Settings.

4.) Uncheck Automatic restart and click OK.

The exact stop message is needed to ensure the correct diagnosis

[Papa_D]

Hi again Papa D,

You seem to have the bad end of luck don’t ya? Just kidding lol

First and foremost, please enable dumping of files as we previously discussed in your last thread That way the DMP files can be uploaded and reviewed Disable automatic reboot when the BSOD occurs and enable dumping of minidumps. You can do this by doing the following:

1.) Open Settings and in the search box, put advanced system settings.

2.) Click View advanced system settings.

3.) In Startup and Recovery, click Settings.

4.) Uncheck Automatic restart and click OK.

The exact stop message is needed to ensure the correct diagnosis

I have done this and next time I get a problem, which probably wont be long, I will post the dmp file, THank you for helping!

[Papa_D]

I used the search box to search for MEMORY.DMP buy nothing comes up…???

[jmarket]

Hi again

Try looking for minidumps, which are located at C:/Windows/Minidump/. A full dump will be found at C:/Windows/MEMORY.dmp.

[Papa_D]

Im not finding those files. I googled it and found that they are in c:/Windows/LiveKernalReports/watchdog. I can not view them but wil lpost most recent in hopes that someone can tell me what is happening.

[Malnutrition]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_APPLICATION_BLOCKED (142)
Application has been blocked from accessing Graphics hardware.
(This code can never be used for real bugcheck).
Arguments:
Arg1: ffffe001e2b0e4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8007b85ed48, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 00000000000020ac, Id of the process being blocked from accessing the GPU.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
atikmpag+ed48
fffff800`7b85ed48 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_APPLICATION_BLOCKED

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


BUGCHECK_STR:  0x142

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT: 
ffffd001`da420480 fffff800`7af44b2c : ffffe001`e2b0e4c0 ffffd001`da420620 ffffe001`e2b0e4c0 ffffe001`dc7505c0 : watchdog!WdDbgReportRecreate+0x104
ffffd001`da4204d0 fffff800`7c8c1909 : 00000000`00000000 00000000`00000000 ffffe001`da729000 ffffe001`da729000 : dxgkrnl!TdrUpdateDbgReport+0xec
ffffd001`da420520 fffff800`7c92a9d8 : ffffe001`da729000 00000000`00000000 00000000`00000001 ffffe001`da729001 : dxgmms2!VidSchiResetEngine+0x675
ffffd001`da420800 fffff800`7c8da7d0 : ffffe001`da72b000 00000000`00000000 00000000`00000000 ffffe001`da729000 : dxgmms2!VidSchiResetEngines+0x84
ffffd001`da420840 fffff800`7c8da576 : 00000000`00000002 00000000`003736d5 00000000`003bb94e 1eb68ad3`1be67c80 : dxgmms2!VidSchiCheckHwProgress+0x1c0
ffffd001`da4208b0 fffff800`7c8ab324 : 00000000`00000002 ffffe001`e18d4010 00000000`c0000000 ffffe001`da729000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x2e6
ffffd001`da420980 fffff800`7c90a75d : ffffe001`d9b51010 ffffd001`da420ad0 ffffe001`d9b51000 ffffe001`da72b000 : dxgmms2!VidSchiScheduleCommandToRun+0x5a4
ffffd001`da420a80 fffff800`7c90a720 : ffffe001`da72b500 ffffe001`da72b000 00000000`00000080 ffffe001`d02e9700 : dxgmms2!VidSchiRun_PriorityTable+0x2d
ffffd001`da420ad0 fffff802`8f2c8a45 : 0000000d`bd9bbfff fffff802`8f3c99af 00000000`00010023 00000000`025cfc6a : dxgmms2!VidSchiWorkerThread+0x80
ffffd001`da420b10 fffff802`8f3c9ae6 : fffff802`8f59e180 ffffe001`d9ae5840 fffff802`8f2c8a04 00000000`0007336f : nt!PspSystemThreadStartup+0x41
ffffd001`da420b60 00000000`00000000 : ffffd001`da421000 ffffd001`da41a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+ed48
fffff800`7b85ed48 ??              ???

SYMBOL_NAME:  atikmpag+ed48

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57ac347c

FAILURE_BUCKET_ID:  X64_0x142_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x142_IMAGE_atikmpag.sys

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

*******************************************************************************
*                                                                             *
*                        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 real bugcheck).
Arguments:
Arg1: ffffe001df0d0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8007b85ed48, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 00000000000002c0, Optional internal context dependent data.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
atikmpag+ed48
fffff800`7b85ed48 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_ENGINE_TIMEOUT

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


BUGCHECK_STR:  0x141

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT: 
ffffd001`da420480 fffff800`7af44b2c : ffffe001`df0d0010 ffffd001`da420620 ffffe001`df0d0010 ffffe001`db2fa8f0 : watchdog!WdDbgReportRecreate+0x104
ffffd001`da4204d0 fffff800`7c8c1909 : 00000000`00000000 00000000`00000000 ffffe001`df0d0010 ffffe001`da729000 : dxgkrnl!TdrUpdateDbgReport+0xec
ffffd001`da420520 fffff800`7c92a9d8 : ffffe001`da729000 00000000`00000000 00000000`00000001 ffffe001`da729001 : dxgmms2!VidSchiResetEngine+0x675
ffffd001`da420800 fffff800`7c8da7d0 : ffffe001`da72b000 00000000`00000000 00000000`00000000 ffffe001`da729000 : dxgmms2!VidSchiResetEngines+0x84
ffffd001`da420840 fffff800`7c8da576 : 00000000`00000002 00000000`0004adc6 00000000`003bb94e 029aab80`e37bc580 : dxgmms2!VidSchiCheckHwProgress+0x1c0
ffffd001`da4208b0 fffff800`7c8ab324 : 00000000`00000002 ffffe001`dd4a5c40 00000000`c0000000 ffffe001`da729000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x2e6
ffffd001`da420980 fffff800`7c90a75d : ffffe001`de421c40 ffffd001`da420ad0 ffffe001`de421c00 ffffe001`da72b000 : dxgmms2!VidSchiScheduleCommandToRun+0x5a4
ffffd001`da420a80 fffff800`7c90a720 : ffffe001`da72b500 ffffe001`da72b000 00000000`00000080 ffffe001`d02e9700 : dxgmms2!VidSchiRun_PriorityTable+0x2d
ffffd001`da420ad0 fffff802`8f2c8a45 : 0000000d`bd9bbfff fffff802`8f3c99af 00000000`00010023 00000000`025cfc6a : dxgmms2!VidSchiWorkerThread+0x80
ffffd001`da420b10 fffff802`8f3c9ae6 : fffff802`8f59e180 ffffe001`d9ae5840 fffff802`8f2c8a04 00000000`0007336f : nt!PspSystemThreadStartup+0x41
ffffd001`da420b60 00000000`00000000 : ffffd001`da421000 ffffd001`da41a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+ed48
fffff800`7b85ed48 ??              ???

SYMBOL_NAME:  atikmpag+ed48

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57ac347c

FAILURE_BUCKET_ID:  X64_0x141_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x141_IMAGE_atikmpag.sys

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

[Malnutrition]

Your graphics card driver is to blame for the crashes, clean install it with DDU

Get the latest driver from here.

[Papa_D]

sorry, I havent been around, got lot of stuff going on. THank you for the driver advice. I have done the DDU in safe mode and continued to experience problems. I took it to a shop (oh that was hard) thier tech seems to think its bad cards. New cards came yesterday. I should have machine back soon, though I am anticipating it will have the same problem. I don think it was the cards, but we shall see…

Personally, from readin gon web, I think its another case of bad AMD drivers. I almost want to install win 7, I suspect I wouldnt have problem…But I am a rookie, so thats my two cents!

[jmarket]

sorry, I havent been around, got lot of stuff going on.

No worries We’re always here

Let us know if you continue experiencing issues when you get it back

[Malnutrition]

I almost want to install win 7, I suspect I wouldnt have problem.

Windows 7 is certainly a LOT more stable.

[Rustys]

Personally, from readin gon web, I think its another case of bad AMD drivers. I almost want to install win 7, I suspect I wouldnt have problem…But I am a rookie, so thats my two cents!

You could install Windows 7 and like Malnutrition said it is more stable. Just to add if you also wanted to if the HDD had enough space you could dual boot the system if seven works and put ten on and see if we can help working out the bugs. That way if Ten never works to you satisfaction you have Seven to fall back on.