Windows 10: BSOD. Please help me in finding the issue.

here is the bugcheck analysis/ this happened while i was gaming


******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KMODE_EXCEPTION_NOT_HANDLED 1eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff80780208c89, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: 000000176580af7a, Parameter 1 of the exceptionDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1468 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on SHIFTMEISTER Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 9936 Key : Analysis.Memory.CommitPeak.Mb Value: 77 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: 1eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff80780208c89BUGCHECK_P3: 0BUGCHECK_P4: 176580af7aREAD_ADDRESS: fffff80780afb390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80780a0f330: Unable to get Flags value from nt!KdVersionBlockfffff80780a0f330: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 000000176580af7a EXCEPTION_PARAMETER2: 000000176580af7aBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemTRAP_FRAME: ffff800000000000 -- .trap 0xffff800000000000Unable to read trap frame at ffff8000`00000000STACK_TEXT: ffffcc8c`9224e418 fffff807`802f4cfe : 00000000`0000001e ffffffff`c0000005 fffff807`80208c89 00000000`00000000 : nt!KeBugCheckExffffcc8c`9224e420 fffff807`801fe93f : fffff807`802f4cdc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22ffffcc8c`9224e460 fffff807`8012bf97 : ffffcc8c`9224e9d0 00000000`00000000 ffffcc8c`9224fb60 fffff807`801f95a4 : nt!RtlpExecuteHandlerForException+0xfffffcc8c`9224e490 fffff807`8012ab86 : ffffcc8c`9224f3a8 ffffcc8c`9224f0e0 ffffcc8c`9224f3a8 00000000`00000003 : nt!RtlDispatchException+0x297ffffcc8c`9224ebb0 fffff807`80207bac : 00000000`00001000 ffffcc8c`9224f450 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x186ffffcc8c`9224f270 fffff807`80203d43 : 00000000`00000000 fffff807`801fbf5b 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12cffffcc8c`9224f450 fffff807`80208c89 : fffff807`80071b93 ffffa788`41e92368 00000000`00000000 00000017`64716da8 : nt!KiPageFault+0x443ffffcc8c`9224f5e8 fffff807`80071b93 : ffffa788`41e92368 00000000`00000000 00000017`64716da8 00000000`00000000 : nt!memset+0x9ffffcc8c`9224f5f0 fffff807`80070154 : 00000000`00000000 00001fa0`00000200 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x18c3ffffcc8c`9224f9f0 fffff807`801f95a4 : ffffffff`00000000 ffffcf80`f404b440 ffffa788`4cf53080 00000000`000006f6 : nt!PoIdle+0x374ffffcc8c`9224fb60 00000000`00000000 : ffffcc8c`92250000 ffffcc8c`92249000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54SYMBOL_NAME: nt!HvlpVtlCallExceptionHandler+22MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.804STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 22FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!HvlpVtlCallExceptionHandlerOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {54c01c2d-844b-456b-978f-b9c94e11c051}Followup: MachineOwner---------

:)

 

BSOD Help Needed.

Making it through 24 hours of Prime means you're most likely ok. I would do an hour of IntelBurnTest and a complete pass of MemTest x86 just to be on the safe side (Prime doesn't stress RAM as much as memtest). If you still have BSODs then you're most likely not chasing a hardware issue. At that point I would suggest looking into some Windows 7 forums and finding their BSOD-specific section and uploading your dump file for their gurus to look at. They could help you far more than I, I'm afraid. TPU may have such a board.

But hopefully you're in the clear. *Rockout :rockout:

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast: