New
#11
All ssd's have been scanned now. Link to the notepad created by the script.
I have a Windows USB still from when I last reinstalled Windows a couple weeks ago.
Daily BSOD. Trying to Determine if Bad RAM, SSD, Motherboard, or Other
-
-
New #12
Chkdsk on E: and D: look good.
Please repeat chkdsk /b /v C:
Run the chkdsk switches overnight while sleeping.
C:\WINDOWS\system32>chkdsk /b /v C:
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
Reboot
Then post a new V2 share link into the newest post.
These were the bad RAM regions that were blocked by Windows:
Code:RAM Defects ----------- 0x15d7e2 0x15d7e5 0x1650ef 0x1bfb38 0x1bfb39 0x1bfb3b 0x1bfb3c 0x1bfb3d 0x1bfb3f 0x2eb4f3 0x33c790 0x33c793 0x33c797 0x7db4b0 0x7db4b1 0x7db4b2 0x7db4b3 0x7db4b4 0x7db4b5 0x7db4b6 0x7db4b7
After completing chkdsk and posting a new V2 share link please remove all RAM modules.
Then test one RAM module at a time in the same DIMM using Memtest86.
Run two tests of four passes each (free version) for a total of eight passes.
Take pictures and post images or share links into this thread.Last edited by zbook; 15 Mar 2023 at 22:06.
-
New #13
To run a dskchk on the C drive doesnt take long. Just a few minutes. There's not a lot on the C drive to scan, but here's the link to the new V2 log collector.
I'll do the RAM testing as soon as I can. With the new RAM installed and windows giving blocked RAM regions does that suggest there's something wrong with the motherboard?
-
New #14
What was the date of the new RAM installation: F4-2400C15-16GVR?
Boot to a Windows Media Creation Tool (MCT) flash drive > Windows Recovery Environment (RE) > command prompt > type:
bcdedit | find "osdevice"
(Look for the partition drive letter)
Type: chkdsk /b /v W:
(replace the letter W with the partition drive letter)
Reboot
Allow the chkdsk switches to run overnight.
Then run:
https://www.tenforums.com/attachment...kfromevent.bat
Post a share link into this thread using one drive, drop box, or google drive.
After removing all RAM modules and reseating one module run:
https://www.tenforums.com/attachment...p_plus_log.bat
Post a share link into this thread using one drive, drop box, or google drive.
-
New #15
It would have been the 13th of March
Sorry for the late reply, life got in the way. I did this and the partition letter was E even though it was on the C drive. Ran the chkdsk and while it took longer than before it still wasnt an overnight process. It was maybe 30min long.Boot to a Windows Media Creation Tool (MCT) flash drive > Windows Recovery Environment (RE) > command prompt > type:
bcdedit | find "osdevice"
(Look for the partition drive letter)
Type: chkdsk /b /v W:
(replace the letter W with the partition drive letter)
Reboot
Allow the chkdsk switches to run overnight.
Then run:
https://www.tenforums.com/attachment...kfromevent.bat
Post a share link into this thread using one drive, drop box, or google drive.
Here's a .zip of the chkdsk results
I didnt have the time to run tests on all 4 sticks twice each so I managed to do a full test on each stick once but got zero failures. Here is a .zip with the memtest86 test results for all 4 sticks.After removing all RAM modules and reseating one module run:
https://www.tenforums.com/attachment...p_plus_log.bat
Post a share link into this thread using one drive, drop box, or google drive.
I gotta ask what is the purpose of all of this? If I installed new RAM and all the issues I was having have gone away wouldn't that explain the source of the problems that it was RAM and not the motherboard?
-
New #16
Today is Monday March 27, 2023.
The new chkdsk reports were ran two weeks ago.
So there were no new chkdsk reports.
All of the Memtest86 reports displayed the same serial number 200771804203682.
The results were not able to be seen for each RAM module with their different serial numbers.
Quote
Related Discussions
