F5F Stay Refreshed Hardware Desktop You're experiencing issues with your PC and programs. Let's troubleshoot this together.

You're experiencing issues with your PC and programs. Let's troubleshoot this together.

You're experiencing issues with your PC and programs. Let's troubleshoot this together.

Pages (2): Previous 1 2
A
andreyu201
Junior Member
14
06-15-2022, 10:51 PM
#11
Configure PCIE to version 3.0 in the UEFI and attempt GPU usage (using riser cable as required). Check if this resolves the problems. Riser cables are known to cause various issues, including micro stuttering. It turns out transmitting 32 GB/s at a 100MHz clock over narrow traces is tricky, especially with extensions involved... who would have thought?
A
andreyu201
06-15-2022, 10:51 PM #11

Configure PCIE to version 3.0 in the UEFI and attempt GPU usage (using riser cable as required). Check if this resolves the problems. Riser cables are known to cause various issues, including micro stuttering. It turns out transmitting 32 GB/s at a 100MHz clock over narrow traces is tricky, especially with extensions involved... who would have thought?

Z
ZexyZeke
Member
166
06-15-2022, 11:28 PM
#12
I've turned off the GPU, but the Chrome keeps crashing as if nothing changed. I don’t think I’ve spent enough time troubleshooting to find out what’s causing it.
Z
ZexyZeke
06-15-2022, 11:28 PM #12

I've turned off the GPU, but the Chrome keeps crashing as if nothing changed. I don’t think I’ve spent enough time troubleshooting to find out what’s causing it.

C
catseecoo
Senior Member
662
06-18-2022, 05:33 AM
#13
The displayed error screen often resembles GPU problems, but it's more likely a Windows issue caused by using a monitor with higher resolution than 1080p. I wasn't certain this was the sole explanation. I strongly dislike PCIe risers. If you have any dump files, please share them. Chrome crashes are pretty typical due to RAM faults. I noticed it appeared at 21% in the image, so if it's stuck it probably isn't a RAM failure. You can also look for kernel dumps, though they're much larger and harder to send. Compressing these is essential. The file named Memory.dmp is located in C:\Windows and only retains the most recent version because of its size. EDIT: I hadn’t realized I was the one assisting you before. I see I didn’t mention it could also relate to the slot itself—not just probability, but from the error. I usually include that note on Reddit, though I might have overlooked it. The Gameflt.sys driver was eventually disproven; an engineer on a debugging forum strongly disagreed and corrected my thinking at the time. We considered WHEA crashes as a possibility, assuming 0x10 WHEA crashes were reported by drivers. If you're still experiencing them, it's unclear if they're all scrambled. Adjusting the page file location might help if the issue persists.
C
catseecoo
06-18-2022, 05:33 AM #13

The displayed error screen often resembles GPU problems, but it's more likely a Windows issue caused by using a monitor with higher resolution than 1080p. I wasn't certain this was the sole explanation. I strongly dislike PCIe risers. If you have any dump files, please share them. Chrome crashes are pretty typical due to RAM faults. I noticed it appeared at 21% in the image, so if it's stuck it probably isn't a RAM failure. You can also look for kernel dumps, though they're much larger and harder to send. Compressing these is essential. The file named Memory.dmp is located in C:\Windows and only retains the most recent version because of its size. EDIT: I hadn’t realized I was the one assisting you before. I see I didn’t mention it could also relate to the slot itself—not just probability, but from the error. I usually include that note on Reddit, though I might have overlooked it. The Gameflt.sys driver was eventually disproven; an engineer on a debugging forum strongly disagreed and corrected my thinking at the time. We considered WHEA crashes as a possibility, assuming 0x10 WHEA crashes were reported by drivers. If you're still experiencing them, it's unclear if they're all scrambled. Adjusting the page file location might help if the issue persists.

B
BlueStar_LH
Posting Freak
842
06-18-2022, 11:06 AM
#14
Support Bjoolz’s suggestion if you have dump files available. Modify the UEFI following the recent updates from December that resolve potential problems. Consider using just one RAM stick in DIMM A2. [Make sure both sticks were placed in A2 and B2 when running two] If one works, test the other. A consistent crash with a single stick indicates it may be faulty.
B
BlueStar_LH
06-18-2022, 11:06 AM #14

Support Bjoolz’s suggestion if you have dump files available. Modify the UEFI following the recent updates from December that resolve potential problems. Consider using just one RAM stick in DIMM A2. [Make sure both sticks were placed in A2 and B2 when running two] If one works, test the other. A consistent crash with a single stick indicates it may be faulty.

L
Leyhaya
Posting Freak
801
06-24-2022, 08:01 PM
#15
I’m just beginning to understand this. After Samsung fixed it, I restored the OS, and everything seems normal so far. It’s odd, and I’m still trying to figure out what happened.
L
Leyhaya
06-24-2022, 08:01 PM #15

I’m just beginning to understand this. After Samsung fixed it, I restored the OS, and everything seems normal so far. It’s odd, and I’m still trying to figure out what happened.

Pages (2): Previous 1 2