BSOD Screen on Samsung RV520

BSOD Appearing at times
Windows 7 Ultimate x64
It was Windows 7 Home basic. I Switched to Windows 7 Ultimate last week using Windows Anytime upgrade key.

Laptop is 7 months old
MODEL : SAMSUNG NOTEBOOK RV520
CPU : Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz
MOTHERBOARD : SAMSUNG ELECTRONICS CO., LTD. RV420/RV520/RV720/E3530/S3530/E3420/E3520
TOTAL MEMORY : 3.00 GB USABLE MEMORY : 2.92 GB
HDD : SAMSUNG HM321HI
SOUND CARD : (1) Realtek High Definition Audio (2) Intel(R) Display Audio
GRAPHICS CARD : Intel(R) HD Graphics Family
OS : Microsoft Windows 7 Ultimate x64 SP1

Please spot out the problem :)
Thanks in Advance :)

I am often seeing problems in the syslog related to sptd.sys. This is the advanced drive emulation driver for Daemon Tools, and if Daemon Tools is trying desperately to use it when it is constantly crashing and failing to load like what I'm seeing in the syslog, then it may be creating these issues. You will want to uninstall Daemon Tools, go to C:\Windows\System32\drivers\ and remove sptd.sys, and then reinstall the latest Daemon Tools if you feel it necessary to continue using it. Note that the sptd.sys file - which is known to bug out a lot - is not required for Daemon Tools to work, only when dealing with emulating certain security mechanisms.

Other then that, everything is rather inconclusive. You should turn on Driver Verifier and await any further crashes to send us the crashdumps. In addition to what the article says about turning off Low Resource Simulation, also do not check Force Pending I/O Requests and IRP Logging.

To supplement Vir Gnarus's good advice, please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

Vir Gnarus said:

I am often seeing problems in the syslog related to sptd.sys. This is the advanced drive emulation driver for Daemon Tools, and if Daemon Tools is trying desperately to use it when it is constantly crashing and failing to load like what I'm seeing in the syslog, then it may be creating these issues. You will want to uninstall Daemon Tools, go to C:\Windows\System32\drivers\ and remove sptd.sys, and then reinstall the latest Daemon Tools if you feel it necessary to continue using it. Note that the sptd.sys file - which is known to bug out a lot - is not required for Daemon Tools to work, only when dealing with emulating certain security mechanisms.

Other then that, everything is rather inconclusive. You should turn on Driver Verifier and await any further crashes to send us the crashdumps. In addition to what the article says about turning off Low Resource Simulation, also do not check Force Pending I/O Requests and IRP Logging.

Thanks ! By the Way,How do I get to the Low Resource Simulation ? And Uncheck Force Pending I/O Requests & IRP Logging ?

writhziden said:

To supplement Vir Gnarus's good advice, please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

Thank You !

vishnu619 said:

Vir Gnarus said:

I am often seeing problems in the syslog related to sptd.sys. This is the advanced drive emulation driver for Daemon Tools, and if Daemon Tools is trying desperately to use it when it is constantly crashing and failing to load like what I'm seeing in the syslog, then it may be creating these issues. You will want to uninstall Daemon Tools, go to C:\Windows\System32\drivers\ and remove sptd.sys, and then reinstall the latest Daemon Tools if you feel it necessary to continue using it. Note that the sptd.sys file - which is known to bug out a lot - is not required for Daemon Tools to work, only when dealing with emulating certain security mechanisms.

Other then that, everything is rather inconclusive. You should turn on Driver Verifier and await any further crashes to send us the crashdumps. In addition to what the article says about turning off Low Resource Simulation, also do not check Force Pending I/O Requests and IRP Logging.

Thanks ! By the Way,How do I get to the Low Resource Simulation ? And Uncheck Force Pending I/O Requests & IRP Logging ?

Click the link mentioned in my post for Driver Verifier. It'll have an article that will describe all the steps you need to set it up. I'm just saying that one of the steps mentioned in the article is to check every option in Driver Verifier except Low Resource Simulation. What I am saying is that you should also make sure not to check Force Pending I/O Request and IRP Logging as well. All three of these are no-nos, so check anything else except them.

Again Crashed !
attached NEW Dump Files And Resource and perfomance report and error screen message

It showed up another ntfs error, which isn't all that conclusive. However, it does suggest possibly some sort of disk corruption.

You'll want to run SFC Scan. In addition to this, after it is done and you are still at the command prompt, you'll want to run "chkdsk /f /r" or "chkdsk /r". If for some reason it complains and won't run, you can go into Windows, enter Computer, right click the Windows disk and go to properties, navigate to Tools tab, click the "Check Now...", select both options and then start. It'll state you need to restart in order to have it run. Before you restart the PC, do the same process and setup a check for all your currently existing drives on your PC. Then when you restart at bootup it'll run through them. It'll take a while, so keep that in mind.

Understand this issue can also come from when nonpaged pool memory gets very low. Nonpaged pool is memory for processes that can only exist on your RAM and cannot be transferred over to the paging file on your disk in the event of low memory conditions. I noticed that when you took the JCGriff Report it mentioned that you had 3GB of RAM on your PC but only 1.3GB was available at the time. Make sure you don't have any processes that are slurping up lots of memory, and if worse comes to worse, you'll just have to cough up 20 bucks for an extra 4GB of RAM.

Vir Gnarus said:

It showed up another ntfs error, which isn't all that conclusive. However, it does suggest possibly some sort of disk corruption.

You'll want to run SFC Scan. In addition to this, after it is done and you are still at the command prompt, you'll want to run "chkdsk /f /r" or "chkdsk /r". If for some reason it complains and won't run, you can go into Windows, enter Computer, right click the Windows disk and go to properties, navigate to Tools tab, click the "Check Now...", select both options and then start. It'll state you need to restart in order to have it run. Before you restart the PC, do the same process and setup a check for all your currently existing drives on your PC. Then when you restart at bootup it'll run through them. It'll take a while, so keep that in mind.

Understand this issue can also come from when nonpaged pool memory gets very low. Nonpaged pool is memory for processes that can only exist on your RAM and cannot be transferred over to the paging file on your disk in the event of low memory conditions. I noticed that when you took the JCGriff Report it mentioned that you had 3GB of RAM on your PC but only 1.3GB was available at the time. Make sure you don't have any processes that are slurping up lots of memory, and if worse comes to worse, you'll just have to cough up 20 bucks for an extra 4GB of RAM.

i will be running the scan and posting the results soon..
and how do i find out the processes that are taking up lots of memory ?

You can use Task Manager to do that, there should be a column for how much is being used. In addition, in Task Manager where the graphs are for Performance there should be a button for Resource Monitor, which a very powerful tool to monitor research usage. If you start seeing overall usage getting close to 2.5GB, it's time to save up for some memory (which is awfully cheap nowadays).