BSOD recovering from sleep with Samsung EVO 840

[j0ker]

Hi!

So the recent change I've made which I think is the responsible for this problem is the 512GB SSD Samsung EVO 840. I've been experiencing this BSOD / crash reboot only when waking up the computer from sleep (which is very common in my workflow, bummer).

When it reboots by itself, starting windows pops up the classical "Window has recovered from an unexpected shutdown" with this text:

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1034

Additional information about the problem:
  BCCode:	f4
  BCP1:	0000000000000003
  BCP2:	FFFFFA800C310B30
  BCP3:	FFFFFA800C310E10
  BCP4:	FFFFF80003792DB0
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

Files that help describe the problem:
  C:\Windows\Minidump\100614-15615-01.dmp
  C:\Users\Neithan\AppData\Local\Temp\WER-19546-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I haven't had any problem besides this, I hope it's easy to fix :\

I attach that *.dmp.

Thanks!

 

[Arc]

Hi j0ker.

So the recent change I've made which I think is the responsible for this problem is the 512GB SSD Samsung EVO 840.

What you stated there is true .... a stop 0xF4 is basically a storage related BSOD.

Make it sure that the SSD is running with the latest firmware.
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

SSDs perform well with the newest version of the BIOS. As your BIOS is old (0402), get Version 1502 from ROG - RAMPAGE III EXTREME - ASUS

Also, follow http://www.sevenforums.com/tutorials/778-power-plan-settings-change.html .... When you are on Step 5. (B), Set the Disc to "never" go to sleep. It is designed in this way that some SSD are not for sleep.

Let us know for any further BSOD.

 

[j0ker]

Hi j0ker.

So the recent change I've made which I think is the responsible for this problem is the 512GB SSD Samsung EVO 840.

What you stated there is true .... a stop 0xF4 is basically a storage related BSOD.

Make it sure that the SSD is running with the latest firmware.
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews

SSDs perform well with the newest version of the BIOS. As your BIOS is old (0402), get Version 1502 from ROG - RAMPAGE III EXTREME - ASUS

Also, follow http://www.sevenforums.com/tutorials/778-power-plan-settings-change.html .... When you are on Step 5. (B), Set the Disc to "never" go to sleep. It is designed in this way that some SSD are not for sleep.

Let us know for any further BSOD.

Before doing anything, I've noticed that these BSOD are intermitent (always after wake up though).

My energy setting is already how you said it should.

I'm a bit afraid of updating the BIOS, as it sounds it could get ****ed and I can't skip a day without this computer. Is it risky?

Similar worries with the SSD firmware, particularly after reading:

the first step before performing any firmware update should still be to backup important data on your drive. Errors and faults can happen that may render your data inaccessible. Sometimes, updates are destructive, but in those cases users will be warned.

Thanks for your help.

 

[Arc]

The BIOS update is really risky. If the process is interrupted then it will convert to the motherboard to a brick only.

But SSD firmware update is not that risky ... at least nobody reported something like that till date. Still if you are afraid, you may backup your data before doing the update.

I am seeking for more help in your thread .... if anyone more experienced can handle your issue.

 

[j0ker]

An update on this thread:

Yesterday night while I was working in Illustrator my computer freezed up and shortly after rebooted itself with no visible errors the first time, and a BSOD (with the 0xF4 thing) the second time. I lost almost 2 hours of work

According to Samsung Magician I have the latest SSD firmware. So, unless there's something else I can do, the last thing to try is updating the BIOS as you said?

One thing though:

I think I tried setting AHCI in the BIOS and then it didn't recognize the device or something, can't remember for sure. Should anything be done about that warning?

There must be something else...

 

[Arc]

Can you post it following the Blue Screen of Death (BSOD) Posting Instructions? Probably the data will elaborate the situation a bit more.

 

[j0ker]

Sure, here it is.

Just now, before entering the forum (after waking up the system) yet another BSOD on my face, this time it wasn't the usual 0xF4 though. It said something about win32k.sys. The dump should be in the ZIP i'm uploading.

Thank you!

 

[Arc]

It is a different thing.

[COLOR=Red]BugCheck 50[/COLOR], {fffff900c30f9608, 0, fffff960002a1d12, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+201d12 )

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

A stop 0x50 is usually a memory error. Either the physical memory is not doing its job properly or any driver is passing bad information to the memory. But the crash dump is not very precious about the probable cause. Let us check both the possibilities one by one.

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.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.