Tweet
Oh I misunderstood the “until now”. Ok, well go ahead and follow the instructions above to turn verifier off please. Let me know if it reboots or BSOD’s.
-
-
My bad, it wasn’t clear.Originally posted by xrobwx71
I stopped the verifier and I got this response, is it normal that says no verified drivers?
[ATTACH type=“full” size=“3840x2160”]15066[/ATTACH]Comment
-
I just restarted the pc, there were no reboots or BSODsComment
-
Yes, normal. If any of the drivers were a problem, driver verifier would root it out, usually with a BSOD.
Use the PC as you normally do. Please don’t install anything until we are finished.
If you don’t have any issues by this evening, you can start installing your favorite programs. Only install one at a time, use it and let it sit for a few hours and if you don’t have any issues, move onto the next program and repeat.
If you have an issue, note the last app you installed.Comment
-
The thing is I have still had issues even without installing any additional program other than minitoolbox and speccy.Originally posted by xrobwx71
I am not surprised that during those 24 hours there weren’t reboots since they always occur after I turn on my PC after several hours of being turned off or in sleep mode
According to you, after all those tests, how likely is it that the problem is software-related rather than hardware-related? Is there any particular component I should try to substitute and test the build without?Comment
-
I’m quite sure that if I now turn the PC off and turn it on tomorrow the issue will present himself again as alwaysOriginally posted by FrancespoComment
-
Let’s do this-
Open an elevated command prompt, type powercfg -h off hit enter. Reboot.
What this does is remove the hibernate process and a file called hyberfil.sys. Hibernation can cause issues. This will rule it out.Comment
-
@Francespo Do you have an update for us?Comment
-
Yes. The computer did reboot even after I disabled hibernation, are there any more tests I can perform?Originally posted by xrobwx71Comment
-
Is there anything more I can do?Comment
-
Follow the instruction @phillpower2 posted here https://pchelpforum.net/threads/sudd...79/post-199943
Download MiniToolBox and save the file to the Desktop.
Close the browser and run the tool, check the following options;
List last 10 Event Viewer Errors
List Installed Programs
List Devices (Only Problems)
List Users, Partitions and Memory size
Click on Go.
Post the resulting log in your next reply for us if you will.Comment
-
Here it isComment
-
The very first thing. You downloaded Fan Control. When you go to the download page, it will give you a choice of .Net 8 or .Net 4.8 versions. It looks like you downloaded the .Net 8 version. You will need to download and install the .Net version 8. Download .NET 8.0 Desktop Runtime (v8.0.12) - Windows x64 Installer
Once you install version 8, Fan Control will work.Comment
-
Any progess?Comment
-
Hi, I started investigating the RAMs. I bought another ram kit they are 5600MHz (the maximum speed allowed by the processor). I used them for a few days and I haven’t had any issues since then. I’m pretty sure the problem was the RAM kit at this point, but now I’d like to go further to know if it is faulty or if there is a compatibility issue.
Now I just swapped back to the previous ram kit, one thing I noticed is that when I first swapped the old ram kit for the new one it was automatically set at 5600MHz speed while when I now have put on the old one it defaults to a speed of 4800MHz.
This was the same speed my computer was running the RAM at while the issue was there so I immediately tried to set the speed at a different value: I used Memory Try It! and I let it set the best OC values according to the RAM specs (DDR5 6000MHz CL36).
I’m not good when it comes to OC stuff so if I’m making mistakes please tell me, I’d really love guidance in this investigation processComment
Comment