Pc shutting down with blue screen sometimes just black screen

[Antonimuks]

Problem: Freezing/blue screen/restarting happens randomly on my Desktop PC. Sometimes it just freezes suddenly (black screen) shuts down and then restarts normally. Sometimes it restarts few times in a row. Sometimes a freezing, then a blue screen. And sometimes it don't, i mean it's first day, it did this 5 times since i reinstalled win.

When?: Sometimes it happens when I run applications. Sometimes it happens when I'm not doing anything (one chrome browser).

It doesn't always happen though. Sometimes I could run the computer 12 hours non-stop without experiencing a single freeze. 

Just now i played dying light for 3 hrs. without a hitch and got a crash later using Chrome. (black screen and pc shutting down/restarting) 

 

All parts are still with warranty and were working fine just a few days/weeks back.

 

Ryzen 2600 paired with msi b450m pro-m2 and gtx 1660 6gb, couple of DDR4 G.SKILL Aegis 8GB 3000MHz CL16, corsair 650w modular psu and that's pretty much it.

I want to make sure what part is failing or is it a system bug b4 i go for a warranty. I do suspect either a psu or a win update.

 

Maybe any of you had similar problems or know any good program tools to start checking? Planing on going full rambo tomorrow. Will upload update and dump info if it crashes after i make it spit dumps. 

[BiotechBen]

what SSD are you using and do you happen to remember what the crash codes were?

[Radium_Angel]

15 minutes ago, Antonimuks said:

Problem: Freezing/blue screen/restarting happens randomly on my Desktop PC. Sometimes it just freezes suddenly (black screen) shuts down and then restarts normally. Sometimes it restarts few times in a row. Sometimes a freezing, then a blue screen. And sometimes it don't, i mean it's first day, it did this 5 times since i reinstalled win.

When?: Sometimes it happens when I run applications. Sometimes it happens when I'm not doing anything (one chrome browser).

It doesn't always happen though. Sometimes I could run the computer 12 hours non-stop without experiencing a single freeze. 

Just now i played dying light for 3 hrs. without a hitch and got a crash later using Chrome. (black screen and pc shutting down/restarting) 

 

All parts are still with warranty and were working fine just a few days/weeks back.

 

Ryzen 2600 paired with msi b450m pro-m2 and gtx 1660 6gb, couple of DDR4 G.SKILL Aegis 8GB 3000MHz CL16, corsair 650w modular psu and that's pretty much it.

I want to make sure what part is failing or is it a system bug b4 i go for a warranty. I do suspect either a psu or a win update.

 

Maybe any of you had similar problems or know any good program tools to start checking? Planing on going full rambo tomorrow. Will upload update and dump info if it crashes after i make it spit dumps. 

If you are OCing or enabling XMP, turn that off.

Also, the BsOD, if enabled right, will record a crashdump, if yuo can post those here, I can pinpoint what's going on

[Antonimuks]

13 hours ago, BiotechBen said:

what SSD are you using and do you happen to remember what the crash codes were?

I'll be going for crash reports now

[Antonimuks]

13 hours ago, Radium_Angel said:

If you are OCing or enabling XMP, turn that off.

Also, the BsOD, if enabled right, will record a crashdump, if yuo can post those here, I can pinpoint what's going on

Not doing OC or anything much with bios. Yet i got these crashes yesterday after installing blue stacks and enabling cpu virtualization in bios.

Tried opening crash dumps with no luck so far. (used whocrashed)

 

adding dump files and a reliability monitor screenshots. Most of the errors are just stopped apps or windows so that's weird (windows were freshly installed not long time ago and i do tend to let it install updates properly)

 

 

Also ran sfc/scannow and planing on checking individual parts for any faults

012221-12015-01.dmp 012221-11625-01.dmp

[BiotechBen]

Would you be able to show the crash codes/messages such as "Page_found_in_non-paged_area" or "Critical_system_failure" those generally point towards problems directly.

[Antonimuks]

1 hour ago, BiotechBen said:

Would you be able to show the crash codes/messages such as "Page_found_in_non-paged_area" or "Critical_system_failure" those generally point towards problems directly.

