BSOD While the Computer Is Asleep

[Neophile]

There are some other treads on this issue, but not quite the same and my log files are certainly different. However, as I do not know where to find where the problem lies in them, I must ask someone to help me with logs.

It is simple to describe. It started over a weak ago. At any time the computer is in sleep mode, it can produce a blue screen, never while awake. It can be just a few minutes after I put in sleep mode, or it can be one hour or more after, but it will produce a BSOD for sure, all depending on the patience to wait for it to happen. I have to use the computer as if the sleep function did not exist. Tank you for any help.



My logs

 

[file3456]

First, the Google Drive link is not valid. You didn't link to the source correctly. You can just simply zip the text file and attach it here.

Second, while this may be a little upsetting to hear, you really should refrain from using those low power modes like sleep or hibernation. I realize this doesn't fix your issue, but those low power states can mess up your computer in many ways. It doesn't happen to everyone, but I've been helping people with computer issues on various tech forums since 2006 and I've seen my fair share of help threads all relating to those low power states. It would be best to just power on and power off the computer normally. This is what I do.

I can never remember the acronym, but it's for the Windows power driver or something like that and I think that could be the issue here with the low power state of sleep. It's probably doing something hardware wise and freaking out thus creating a BSOD. It could be related to a recent piece of software you installed or a driver. Damn near all BSODs involve a driver or hardware.

I'm not on the up and up with reading raw logs like the one you tried linking to from Google Drive. But if you run the program Who Crashed, that may in fact clue you in to the source of the issue right away. Though, the program may be cryptic by saying it's some driver or DLL. But if you share what it reports this might shed some light on the issue.

But again, I'd really refrain from using a low power state like sleep or hibernation. If you are in fact using any full disk encryption, you don't want to use those low power modes. Just putting that out there.

Resplendence Software - WhoCrashed, automatic crash dump analyzer

 

[Neophile]

Thank you for replying.

I am not sure that I understood your point. Do you mean it is better never use sleep or hibernation? For many people that is one of the best functions on the OS. I do not know if there are many people not using either one.

Sorry for the bad link, I am not so acquainted with Google Drive. It is now attached here. I hope you can tell me what is wrong.

Meanwhile it crashed again, I tried WhoCrashed from your link at the bottom of your post. There are now six BSOD recorded. All reports are the same, systematically pointing the fault to the same kennel file ntoskrnl.exe, possibly caused from a driver. How can I know which one is the culprit?

WhoCrashe says to configure the system to write out a complete or automatic crash dumps for more complete results. However, at the place they point to there isn't any "complete memory dumps", but only "Small memory dump" or "Kennell memory and dump", and I have the later.

 

[axe0]

It appears the installation is counterfeit, per forum rules no help can be given until Windows is genuinely activated.

 

[Neophile]

It appears the installation is counterfeit, per forum rules no help can be given until Windows is genuinely activated.

That is not true. I had windows 10 and, but I reinstalled 7 because I didn't like it. 10 was installed from an upgrade directly downloaded from Microsoft's site two years ago, and I didn't even have to validate the upgrade. If 7 was counterfeit, 10 it would note install, or It would have asked for validation.

 

[axe0]

Please follow Windows Genuine and Activation Issue Posting Instructions.

Your logs show the following

Registered Organization:   
Product ID:                00426-OEM-8992662-00006
Original Install Date:     25-06-2019, 19:38:42
System Boot Time:          22-07-2020, 17:04:34
System Manufacturer:       System manufacturer
System Model:              System Product Name

00426-OEM-8992662-00006 is a product ID that cannot be transferred and comes preinstalled with Windows. It's legally impossible to have it on a custom build PC, because it requires a SLIC table in the BIOS to activate that OEM vendors flash into the BIOS before it arrives to the customer.

 

[Snick]

axe0



Totally agree!