BSOD after bios update - happens when exiting hibernation

[careh]

A month ago I updated to an Intel SSD 335 series 240 GB from the stock 320 GB disk. I don't recall seeing any issues after I did that upgrade.

2 weeks ago I updated the BIOS from the factory version 1 to the current version 1.08 thinking it would fix a failure to charge issue I was having with a new battery I had purchased. It turned out the battery failure to charge issue was the battery was the wrong voltage -10.1 volts instead of 14 volts.

So I got the 'right' 14 volt battery and the failure to charge issue went away - however now when it comes out of hibernation I get BSOD. I will also get BSOD if I let the PC go into hibernation following x minutes of inactivity. I turned hibernation off for inactivity - so that gets around that problem - however |I still have the BSOD if/when I close the cover and it hibernates.

 

[Arc]

Hi careh.

Can you uninstall TrueCrypt, as a test? Does it behave the same even without truecrypt installed?

Also .....

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before uploading another zip.

 

[careh]

I removed truecrypt and installed the minidump from steps 2 and 5 into the registry.

I then closed the laptop lid - opened it - and Pow!! BSOD. I went into C:\Windows\MiniDump but it was empty. I don't know where to look for %SystemRoot%\Minidump but if you meant C:\Minidump - then that folder does not exist.

I will try another computer reboot and then see if the minidump file gets created.

 

[careh]

I did a shutdown / power up - let it settle down after the reboot, close the lid, open the lid - BSOD - and again no file in minidump folder. Attached is the latest zip file.

 

[Arc]

I removed truecrypt and installed the minidump from steps 2 and 5 into the registry.

What you have actually done? What was suggested was .... Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

 

[careh]

Yes, I downloaded Create_Minidump_on_BSOD.reg and ran it.

I removed truecrypt and installed the minidump from steps 2 and 5 into the registry.

What you have actually done? What was suggested was .... Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

 

[Arc]

I am/was wondering what "steps 2 and 5" may mean.

Anyway, take a camera snap of the BSOD screen and upload it. That will let us see the bugcheck code and the parameters, at least.

 

[careh]

Attached is a screen shot from a couple of weeks ago.

 

[careh]

And here are a couple from just now

 

[Arc]

So it is a CRITICAL_OBJECT_TERMINATION (0xF4). From the first parameter, it appears that a process is the terminating object.

Stop 0xF4's are storage related.

Go to http://www.sevenforums.com/tutorials/778-power-plan-settings-change.html .... when at Step 50B., set the Hard Drive to never go to sleep.

View attachment 332299
​

Also 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 and ETDctrl.
5. Apply > OK
6. Accept then restart.

Make it sure that the SSD is running with the latest firmware.

How to Upgrade Intel SSD Firmware | StorageReview.com - Storage Reviews
​

Let us know the results.

 

[careh]

The disk was already set to 'never sleep'... I had put in that change last week when I first found it mentioned on this site.

I turned off all in startup except ETDctrl (ELAN Smart-Pad) and Microsoft Security Client ... which I surmise is the anti-virus? Seems to be as M/S Security Essentials is running.

I closed the lid, opened it and got BSOD.



The Intel SSD 335 series 240 GB is at firmware version 335u and Toolbox version 3.2.3 which is the latest firmware. Of note - that firmware was released on July 22, 2014.

I tried a quick diagnostic scan in Intel toolbox and it completed successfully.

In Intel toolbox system tuner it shows:
Superfetch/Prefetch Feature is optimised
ReadyBoost Service not found
Device Initiated Power Management (DIPM) Current storage driver does not support DIPM settings. Consider changing to another storage driver compatible with your system
Defragmenter (none).

C:\Windows\Minidump is still empty....
I saw in Control Panel / System and Security / System / Advanced System Settings / System Properties / Advanced / Startup and Recovery / Settings that the 'small dump directory' is set to %SystemRoot%\Minidump Where would I find the SystemRoot - like is that C:\ or some other location?

I attached the latest log file.

 

[Arc]

The disk was already set to 'never sleep'... I had put in that change last week when I first found it mentioned on this site.

In that case the disc should not fail during wake-up.

A stop 0xF4 is generally a storage related issue. In your case it is happening during wake up from sleep; that generally means that the sleep configuration is causing some issues there, as some of the SSDs are supposed to not go to sleep.

Next big opportunity is that the Acer ACPI utility is causing the issue. To deal with it, I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

The crash dumps are not being recorded because the disc is not accessible when the crash occurs.

 

[careh]

Thanks - I will give that a try.

I can live with the problem for the next while now that I know how the BSOD occurs which is when it fails to come out of hibernation / sleep).

Long term though I think I will also try swapping back in the original hard disk and see if the problem is still there. Another avenue is to sell the unit off while it still has some residual value - BSOD and all.

Thanks for your help on this.

 

[Arc]

I think I will also try swapping back in the original hard disk and see if the problem is still there.

That will be a worthy attempt.