- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
re: PC turns on, Monitors do not wake
Posted on 12/28/23 at 6:48 pm to reauxl tigers
Posted on 12/28/23 at 6:48 pm to reauxl tigers
quote:
34-45-45-115
9.444ns
At this point in DDR5, that is *very* fast RAM. Your CPU just might not be able to keep up. If you haven't already, download and install HWiNFO64. In the very bottom right of all of that data, check to see if your system is throwing WHEA errors.
0
Posted on 12/28/23 at 6:50 pm to reauxl tigers
quote:
I'm assuming the hardware changes caused this. I was able to re-activate it using the "my hardware changed" option in settings.
Windows will do that anytime you "reinstall" your CPU.
Posted on 12/28/23 at 7:28 pm to reauxl tigers
quote:
The PerfCap Reason says "Pwr", but I have the power limit maxed out in MSI afterburner.
Just noticed this. Don't stress over that. There's always going to be something that acts as the limit on GPU performance. Power is a perfectly acceptable one.
Posted on 12/28/23 at 9:14 pm to Joshjrn
This is the drive I have Windows installed on. Usually keep about 100GB of free space.
Also noticed this
Nothing to see here
Also noticed this
Nothing to see here
This post was edited on 12/28/23 at 9:39 pm
Posted on 12/28/23 at 9:42 pm to reauxl tigers
That drive health is more than a little alarming…
Being you aren’t throwing WHEA errors, we’ll have to test the RAM a bit more in depth to make sure there aren’t any issues. I’ll post a process tomorrow
Being you aren’t throwing WHEA errors, we’ll have to test the RAM a bit more in depth to make sure there aren’t any issues. I’ll post a process tomorrow
Posted on 12/29/23 at 1:58 am to Joshjrn
I turned off XMP and just set the frequency to 6400 G2 100:100 and the CPU to 5ghz.
Ran a handful more GTA benchmarks b/c this seems like the only one where stuttering seems to occur, even after verifying the game files.
The stuttering got progressively worse with each benchmark, starting out with none, then having quite a bit on the last one.
Each time stuttering would happen, the PerfCap Reason said VRel/VOp (blue/orange). Idk if this is an issue or just nothing. My PSU is a bit old. Although I don't have this problem running a Furmark stress test. Maybe it's a setting somewhere within GTA that's causing this. I wonder if maybe there's just a bottleneck happening during the specific scenes where there's stuttering.
Ran a handful more GTA benchmarks b/c this seems like the only one where stuttering seems to occur, even after verifying the game files.
The stuttering got progressively worse with each benchmark, starting out with none, then having quite a bit on the last one.
Each time stuttering would happen, the PerfCap Reason said VRel/VOp (blue/orange). Idk if this is an issue or just nothing. My PSU is a bit old. Although I don't have this problem running a Furmark stress test. Maybe it's a setting somewhere within GTA that's causing this. I wonder if maybe there's just a bottleneck happening during the specific scenes where there's stuttering.
This post was edited on 12/29/23 at 3:12 am
Posted on 12/29/23 at 7:44 am to reauxl tigers
quote:
Each time stuttering would happen, the PerfCap Reason said VRel/VOp (blue/orange). Idk if this is an issue or just nothing. My PSU is a bit old.
VOp isn't inherently problematic, though unless you are running an undervolt, it's odd to see and possibly an issue. On the other hand, VRel is almost inherently problematic, as it's saying your voltage is "unreliable". Unless you've done something very weird, this usually means there is something wrong with your PSU, cables, connectors, etc.
With all of that said, GTAV is a bit of a mess, so general stuttering wouldn't surprise me, even in the best of situations. But your drive health and possible PSU issues are something I would be inclined to address, regardless.
Posted on 12/29/23 at 1:20 pm to Joshjrn
Yea the drive is going on 7 years old, the PSU might be older, it was a hand me down from a friend when I needed an upgrade in wattage. Already ordered a nice, shiny 2TB NMVe for my main drive, PSU might be next.
This post was edited on 12/29/23 at 1:25 pm
Posted on 12/29/23 at 11:23 pm to reauxl tigers
Went ahead and undervolted the GPU and CPU, much better results but still some stuttering. I'm convinced the issue is just GTAV.
Posted on 12/30/23 at 12:49 pm to reauxl tigers
Yup, GTAV is a mess. I wouldn’t worry unless you’re seeing that behavior in other, more stable games.
Posted on 12/30/23 at 5:31 pm to Joshjrn
shite, I clean installed windows on the new SSD, tried to reactivate Windows with the "hardware changed" method again and it will not allow me to do so. I have a digital copy with my Microsoft account and I'm signed in.
Is there any way for me to reactivate Windows again? Like removing the device on my account that Windows is active on?
Is there any way for me to reactivate Windows again? Like removing the device on my account that Windows is active on?
This post was edited on 12/30/23 at 5:35 pm
Posted on 12/30/23 at 5:38 pm to reauxl tigers
That's actually outside of the scope of my knowledge. It's only very recently, like less than six months ago, that Microsoft starting giving a shite about that kind of thing. I've been using an old Windows 7 key over and over for years. Anyway, worst case, reach out to Microsoft customer support and see what they suggest.
Posted on 12/31/23 at 1:45 pm to Joshjrn
I made such a mess of this 
Microsoft support said I couldn’t reactivate after the clean install b/c I’ve had a digital license since Windows 7 that I've been upgrading from. So I said screw it and went back to the old drive, wiped the new drive and just cloned to it.
I spent the next 4 hours running CMD, formatting and cloning from drive to drive trying to figure out why every time I booted up I would receive this error.
Eventually, I fugured out the default OS was still set to the clean installed copy of Windows even though the drive it was on was formatted. Hopefully I don't frick anything else up from here on.
Microsoft support said I couldn’t reactivate after the clean install b/c I’ve had a digital license since Windows 7 that I've been upgrading from. So I said screw it and went back to the old drive, wiped the new drive and just cloned to it.
I spent the next 4 hours running CMD, formatting and cloning from drive to drive trying to figure out why every time I booted up I would receive this error.
Eventually, I fugured out the default OS was still set to the clean installed copy of Windows even though the drive it was on was formatted. Hopefully I don't frick anything else up from here on.
This post was edited on 12/31/23 at 1:49 pm
Posted on 12/31/23 at 1:49 pm to reauxl tigers
You've run into an impressive number of different issues during this build
Posted on 12/31/23 at 2:16 pm to Joshjrn
Yea it's been nothing but a pain so far. Lessons learned tho.
Page 2 of 2
Popular
Back to top
Follow TigerDroppings for LSU Football News