Kernel BSODs

Hi,

My system crashes frequently.
For example during an encode of Premiere Pro. Or sometimes the screens are just blacked out, only can be resolved with a hard reset.

Any idea?

Thanks,
Bart

• DESKTOP-KP5FM0K-di_08-03-2016__81444,68.zip (1.26 MB, 7 views)

There are various different BSODs. Even Adobe Premier is failing with different bugcheck codes.

But one thing is common there, stack overflow.

Code:

PROCESS_NAME:  Adobe Premiere  EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

Code:

PROCESS_NAME:  Adobe Premiere  STACKUSAGE_FUNCTION: The function at address 0xFFFFF800CEF676BC was blamed for the stack overflow. It is using 9608 bytes of stack total in 24 instances (likely recursion).

And it is not possible to determine what is causing this from the given data. It may be some hardware component, or may be some drivers acting rogue.

Let us first check for the hardware.

Test your RAM modules for possible errors.

MemTest86+ - Test RAM

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in windowssh blog - Windows 10 blog

Stress test the CPU.

Prime95 - Stress Test Your CPU

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Stress test the Graphics Card using Furmark.

FurMark - GPU Stress Test

Take a screenshotof the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Let us know the results.
____________________________________________________________________________________________________ ___

Code:

BugCheck 1E, {ffffffffc0000005, fffff8001db3869c, 0, ffffffffffffffff}  Probably caused by : ntkrnlmp.exe ( nt!BcpCursor <PERF> (nt+0x33569c)+0 )  Followup:     MachineOwner ---

Code:

BugCheck 139, {3, ffffd00025506840, ffffd00025506798, 0}  Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )  Followup:     MachineOwner ---

Code:

BugCheck 7F, {8, fffff800d0b51e70, ffffd00021847ef0, fffff800cef67590}  Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+13c )  Followup:     MachineOwner ---

Code:

BugCheck 50, {fffff921465e7040, 0, fffff9601ada9ee9, 2}  *** WARNING: Unable to verify checksum for win32kfull.sys *** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32kfull.sys -   Could not read faulting driver name *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption  Followup:     memory_corruption ---