from reliability app it shows these errors:

 

i get these a lot one was at 6pm the other was at 22:30. played some games everything was extra ok watched youtube on chrome for a while and it crashed it seems it causes crashes?

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

these ones i got like 30 or 40 it was restarting i guess, wasn't around.

hardware reports lead to gpu drivers, i did reinstall drivers and yet still it just freezes and shuts down (freezes loudly via speakers).

pasting info of crashes in quotes for easy copy if anyone knows more than i can google

"

Description
Faulting Application Path:    C:\Windows\System32\dwm.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    dwm.exe
Application Version:    10.0.19041.746
Application Timestamp:    6be51595
Fault Module Name:    nvwgf2umx_cfg.dll
Fault Module Version:    27.21.14.6109
Fault Module Timestamp:    5fed9826
Exception Code:    c0000005
Exception Offset:    000000000039a8c3
OS Version:    10.0.19042.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    e916
Additional Information 2:    e91645a8a539190457b56a40d031c6d6
Additional Information 3:    cff2
Additional Information 4:    cff2cc3f3d5a41bd86f34ffc32b28d9c

Extra information about the problem
Bucket ID:    22bf32b8c6fdc7e02c4a902170757c87 (2038600254633639047)

"

 

 

"

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name:    LiveKernelEvent
Code:    141
Parameter 1:    ffffd3037c02d010
Parameter 2:    fffff804801d2100
Parameter 3:    0
Parameter 4:    4
OS version:    10_0_19042
Service Pack:    0_0
Product:    256_1
OS Version:    10.0.19042.2.0.0.256.48
Locale ID:    1033

"

 

"

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0xffffad87bd1f61e0, 0x0000000000000002, 0x0000000000000000, 0xfffff8055edc6c91). A dump was saved in: C:\WINDOWS\Minidump\012221-12015-01.dmp. Report Id: 32cf8145-59b5-45df-be71-ec2ee1e3cd33.

"

 

 

[BiotechBen]

Have you tried a fresh install of windows, it's spitting out kernel errors, you might have something wrong with your installation of windows.

[Radium_Angel]

12 hours ago, Antonimuks said:

Also ran sfc/scannow and planing on checking individual parts for any faults

Thanks for the dumps, will look them over shortly

[Radium_Angel]

2 hours ago, Antonimuks said:

from reliability app it shows these errors:

I'm going to post some relevant details here form the crash dumps, and then at the end give you my thoughts.

__

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: ffffdf3684a080c1, Address of the instruction which caused the bugcheck
Arg3: ffff8800b6a4ae00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
 

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe
 

SYMBOL_NAME:  cdd!GetConnectedStandbyProcessName+5

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

IMAGE_VERSION:  10.0.19041.1134

STACK_COMMAND:  .cxr 0xffff8800b6a4ae00 ; kb

BUCKET_ID_FUNC_OFFSET:  5

FAILURE_BUCKET_ID:  0x3B_c0000005_cdd!GetConnectedStandbyProcessName

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {64fc9402-841c-4a5c-97d3-cae66b87a441}

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffad87bd1f61e0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8055edc6c91, address which referenced memory

 

*** WARNING: Unable to verify timestamp for BstkDrv_bgp.sys
DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump
 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  HD-Player.exe

DPC_STACK_BASE:  FFFFE40B67030FB0
 

SYMBOL_NAME:  BstkDrv_bgp+15298

MODULE_NAME: hardware

IMAGE_NAME:  hardware

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  IP_MISALIGNED

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

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

Ok, thoughts:

 

Two different BSoDs, in quite a different style, one when Discord went south, the other when BlueStacks went stupid

I can't vouch for Bluestacks, or Discord for that matter, but when you have non-repeating crashes, it's *typically* a memory issue.

Either the memory is bad (in which case MemTest86 would tell you), XMP is mucking things up, RAM timings are wrong (see comment on XMP) or the RAM isn't on the QVL for your mobo and it's an issue.

 

Given that the second crashdump was truncated (possibly corrupted) I"m inclined to start by swapping RAM before moving on to other issues.

 

