BSOD when launching steam game

Malneb said:

Because Op OCd the ram and most likely the other parts of the PC couldn't this suggest that Power Transitions are at play? Like unless they full tit on all cores all the time if they are using p states then that could explain ramping the cores when loading a game and then the memory bugs out?

ubuysa said:

Absolutely.

I'd go even further, buy your RAM in a pack. If you need, for example, four 16GB sticks, then buy a pack of four 16GB sticks. Do not buy four separate 16GB sticks. RAM in a pack is almost certainly a matched set, individual sticks may not be. With DDR5 RAM in particular, and the sorts of clock speeds at which that RAM can run, you really want all your RAM chips to come from the same slice of silicon....

F22 Simpilot said:

Yeah, I had a lot of issues with bad RAM myself, actually an odd RAM stick was the issue (long story. See below).

Run Memtest86 with all four (default) options overnight.

Any errors? If so, now test one stick at a time until you nail the bad stick/s.

In my case it was not really a bad stick, but a combination of using this one stick with the others that seemed to have caused an incompatibility issue and thus my BSODs and other crap. So in my case all RAM sticks checked out in Memtest86, but upon further investigation I found out that if I used a certain stick that was the same as the others except for a few different numbers on the serial number it was causing the other sticks an issue. So, all my sticks of RAM are the exact same, except one stick had a slightly different serial number. And for some reason that one and only stick, even though it was the same model, was causing issues with the other sticks of RAM.

Very peculiar and interesting issue that was and I don't ever recall anyone having the same issue I've seen posted on the Internet. ALL the RAM sticks were the same model! Just one stick had a slightly different serial number. I don't know if that meant something different in the manufacturing process or what. So because of that I'm now down to 12GB instead of 16GB. I need to buy a whole new compatible set of RAM if I want my 16GB back. I don't risk buying just the one stick and having a serial number mismatch again.

Word to the wise: buy all your RAM at once...

zbook said:

The tuneup plus yesterday was seen.
Today it displayed: Sorry, the file you have requested does not exist.

Please boot to the Windows 10 MCT > Troubleshooting > command prompt

Type:
C:
dir
D:
dir
E:
dir

Identify the Windows drive letter.



chkdsk /b /v W: (change W: to the Windows drive letter > run overnight while sleeping)
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)


Reboot as needed.


Later run:
https://www.tenforums.com/attachment...kfromevent.bat

Post a share link.

I deleted the file thinking you already seen it. I can upload again if you want to take another look.

I recently installed a new SSD and then cloned by existing SSD to the new SSD so some corruptions could have happened.

Regarding the ram, I will test this weekend and report back. If I have issues, I can buy a new ram pack. I am using ddr4 3600 Mhz, any recommendations on cheap work horse ram? please do link
thanks

To review results and follow the thread the share links are viewed.

Please repost the prior Tuneup / V2 results into the newest post.

Also post new script results for Tuneup / V2 / Get memory configuration

https://www.tenforums.com/attachment...figuration.bat

Batch files for use in BSOD debugging

When troubleshooting has completed share links can be deleted.

MisterEd said:

The default speed of DDR4 is 2133MHz. All RAM that is sold with a higher speed is considered overclocked. The 3200MHz RAM you have is overclocked but has been thoroughly tested by the manufacturer to run stably at the speed it is sold as. By overclocking the RAM to 3600MHz you are overclocking it even further which risks being unstable. You are risking BSODs but will also slowly corrupt the data on your drives.

I suggest that you forget about testing your RAM and return it to its default 3200MHz and see if that is stable. If you want 3600MHz RAM and your computer is capable of running it stably then do yourself a favor and buy 3600MHz RAM.

I agree this makes sense too, because it is a possibility that when you OC the computer that instability happens.
When the manufacture sells their parts they are tested for those settings. Timings would be at play too and you might get a higher speed to work but you might need to make the timings slower. OC ram from manufacture is already set to what they think is reliably to market if you go over that then it becomes a smaller margin you really have to dial in the computer to the T and XMP is going to be less warranted you would want to do it manually.

QC control is pretty good i think on ram there would be clear cut signs right away if there was some issue at manufacture especially bit flipping and other issue, if the problem only presents after OC over the rated settings then that is grounds for issues.

