SSD has been replaced. Samsung did a diagnostic and found nothing wrong with the SSD either. So they sent it back. But I still kept getting BSODs so they warranty replaced the drive.
Type: Posts; User: radji
SSD has been replaced. Samsung did a diagnostic and found nothing wrong with the SSD either. So they sent it back. But I still kept getting BSODs so they warranty replaced the drive.
Oh yeah. HWinfo said I had 100% remaining life on my SSD. Might not have been the actual flash memory, though. It may have been the SSD controller going bad.
Welp, we can mark this as solved. My SSD definitely went bad.
Long story short, I sent my system back to Alienware. They reported to have replaced the mainboard, daughterboard, wireless card and all associated cables. So the only things still original are the...
Can't swap out the GPU since this is the integrated CPU/GPU on a laptop. But since switching the driver helped some, I still hope it is a driver or setting issue. Next step will be to run it a week...
Went with an alternate Intel GPU driver as suggested. This version seemed much more stable. Just had a BSOD for the 1st time in 3 days. Not a memory management one either.
...
I'll definitely try that. I have a few other recommendations to try as well which in implementing.
Thank you for the insight. Just had another BSOD and will upload the dump file and beta log in the morning.
My core isolation memory integrity has been off. I will have to reach out to...
Here are the links for the 2 memory dumps
2018-08-05-MEMORY.DMP - Google Drive
2018-08-04-MEMORY.DMP - Google Drive
None. I am not installing any of my programs other than Firefox after each clean install. Only software after each clean install is what comes default from the latest Windows USB recovery build.
I do have both the memory dumps. Just lost internet for a while this morning so I could not upload them. They are uploading right now.
I will play with the 3 tests to see if I can select...
Here are the logs for the last 2 BSODs. I am uploading the dump files.
I was able to use the 3 customized test (I/O verification, force I/O requests, IRP logging) on all the non-Microsoft...
I was able to get a pair of standard 4GB DDR4-2133 dimms of RAM to use for testing. Assuming neither of the testing dimms was bad, it is not the RAM because I still got a memory management BSOD.
...
There were no dump files on the OS drive. I did a full search. I know debug information was set to Complete Memory Dump.
Changed the Verifier settings to all but DDI compliance checking and randomized low resource simulation. Got the DRIVER_VERIFIED_DETECTED_VIOLATION BSOD. It did not list the driver on the blue...
So all setting except DDI compliance checking and randomized low resource simulation?
RAM came with my system. I know it is not the Dell system memory. The previous owner swore he had no...
Welp, Driver verifier has been on for one night for all non-Microsoft driver and no issues or lagging. I am confused about one thing. The first link you posted to use driver verifier said to check...
What about the Microsoft update installed drivers for my graphics cards? Update automatically applied drivers for my Intel and Nvidia GPUs. Should I start with this drivers for verification?
Can I install new drivers with verifier turned on? And each time I install drivers, I will need to go in and update the driver verifier list list, yes?
Didn't bother with the Macrum backup image since their was a disclaimer that it would not turn off driver verifier. So there was no difference between it and a system restore.
Executing verifier...
Followed driver verifier instructions exactly. Did a fresh system restore point and enabled driver verifier exactly as prescribed, checking only the non-microsoft drivers. Complete bricked system. ...
I did the first time it was recommended. I did not induce a BSOD that night with about 6 hours of continuous use. Should I keep driver verifier on until I get a BSOD?
Here is the link to the memory dump.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Re ran the log collector. The memory dump is being uploaded. Will post the link when it is finished.
A new BSOD, ran the collector directly after it happened. It will be a while before the dump file is uploaded.