- Joined
- Aug 9, 2024
- Messages
- 80 (0.94/day)
- Location
- Michigan, United States
| Processor | Intel i7-13700K |
|---|---|
| Motherboard | Asus ROG Strix Z690-E Gaming |
| Cooling | NZXT Kraken Elite 360 |
| Memory | G.Skill Trident Z DDR5-6400 |
| Video Card(s) | MSI RTX 4090 Suprim X Liquid |
| Storage | Western Digital SN850X 4Tb x 4 |
| Case | Corsair 5000D Airflow |
| Audio Device(s) | Creative AE-5 Plus |
| Power Supply | Corsair HX-1200 |
| Software | Windows 11 Pro 23H2 |
In the process of submitting a support ticket to Nvidia (for the first time in my life), I was asked to generate one of these reports, which I've done before, but not very often, and this time around I actually spent a lot more time poring over it.
One interesting thing I noticed was the Windows Error Reporting message in the title, and in my case, it was not only attached to Edge but also to several benchmarking applications that I had run recently (some for posting results here on the Benchmarking page). I did some Googling online, and the consensus appears to be that these are more application related and not necessarily a symptom of trouble. These messages don't register with datre and time stamps in the event logging, which is why I never noticed it until last night.
Has anyone ever run into a situation where one of these messages has led to a significant root cause or been an indication of system instability, or is this something that can be safely ignored?
One interesting thing I noticed was the Windows Error Reporting message in the title, and in my case, it was not only attached to Edge but also to several benchmarking applications that I had run recently (some for posting results here on the Benchmarking page). I did some Googling online, and the consensus appears to be that these are more application related and not necessarily a symptom of trouble. These messages don't register with datre and time stamps in the event logging, which is why I never noticed it until last night.
Has anyone ever run into a situation where one of these messages has led to a significant root cause or been an indication of system instability, or is this something that can be safely ignored?