I know, it sucks, he was the BSOD masteroh ok
Cool, let us know how you get on.i will see how it goes now, with the updated gpu drivers and the registry change
thanks
That's not a fix, all that's doing is nerfing the performance of the processor. It's not a solution. it's a workaround at best, but a poor one.After months of this issue i have found the actual issue
Its with the way the cpu boosts up and down
So, if i put the minimum processor state to 99%, the cpu will not BSOD (hasnt bsod in 3 days of being on, different workloads)
If i put it to 5% (the default) it does the same old crash
what shall i do now? replace motherboard? check PSU? RMA cpu?
What do you recommend the minimum processor state be?That's not a fix, all that's doing is nerfing the performance of the processor. It's not a solution. it's a workaround at best, but a poor one.
The error code is a driver issue.
I'd suggest a clean install.
It's default value, should never be changed, or certainly lowered rather than raised. All you've done is hugely increase the rest state of the processor before sleep, but it's not fixing anything, the issue that's occurring needs to be fixed to stop it occurring in the first place, not worked around so it's never triggered. You'll see far higher electricity bills currently if you leave that setting on aside from other issues.What do you recommend the minimum processor state be?
I have done like 5 clean installs with this same problem.
For reinstall I am doing:It's default value, should never be changed, or certainly lowered rather than raised. All you've done is hugely increase the rest state of the processor before sleep, but it's not fixing anything, the issue that's occurring needs to be fixed to stop it occurring in the first place, not worked around so it's never triggered. You'll see far higher electricity bills currently if you leave that setting on aside from other issues.
So the assumption must be that the clean install is not correct.
How are you sourcing drivers.
What process are you going through for the install? How are you processing partitions?
I think that its a hardware issue in the first place as it shouldnt have persisted over many windows installs if its software, do you see where i am coming from?It's default value, should never be changed, or certainly lowered rather than raised. All you've done is hugely increase the rest state of the processor before sleep, but it's not fixing anything, the issue that's occurring needs to be fixed to stop it occurring in the first place, not worked around so it's never triggered. You'll see far higher electricity bills currently if you leave that setting on aside from other issues.
So the assumption must be that the clean install is not correct.
How are you sourcing drivers.
What process are you going through for the install? How are you processing partitions?
What do you mean by this, are you specifically formatting each partition and then installing where?format every drive when on the win10 reinstall usb
NoWhat do you mean by this, are you specifically formatting each partition and then installing where?
Already done thatWorth considering a bios update?
Ok, so this is what I'm trying to clarify.in the setup there is an option to delete whats on the partition, then format it so it becomes part of unallocated space
This would suggest you're formatting each partition on every drive which would suggest you don't undertsadn the process of a clean install. There is only one system drive.format every drive when on the win10 reinstall usb
I am being stupid.Ok, so this is what I'm trying to clarify.
This isn't the case, it's not possible to format a partition that doesn't exist.
This would suggest you're formatting each partition on every drive which would suggest you don't undertsadn the process of a clean install. There is only one system drive.
I'm not trying to be clever although I realise that's how I'm coming across, just genuinely trying to figure out what process you're taking to find out why the issue isn't going.
A lot of people don't know the process of a clean install and when you try to fathom which part they're getting wrong they seem to try to cover their mistakes which makes troubleshooting a hell of a lot more difficult.
From what you've said so far, either the partitions aren't being correctly deleted, although I think I understand what you're meaning but it's best never to assume. Or that it's an issue with chipset driver not being manually installed along with GPU drivers, or that there's a RAM issue.