BSOD about once a month when not in use

[den942]

About once a month when the computer is on but not being used, I see the BSOD error.

 

[axe0]

Hi den942,

Are you still in need of help?

 

[den942]

Yes, it just happened again. Computer on but not being used when it happens.

 

[axe0]

Please run the DM Log Collector again and upload a new zip, the current uploaded one misses several logs.
You could check if there are

1. 18 .txt,
2. 1 .nfo,
3. 1 or more .dmp,

files present, if this is the case then all logs are present
If there are a few missing, no problem as we can get them manually if required

 

[den942]

Here it is...

Please run the DM Log Collector again and upload a new zip, the current uploaded one misses several logs.
You could check if there are

1. 18 .txt,
2. 1 .nfo,
3. 1 or more .dmp,

files present, if this is the case then all logs are present
If there are a few missing, no problem as we can get them manually if required

 

[den942]

Don't know if this might help but here it is...

Here it is...

Please run the DM Log Collector again and upload a new zip, the current uploaded one misses several logs.
You could check if there are

1. 18 .txt,
2. 1 .nfo,
3. 1 or more .dmp,

files present, if this is the case then all logs are present
If there are a few missing, no problem as we can get them manually if required

 

[axe0]

Please re-run the DM Log Collector and ensure to check the content that the tool creates by opening the zip file.
The zip should be at least a 100KB large.

 

[den942]

Please re-run the DM Log Collector and ensure to check the content that the tool creates by opening the zip file.
The zip should be at least a 100KB large.

I'll run it a third time. Why is it not producing all the required files? It doesn't show any errors when I run it.

 

[den942]

Please re-run the DM Log Collector and ensure to check the content that the tool creates by opening the zip file.
The zip should be at least a 100KB large.

Here is the third try. If it isn't all there I guess I'll try again...

 

[axe0]

It appears your installation is counterfeit, no support may be provided until a genuine activation has been used on a clean install.

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and analysts won't try it.

I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

 

[den942]

It appears your installation is counterfeit, no support may be provided until a genuine activation has been used on a clean install.

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and analysts won't try it.

I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

Installation is genuine and has been validated through Microsoft Genuine Validation. Under "System" it says "Windows is Activated", shows the Product ID, and shows the "Genuine Microsoft Software" logo. Why do you say it is not?

 

[axe0]

Because the activation is the kind that is used with preinstalled Windows, like with laptops.

They cannot be used on retail boards in a genuine way, that Windows is activated means nothing because the activation is not genuine.

 

[den942]

Because the activation is the kind that is used with preinstalled Windows, like with laptops.

They cannot be used on retail boards in a genuine way, that Windows is activated means nothing because the activation is not genuine.

So Microsoft validates installations that are not genuine? Why would they do that? Makes no sense to me.
My hard drive was failing and I cloned the bad one to a new one and it was validated again.

 

[axe0]

Microsoft eventually validates every activation. Those that haven't been activated genuinely will after some time give the message that Windows isn't activated, because the exploit is broken.

FYI, my current definition of validating is the process of checking. Thus only checking if a system is genuine or not, this does not include the result.