New
#81
It was not automated.
It was not automated.
Okay, but the dump and memory files were deleted by some process.
In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread
If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab > scroll down to system and advanced > post an image into the thread
It can be easy to miss BSOD if automatically restart is checked.
Please uncheck automatically restart then reboot to keep the setting change.
With automatically restart unchecked:
a) There should be a BSOD window with bugcheck and : (
b) Sometimes it may display a misbehaving driver in the form *.sys
c) At the start of the BSOD you may see a % counter.
d) If you see the % counter allow it to rise to 100 % before rebooting so that there is sufficient time to create the dump file.
Please run the BETA log collector and post a new zip into the thread.
I like to keep automatic restart on because I remote into the computer alot, so if it does BSOD while I am away, I can still remote in. I don't think automatic restart is causing it to miss BSOD files. I had a dump file this morning at 8 am, but at 10 am it got deleted somehow.
Attachment 212545
The bugchecks in the logs were:
154
139
19
1A
18
The options are to wait for a new BSOD and then collect the mini and memory dump for debugging.
Alternatively if the files are backed up, and if there is a backup image, a tool can be used to stress test the drivers.
Got another one over the weekend. Memory and dump file were still there when I logged in today.
Attachment 215159
Memory file
MEMORY.7z - Google Drive
The BSOD was bugcheck 139.
Windows driver verifier was not in use.
There was no definitive misbehaving driver in the latest memory.dmp.
In May memtest86+ version 5.01 had passed (approximately 6 months ago).
Later there was a bit flip and philc43 was suspecting problems with DIMM.
Please clean any dust in the computer and remove both RAM modules and label them and the DIMM.
Run a Memtest86+ version 5.01 test with the same RAM module in each DIMM for 8 or more passes.
A substantial portion of the testing can be performed overnight.
It takes approximately 1 - 2 hours / GB RAM.
For each test post an image into the thread.
And for each test please indicate the DIMM that was tested.
Just one error is a fail and testing can be aborted.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM | Tutorials
Last edited by zbook; 25 Nov 2018 at 23:33.
Got another one today. I will try and check the ram sometime this weekn Attachment 215187
memory
https://drive.google.com/file/d/1BQe...ew?usp=sharing