Solved BSOD whenever putting computer to standby

[fuddlestick]

So starting I think yesterday or so, whenever I put my computer on standby mode, it shuts down. When I turn it back on, I get a windows has shutdown improperly message and the thing says Blue Screen.
I standby by closing my lid so I tried pressing the standby button once and turning it on and that didn't seem to have any problems.

I read some of the forum threads and tried to analyze the debug myself and the error is the same, and still is: NT Kernel & System. The ntoskrnl.exe file seems to be causing it. So I restored important Windows files using Samsung Recovery Solution 5. But the problem is still there.
(Is the only solution reinstalling my OS?)


I have a i5 2.3GHz processor
4GB RAM
Windows 7 Home Premium K 64bit

 

[fuddlestick]

Bump?

 

[Vir Gnarus]

I'm not sure what Samsung Recovery Solution is. I assume it's a recovery partition that's used to reset everything back to factory defaults. Am I correct in this? What exactly did it say it will accomplish?

Anyways, none of the crashdumps are inconclusive, and I cannot debug them further as they're just minidumps. The pattern does seem indicative of a driver-based issue, however, so we'll will start approaching it in that direction.

First, let's start with a couple drivers I did see in the crashdumps that were somewhat related to the crashes. The first is the Intel Graphics Driver, which is dated back in July 26, 2011. You'll want to find an update for this on the Samsung website when available. The other is some network filter driver for AhnLabs AV. You may wanna try and update it if available.

With that all done, if the problems still occur, your next step is to turn on Driver Verifier. Follow the instructions. When you get to the part where you select which checks to use, do not select IRP Logging, Force Pending I/O Requests, and Low Resource Simulation. Select the rest. Restart after everything is setup. If you start getting into a BSOD startup loop, press F8 at startup before Windows logo pops up to go into Boot Menu and select Safe Mode, then turn Driver Verifier off there.

Keep Driver Verifier on until you experience a few crashes. Then send us the crashdumps.

 

[fuddlestick]

Thank you for your help

The Samsung Recovery Solution is kind of like the OS CD they usually give you with the computer. It can recover Windows files, data files, reinstall all of Windows (at least this option says deletes all things inside the Windows Drive and reinstalls).
What I did was the simple recover, which says "Keeps the data inside the Windows Drive, but quickly recovers the crucial Windows files"

The computer uses NVIDIA® GeForce® GT 520MX Graphics, but just in case I still updated the Intel HD graphics card.
The AhnLabs AV is a antivirus program (least I thought) that I had to install to use online banking (Koreans have so much useless security) and I had no idea how to update that really...

I just did standby twice without the lid and twice with the lid...It died on me one out of four :/

So I did the driver verifier, following the post and your directions.
I got caught in a BSOD loop, so I crashed it two more times. and because I forgot for a moment how to get into safe mode, it crashed couple more times

But now that I check the log there's only one from the driver verifier.. I uploaded that.

 

[writhziden]

I don't see the crash with Verifier enabled. Are you sure you uploaded it?

 

[fuddlestick]

Woah I swear I did... I'm so sorry!
Just attached it. Lately what I've been doing is just using hibernate. That seems to work around 80% of the time I think...

 

[writhziden]

Verifier enabled crash indicates your ESTsoft Corp ALYac Security software driver as the cause. Uninstall the software. If you need it, re-install it again. It may just be a corrupted install.

If you are using ALYac Fast & Light Security Software, it is not among those listed for Windows 7: Consumer security software providers and may not work well with Windows 7. Windows 7: Consumer security software providers

You may consider replacing it with Microsoft Security Essentials - Free Antivirus for Windows.

 

[fuddlestick]

Thank you a ton! I think you found the problem!

 

[writhziden]

No problem. Make sure to disable Verifier or you will get false positive crashes still.

Glad to see the thread marked solved.

 

[fuddlestick]

Haha I had to disable it right away because it got caught in a BSOD loop
How'd you figure out it was ALYac though from the dump files I gave you?

 

[writhziden]

An ALYac driver was blamed in the crash.

Probably caused by : [B][COLOR="Red"]EstRtw.sys[/COLOR][/B] ( EstRtw+14e49 )

EstRtw.sys

Ah, I see why Verifier caused your system to get stuck in a restart loop. You have Daemon Tools installed. Daemon Tools does not seem to cause any problems when Windows is run normally, but the driver dtsoftbus01.sys that it contains was not developed properly and causes issues when it is enabled within Verifier. We often recommend removing Daemon Tools before proceeding with Verifier to prevent the false positive it creates.

 

[Vir Gnarus]

Daemon Tools drivers should be kept up to date as much as possible, or you may need to find an alternative for it if it keeps bugging out.

Daemon Tools drivers will also cause a reboot loop if you have Force Pending I/O Requests check selected for DV.

 

[fuddlestick]

Wow thank you for all the answers! :]
Hopefully if I have problems in the future I can figure it out on my own without taking your guys' time!

Thanks!