Another way to test if it's hardware, is run a LiveUSB install of Linux Mint (very Windows like) and see if it goes stupid. If it does, then it's hardware, if it doesn't, then your windows (or one of the programs) is borked.

 

 

 

 

[Antonimuks]

15 hours ago, BiotechBen said:

Have you tried a fresh install of windows, it's spitting out kernel errors, you might have something wrong with your installation of windows.

Fresh install was on 2020 12 25th, very recently ;/ ? I didn't do much after just a few programs and no bios/regedit modifications

[Antonimuks]

On 1/24/2021 at 1:21 AM, Radium_Angel said:

I'm going to post some relevant details here form the crash dumps, and then at the end give you my thoughts.

__

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: ffffdf3684a080c1, Address of the instruction which caused the bugcheck
Arg3: ffff8800b6a4ae00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
 

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe
 

SYMBOL_NAME:  cdd!GetConnectedStandbyProcessName+5

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

IMAGE_VERSION:  10.0.19041.1134

STACK_COMMAND:  .cxr 0xffff8800b6a4ae00 ; kb

BUCKET_ID_FUNC_OFFSET:  5

FAILURE_BUCKET_ID:  0x3B_c0000005_cdd!GetConnectedStandbyProcessName

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {64fc9402-841c-4a5c-97d3-cae66b87a441}

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffad87bd1f61e0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8055edc6c91, address which referenced memory

 

*** WARNING: Unable to verify timestamp for BstkDrv_bgp.sys
DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump
 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  HD-Player.exe

DPC_STACK_BASE:  FFFFE40B67030FB0
 

SYMBOL_NAME:  BstkDrv_bgp+15298

MODULE_NAME: hardware

IMAGE_NAME:  hardware

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  IP_MISALIGNED

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

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

Ok, thoughts:

 

Two different BSoDs, in quite a different style, one when Discord went south, the other when BlueStacks went stupid

I can't vouch for Bluestacks, or Discord for that matter, but when you have non-repeating crashes, it's *typically* a memory issue.

Either the memory is bad (in which case MemTest86 would tell you), XMP is mucking things up, RAM timings are wrong (see comment on XMP) or the RAM isn't on the QVL for your mobo and it's an issue.

 

Given that the second crashdump was truncated (possibly corrupted) I"m inclined to start by swapping RAM before moving on to other issues.

 

Another way to test if it's hardware, is run a LiveUSB install of Linux Mint (very Windows like) and see if it goes stupid. If it does, then it's hardware, if it doesn't, then your windows (or one of the programs) is borked.

 

 

 

 

Tried memtest 4 passes, no errors. Will probably do 8 passes later just to be sure. I recon discord and bluestacks got into argument and failed my system, but i never had problems before.. wierd

[Radium_Angel]

2 hours ago, Antonimuks said:

Tried memtest 4 passes, no errors. Will probably do 8 passes later just to be sure. I recon discord and bluestacks got into argument and failed my system, but i never had problems before.. wierd

Try the LiveUSB of linux mint then, it's really easy to use and discord should be available. If it behaves, then windows/software is bad, if it crashes/refuses to load, then it's hardware

[BiotechBen]

I honestly don't put all my faith in memtest and dskchk, as I've seen dead RAM come up as "functioning correctly" and very very dead video card come up as "no errors detected, hardware functioning correctly". like the "fully functional" graphics card was lighting the monitor up like a roller disco, and then would end with magenta bars accented with bright green.

[Antonimuks]

After memtest for like 2-3day my pc was running like a champ and now it's acting up again. I've deleted discord and reinstalled it did not help i checkt reliability: 

 

it crashed and then screen turned off for a few sec and got back on with an error (117 one)... i'll try installing older gpu drivers

[Antonimuks]

15 hours ago, Antonimuks said:

After memtest for like 2-3day my pc was running like a champ and now it's acting up again. I've deleted discord and reinstalled it did not help i checkt reliability: 

 

it crashed and then screen turned off for a few sec and got back on with an error (117 one)... i'll try installing older gpu drivers

Installed newest drivers, cleaned up reinstalled some programs run test today i got:

these 2 errors so far and im out of my mind i can't find whats wrong ughhh