Background:
Relatively new Gaming PC (Jan 2019), ran like a dream until recently - experiencing unusual/disruptive behaviour as outlined below (screenshots included from Dropbox). PC is usually running all the time but not intensively - I don't play games (but do make games) so I don't exhaust the hardware to incite any failures that I can think of but I do suspect a hardware failure somewhere - specifically the CPU due to symptoms or possibly GPU. Paws crossed it's just a software/driver issue though. 😛
Machine specification: ACER Predator Orion 9000 Intel® Core™ i9 RTX 2080 Ti Gaming PC - 3 TB HDD & 512 GB SSD
Symptoms:
Updates:
Relatively new Gaming PC (Jan 2019), ran like a dream until recently - experiencing unusual/disruptive behaviour as outlined below (screenshots included from Dropbox). PC is usually running all the time but not intensively - I don't play games (but do make games) so I don't exhaust the hardware to incite any failures that I can think of but I do suspect a hardware failure somewhere - specifically the CPU due to symptoms or possibly GPU. Paws crossed it's just a software/driver issue though. 😛
Machine specification: ACER Predator Orion 9000 Intel® Core™ i9 RTX 2080 Ti Gaming PC - 3 TB HDD & 512 GB SSD
Operating system | Windows 10 (64-bit) |
---|
Processor | - Intel® Core™ i9-7900X Processor |
---|
RAM | - 32 GB DDR4 (2666 MHz) |
---|
Graphics card | - NVIDIA GeForce RTX 2080 Ti x 2 - 11 GB DDR6 |
---|
Symptoms:
- Solid green video glitch: example: https://www.dropbox.com/s/2bz4dukmhjta1nq/youtube-green-screen.png?dl=0
Video playback sometimes stops and shows solid green (YouTube as well as locally i.e. Windows Media Player). Refreshing page / restarting application resolves issue (temporary but recurring glitch). Video drivers are up-to-date via GeForce Experience app.
- Flashing (black) screen:
Screen sometimes flashes black, comparable to what you might expect when installing video drivers
- CPU fan: see image: https://www.dropbox.com/s/sm7ogcveke2sd22/CPU fan.png?dl=0
Cooling fan sometimes kicks in unexpectedly (particularly CPU fan) but system isn't doing anything strenuous and temperature seems normal (38-48 degrees Celsius range). Temperatures never exceed 48 degrees.
- Freezing:
See my event viewer history - lots of errors (.mp4 scroll-through ensure 1080p is selected): https://www.dropbox.com/s/kntshivysu8ws11/Event_Viewer_doodledile.webm?dl=0
Most recent experience which prompted me to seek advice: Windows froze, completely unable to move cursor and Windows lingered on a still image of my desktop with open windows for a few minutes before restarting. Included recent history from Event Viewer .msc - highlighted the point at which the restart happened.
Updates:
- Manufactured unit (not custom build)
- Symptoms began in the last week altogether or in quick succession, in this order: green video glitch, black screen flashes, cpu fan, freezing. (Latest white square artefacts/glitches mentioned below)
- PSU: MODEL NO: FSP1000-50AAG
Potato photograph
- BIOS is latest version (different dates though?): R01-A4
CPU-Z screenshot (Mainboard)
PC Manufacturer's website
- Update: Flickering white square graphical glitches/artefacts 😥
- Update: Screen lingered on black screen for 2-3 minutes while browsing online - recovered - was able to resume browsing activities. Captured possible culprit on event manager (error: nvlddmkm at 07:46:23 & display warnings)
- Update: 27/05/2019 - Freezing and screen blackouts becoming increasingly frequent (once every few hours) here are recent event viewer logs:
4.01AM: https://www.dropbox.com/s/xn3dvv85seujvrq/event viewer 4.01AM 27-05-2019.webm?dl=0
6.35AM: https://www.dropbox.com/s/ssdskmv1a1qln4a/event viewer 6.35AM 27-05-2019.png?dl=0
12.06PM: https://www.dropbox.com/s/clwmafq8vfhjx4v/event viewer 12.06PM 27-05-2019.webm?dl=0
4.01AM error presented a graphics driver error when the screen recovered from the blackout. As such I uninstalled/reinstalled Nvidia drivers, but the problem persisted from 6.35AM. 😥
To Note: Recurring item of interest from Event Manager: "The description for Event ID 14 from source nvlddmkm cannot be found."
Last edited: