BSOD with NTOskrnl.exe as common factor

I have been receiving several Blue screens with the ntoskrnl.exe as a common error, I have included zipped files and screen shot of CPU-id. This is a custom built pc and has been having this problem for a few months, I previously was having the same problem finally just re installed Windows 7 64 bit to get rid of it but it is back.

Some drivers may be out of date but i don't think any are very old. Would like help to search for solution, memory is not the problem, I have replaced memory sticks and the system is still getting the crashes. I get about one crash every day or so but it sometimes skips a day or two, usually not more than two a day for the past two months.

Thanks for anyone who helps.



Last edited:


Fantastic Member
Microsoft Community Contributor
Your BIOS dates from 2010. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

You only have 103 updates after SP1 - most systems have 130 to 140. Please visit Windows Update and get ALL available updates.

You have both AVG and Trend Micro installed - please remove all but one anti-virus and all but one firewall. Using more than that will cause the programs to fight each other for control of the system - and will cause problems and may even let virus' get through.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). I strongly suspect that this hold true for Win8 systems also.
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

nvsmu.sys Mon Jun 29 03:36:37 2009 (4A486F05)
nVidia nForce System Management Controller (nVidia nForce chipset driver)

nvBridge.kmd Tue Jul 14 15:26:48 2009 (4A5CDBF8)
nVidia Compatible Vista Kernel Mode Driver (likely belongs to nForce chipset drivers)

Must be removed:
sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)

The following is for informational purposes only.
[font=lucida console]**************************Sat Jan  5 21:49:25.499 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010513-18314-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:32:07.779[/B]
Probably caused by :[B]hardware ( fileinfo!FIStreamGetInfo+11f )[/B]
BugCheck [B]50, {ffffffff80000048, 0, fffff800039cb04a, 5}[/B]
BugCheck Info: [url=]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Arg1: ffffffff80000048, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800039cb04a, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000005, (reserved)
PROCESS_NAME: [B]svchost.exe[/B]
  BIOS Version                  1403   
  BIOS Release Date             08/20/2010
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
[font=lucida console]**************************Sat Jan  5 21:49:25.499 2013 (UTC - 5:00)**************************
[COLOR=RED][B]nvsmu.sys                   Mon Jun 29 03:36:37 2009 (4A486F05)[/B][/COLOR]
[COLOR=RED][B]nvBridge.kmd                Tue Jul 14 15:26:48 2009 (4A5CDBF8)[/B][/COLOR]
ASACPI.sys                  Wed Jul 15 23:31:29 2009 (4A5E9F11)
[COLOR=RED][B]sptd.sys                    Sun Oct 11 16:55:14 2009 (4AD24632)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvmf6264.sys                Thu Aug 12 07:46:06 2010 (4C63DEFE)
ElbyCDIO.sys                Thu Dec 16 17:58:13 2010 (4D0A9985)
speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)
RimSerial_AMD64.sys         Wed Jul  6 19:20:01 2011 (4E14EDA1)
tmtdi.sys                   Mon Aug 22 11:21:54 2011 (4E527412)
btwl2cap.sys                Sat Aug 27 18:58:52 2011 (4E5976AC)
btwavdt.sys                 Thu Mar  1 16:45:18 2012 (4F4FEDEE)
btwrchid.sys                Thu Mar  1 16:46:08 2012 (4F4FEE20)
btwaudio.sys                Wed Mar 28 18:34:32 2012 (4F7391F8)
btwampfl.sys                Thu Mar 29 14:51:21 2012 (4F74AF29)
PxHlpa64.sys                Tue Apr 24 13:26:29 2012 (4F96E245)
AnyDVD.sys                  Tue May  1 19:35:22 2012 (4FA0733A)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
tmnciesc.sys                Thu Jul  5 23:35:43 2012 (4FF65D0F)
tmevtmgr.sys                Thu Jul 12 06:28:04 2012 (4FFEA6B4)
tmcomm.sys                  Thu Jul 12 06:28:08 2012 (4FFEA6B8)
tmactmon.sys                Thu Jul 12 06:28:19 2012 (4FFEA6C3)
TMEBC64.sys                 Fri Aug 24 01:04:26 2012 (50370B5A)
tmeevw.sys                  Sat Aug 25 01:04:31 2012 (50385CDF)
kbfilter.sys                Tue Sep  4 05:19:41 2012 (5045C7AD)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
TMEBC64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
kbfilter.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

Thanks for the help, I will look at removing/updating drivers but I have a few questions, the AVG is not on this system, Installing Trend Micro checks for conflicting programs but even then I do not see AVG in Easy Cleaner or installed programs in control panel. I also do not have Daemon tools or Alcohol installed, the closest thing I can think of would be NEro or one of the SlySoft programs like AnyDVD or Clone DVD.

I iwll update and remove sptd.sys and see if things continue with blue screens, thanks.



Fantastic Member
Microsoft Community Contributor
I saw the AVG in the MSINFO32 report (Software Environment...Program Groups). It doesn't appear to be involved in the memory dumps - but it can't hurt to attempt to remove it with this free tool: AVG | Download tools and utilities

The sptd.sys driver must go as it's (IMO) the most likely cause of the BSOD's. In the past there were known issues with uninstallers leaving the sptd.sys driver behind (and loaded) when uninstalling Daemon Tools/Alcohol % software.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.