F5F Stay Refreshed Hardware Desktop Identifying RAM issues - occurrence and crashes

Identifying RAM issues - occurrence and crashes

Identifying RAM issues - occurrence and crashes

Pages (3): Previous 1 2 3 Next
I
Iya20154
Junior Member
21
02-28-2018, 12:15 PM
#11
The system restore didn’t succeed, so I’m considering another option. I refreshed the chipset drivers once more. For context, my Radeon Software manager mentioned Rainbow Six Siege launched on July 26th, 2020 with an average of 132 FPS. Based on Radeon data, CSGO currently averages 93 FPS.
I
Iya20154
02-28-2018, 12:15 PM #11

The system restore didn’t succeed, so I’m considering another option. I refreshed the chipset drivers once more. For context, my Radeon Software manager mentioned Rainbow Six Siege launched on July 26th, 2020 with an average of 132 FPS. Based on Radeon data, CSGO currently averages 93 FPS.

I
Izaiah3000
Junior Member
8
02-28-2018, 02:36 PM
#12
Yes, it was the reset that didn’t succeed, not the sfc/scannow choice. There was an issue preventing the process from completing.
I
Izaiah3000
02-28-2018, 02:36 PM #12

Yes, it was the reset that didn’t succeed, not the sfc/scannow choice. There was an issue preventing the process from completing.

T
thibdu87
Member
229
03-01-2018, 04:25 AM
#13
When issues arose with resetting your PC, I used the sfc /scannow command and it helped a lot, especially after a PSU failure and system corruption.
T
thibdu87
03-01-2018, 04:25 AM #13

When issues arose with resetting your PC, I used the sfc /scannow command and it helped a lot, especially after a PSU failure and system corruption.

D
Daantjeplays
Member
157
03-01-2018, 09:43 AM
#14
The system's Restore Point failed to finish. I'm not confident about my actions. It took 30 minutes before the screens went dark; I waited 10 minutes afterward, with lights still on and fans operating. At that stage, I pressed the power button. Running sfc /scannow is now at 70%.
D
Daantjeplays
03-01-2018, 09:43 AM #14

The system's Restore Point failed to finish. I'm not confident about my actions. It took 30 minutes before the screens went dark; I waited 10 minutes afterward, with lights still on and fans operating. At that stage, I pressed the power button. Running sfc /scannow is now at 70%.

L
lewade2002
Junior Member
33
03-01-2018, 10:42 AM
#15
Scan completed successfully. No integrity issues detected. PS C:\WINDOWS\system32> sfc /scannow Initiated system check. The process is underway and will require time. All verification steps finished with 100% accuracy. Windows Resource Protection confirmed no violations.
L
lewade2002
03-01-2018, 10:42 AM #15

Scan completed successfully. No integrity issues detected. PS C:\WINDOWS\system32> sfc /scannow Initiated system check. The process is underway and will require time. All verification steps finished with 100% accuracy. Windows Resource Protection confirmed no violations.

C
Coconutpants
Junior Member
19
03-02-2018, 01:59 PM
#16
This situation is odd, particularly if your system remains slow as you mentioned (you haven’t used a 144 hz monitor that just restarted, which might explain the lag). If you’re encountering black screens and crashes without BSODs, it likely points to a graphics card or driver problem. Even after resetting everything, removing extra RAM, and checking for issues, I’m running out of options except for a potential graphics-related fix. I’d suggest trying a reset again this time and letting it run longer. It would be problematic if you needed a full factory reset just because of this strange issue. If you have time, look for help elsewhere. As a final resort, consider backing up important data to an external drive or USB and reinstalling, though I’m sure it can be resolved. PS: Did you replace the new memory and return the old one to its original slots? That’s another possibility.
C
Coconutpants
03-02-2018, 01:59 PM #16

This situation is odd, particularly if your system remains slow as you mentioned (you haven’t used a 144 hz monitor that just restarted, which might explain the lag). If you’re encountering black screens and crashes without BSODs, it likely points to a graphics card or driver problem. Even after resetting everything, removing extra RAM, and checking for issues, I’m running out of options except for a potential graphics-related fix. I’d suggest trying a reset again this time and letting it run longer. It would be problematic if you needed a full factory reset just because of this strange issue. If you have time, look for help elsewhere. As a final resort, consider backing up important data to an external drive or USB and reinstalling, though I’m sure it can be resolved. PS: Did you replace the new memory and return the old one to its original slots? That’s another possibility.

T
Thunderbear55
Junior Member
21
03-08-2018, 10:18 PM
#17
The original data hasn't been changed; only another BSOD page fault appears. I'm attempting a final restore by playing a movie and letting it finish. If it fails before the film ends, I'll perform a complete factory reset.
T
Thunderbear55
03-08-2018, 10:18 PM #17

The original data hasn't been changed; only another BSOD page fault appears. I'm attempting a final restore by playing a movie and letting it finish. If it fails before the film ends, I'll perform a complete factory reset.

D
DatGuyJaden
Member
58
03-09-2018, 06:16 PM
#18
Consider resetting the whole system with the added RAM installed. Check the compatibility guide for the MB model to confirm support.
D
DatGuyJaden
03-09-2018, 06:16 PM #18

Consider resetting the whole system with the added RAM installed. Check the compatibility guide for the MB model to confirm support.

P
paxpax1
Junior Member
36
03-12-2018, 11:32 PM
#19
The page fault error seems linked to an incomplete recent reset, possibly due to a faulty update or an incompatible driver. It could also indicate a problem with your RAM, though using outdated RAM is unusual unless something disrupted your existing RAM or slots.
P
paxpax1
03-12-2018, 11:32 PM #19

The page fault error seems linked to an incomplete recent reset, possibly due to a faulty update or an incompatible driver. It could also indicate a problem with your RAM, though using outdated RAM is unusual unless something disrupted your existing RAM or slots.

U
UsagiK
Junior Member
49
03-13-2018, 01:56 AM
#20
At that stage, the most likely outcome is a complete system wipe, requiring a fresh factory setup.
U
UsagiK
03-13-2018, 01:56 AM #20

At that stage, the most likely outcome is a complete system wipe, requiring a fresh factory setup.

Pages (3): Previous 1 2 3 Next