New
#31
I could actually cry, my PC crashed earlier, and after it restarted, I was so busy multi-tasking I actually ran CCleaner and overwrote the DMP files again. Just a momentary lapse of reason. I believe it was a DXDIAG related error and I was running ROG RAM Disk at the time. Rest assured I will immediately upload the DMP files once I can recreate a BSOD. The weird thing is that it never seems to coincide with a specific action so is very hard to predict. Apologies. Chris
FINALLY - never been so glad to see a BSOD! Happened after leaving PC on idling so very random.
Logs attached - very grateful for input as stumped on this as discussed throughout this thread
NoteRun the tests on all hard drives/partitions!
Please run HDTune first, in the order posted!
Run HDTune to
- check the health,
- scan for errors, no quick scan but full scan
- run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
- the health,
- the error scan,
- the benchmark incl. following
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
NoteDo not run SeaTools on an SSD as the results will be invalid.
Make a photo of the result and post it.
Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
Hi.
Happy to do this but as you can see from my username, hard drives are something I'm definitely "into"
The SMART is fine on all devices but I will do what you request but will be later today as up to my neck in project work.
Thanks again for the response - my response as per your instructions will be forthcoming as stated
Hi. As I knew anyway, the SMART on all HDDs / SSDs is near perfect. I will try to complete the rest of your requests but I really do think that the HDD / RAM is not the issue here as both aspects have been thoroughly tested in the past.
Can you please indicate what the dump files, show, please?
My working assumption is that the Elpida branded RAM on my 770 GPU is what is at fault.
Any tests to try this theory out, please?
Att: SMART info
It's been some time since the last post so I had to check the dump again. It's a 0x116 which means Windows attempted to get the display drivers to respond but failed to do so resulting in a crash.
However, the eventlogs showed some concerning things related to your drive. Although they were already tested, in between the months things do change and hardware can fail, that is why I posted HDD tests (again) for all drives.
Regarding your theory, it's a possibility but currently I would suggest to reinstall/update the GPU drivers due to the frequence of the crashes over the past few months.Code:2018-06-23T22:25:13.558 The device, \Device\CdRom0, has a bad block. 2018-06-23T22:25:03.582 The device, \Device\CdRom0, has a bad block. 2018-06-05T17:46:23.648 The IO operation at logical block address 0x0 for Disk 5 (PDO name: \Device\00000084) was retried. 2018-06-05T17:45:05.050 An error was detected on device \Device\Harddisk6\DR6 during a paging operation. 2018-06-05T17:45:05.050 An error was detected on device \Device\Harddisk6\DR6 during a paging operation. 2018-05-26T18:40:01.579 An error was detected on device \Device\CdRom0 during a paging operation. 2018-05-26T18:40:00.471 The device, \Device\CdRom0, has a bad block. 2018-05-26T18:39:51.813 The device, \Device\CdRom0, has a bad block.
PS, the dump took too long to load for any insight so I just gave the general meaning about the crashdump.
Hi the GPU drivers were uninstalled in Safe Mode using DDU uninstaller and latest reinstalled. I've done this several times.
As regards the "bad block" message. Can you narrow that down to a drive descriptor or volume letter?
My boot drive is a Samsung 960 Pro NVMe which was brand new very recently.
*Could the "bad block" refer to a RAM Drive?*
I have a ~40GB RAM drive and although Memtest passes ad infinitum at SPD speeds, I'm just wondering . . . . .