Random BSODs since heat wave

[Swennet]

Hello,

I've been having random BSOD since a heat wave struck where I live. At first I thought it was just overheating, but later I've started suspecting there was an underlying problem with my PC. Mostly because when I check my temps in SpeedFan they're not abnormal.

CPU ~50 C
GPU ~50 C
Hard Drives ~30 C

Right before the BSOD occurs my screen gets artifacts for a split second. The type of Error that is displayed on the BSOD also seems to change.

I hope you guys can help me either reassure me that it's simply overheating that's causing these BSODs or if there is a defect in my hardware.

I have attached a DM Log Collector to this post.

Thank you for helping

EDIT: Since posting this thread no BSOD has occurred, but my PC now freezes randomly (usually when I have a youtube video + a Java application open) The screen still displays everything that was on screen before it froze. I have to manually reset my PC before something happens.

 

[Arc]

Heat wave.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. Take a camera snap of the memetst86+ window before closing the program and let us see it.
_______________________________________________

BugCheck 3B, {c0000046, fffff80002ebd7fc, fffff88007e37720, 0}

Probably caused by : cdd.dll ( cdd!CDDMULTISURFLOCK::vLockShadowW+352 )

Followup: MachineOwner
---------

BugCheck 50, {ffffbf801d9199b8, 1, fffff80002e94be0, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KeAcquireGuardedMutex+0 )

Followup: MachineOwner
---------

 

[Swennet]

Thank you very much for your reply. One of my sticks gave errors almost immediately, after which memtest crashed and my PC rebooted. I will RMA these parts.

Thanks again!

 

[Arc]

Memtest86+ crashed and PC rebooted?

It seems to be a deeper issue than a memory failure, it sounds like memory controller failure.

Anyway, see how the replacement RAM sticks work there.

 

[Swennet]

Memtest86+ crashed and PC rebooted?

It seems to be a deeper issue than a memory failure, it sounds like memory controller failure.

Anyway, see how the replacement RAM sticks work there.

I thought so as well, possibly my DIMM slots being broken or my motherboard failing. For now, I'm using the 1 RAM stick that didn't gave me any errors and my PC works fine.

I think I will test the working stick in all of my slots to see if that gives me any errors. The broken RAM stick gave errors in 2 separate slots so far, so I'm pretty sure that one is actually broken.

I will update this thread later with the results. Thank you very much for your help so far.

 

[Arc]

Now your test results give a sense that it is a RAM module that is failing.

So dont use that one. Things should go fine.