setting to defaults and testing thoroughly like mentioned by others would be the right line of action if you still have issues then it would be down to the ram being actually bad.

zbook said:

To review results and follow the thread the share links are viewed.

Please repost the prior Tuneup / V2 results into the newest post.

Also post new script results for Tuneup / V2 / Get memory configuration



Batch files for use in BSOD debugging

When troubleshooting has completed share links can be deleted.

Hello,

Thank you zbook for all your help. I re uploaded all files into a folder and here is the link

Update your browser to use Google Drive, Docs, Sheets, Sites, Slides, and Forms - Google Drive Help

Thank you to others pointing out about the ram OC, I am going back to my default 3200 Mhz so hopefully no more issues.

Please let me know if you find anything in the logs @zbook

I wouldn't rule it out Ubusya and others pointed out that the issue is suggesting bad ram but OCing the ram is going to bias the situation. You could just need more voltage to the ram or something else needs to be tweaked but that is several areas to cover.
XMP is a baseline if that is what you were doing really you need more granularity than that by doing it manually.

Set the ram to default and what ever other OC you did in the computer and do some tests with memtest like mentioned and then test by gaming. if it comes up ok then you know it was just a bad OC i would test this over a few days at stock settings though where you are doing heavy work loads.

I also never looked at any of the logs so i am just generalizing here.

Malneb said:

I wouldn't rule it out Ubusya and others pointed out that the issue is suggesting bad ram but OCing the ram is going to bias the situation. You could just need more voltage to the ram or something else needs to be tweaked but that is several areas to cover.
XMP is a baseline if that is what you were doing really you need more granularity than that by doing it manually.

Set the ram to default and what ever other OC you did in the computer and do some tests with memtest like mentioned and then test by gaming. if it comes up ok then you know it was just a bad OC i would test this over a few days at stock settings though where you are doing heavy work loads.

I also never looked at any of the logs so i am just generalizing here.

ok, thanks, yeah I am going back to defaults

1) Please run these chkdsk /b /v switches on all drives using the syntax:


chkdsk /b /v D: , chkdsk /b /v E: , chkdsk /b /v F: etc.

Repeat chkdsk /b /v C: after completing the switches on the other drives.


C:\WINDOWS\system32>chkdsk /b /v
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 as needed.



2) Post images of disk management:
How to Post a Screenshot of Disk Management


3) Post a new Tuneup plus after completing the above steps (1 - 2).


4) Post a new :
https://www.tenforums.com/attachment...kfromevent.bat

after completing all of the above steps (1 - 3).


5) Post a new V2 after completing all of the above steps (1 - 4)

Code:

              unneeded link ($FILE_NAME: "35D868~1") in index "$I30" of directory "\Users\tim\AppData\Roaming\Opera 
              Software\Opera Stable\Code Cache\js <0x2,0x3b382>"
              was not able to send command for self-healing due to lack of memory.

Code:

              The file reference 0x1e000000025b28 of index entry 35D868~1 of index $I30
              with parent 0x3b382 is not the same as 0x13d000000025b28.
              Deleting index entry 35D868~1 in index $I30 of file 3B382.
              "chkdsk /scan" is aborting due to self-healing command failure: 0xc0000102

Code:

            CHKDSK discovered free space marked as allocated in the volume bitmap.
              
              Windows has made corrections to the file system.

Code:

Memory Modules:

Tag               BankLabel Capacity(GB) Manufacturer PartNumber       Speed
---               --------- ------------ ------------ ----------       -----
Physical Memory 1 BANK 1              16 G-Skill      F4-3200C14-16GVK  3600
Physical Memory 3 BANK 3              16 G-Skill      F4-3200C14-16GVK  3600


Total Memory:
32GB

Total Memory Slots:
4

Used Memory Slots:
2

Code:

Windows RE status:         Disabled

Code:

    Disk 0 : HDD. It has 2 partition(s). Model: WDC WD4005FZBX-00K5WB0   
    Disk 1 : HDD. It has 2 partition(s). Model: ST1000DM010-2EP102    
    Disk 2 : SSD. It has 2 partition(s). Model: SHGS31-1000GS-2    
    Disk 3 : SSD. It has 2 partition(s). Model: WDC WDS100T2B0C-00PXH0   
    Disk 4 : SSD. It has 4 partition(s). Model: SHPP41-2000GM