Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Several BSOD, ntoskrnl.exe, aswSP.sys, more.

15 May 2015   #11

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Hi Gina.

Have you uninstalled Avast already, as suggested by Boozad in #2?

If so, let us see any further BSOD after doing it. It will help us to decide our next courses of actions.

My System SpecsSystem Spec
18 May 2015   #12

Windows 7 Home Premium 64bit

Hello Arc, forgive my delay I was going mostly nonstop from Friday to Sunday evening. :-P

I have not uninstalled Avast yet. I barely had time to work on the computer much actually. I was going to wait for Avast to get back with me, but they have not. However I just got their attention on Friday. I have had another BSOD however, and something else interesting.

I rebooted my computer yesterday. It did not give me a BSOD this time. I got a message from Malwarebytes. Screenshot attached. I got a notification that Avast was turned off as well. So my computer booted normally (although slowly) and Avast was turned off when I was fully booted.

I ended up running a few rootkit removers. None were found. One note of interest however: when I ran Avast's aswmbr, my computer gave a BSOD and spontaneously rebooted almost as soon as Avasts's aswmbr began scanning. When I booted again, I started the scan once again and it took all day to run, but just seemed to sit there for a couple of hours. I finally just shut it off. I do not have a dump file for this BSOD, at least BlueScreen Viewer doesn't bring up a dump for yesterday.

Today I got a BSOD on startup. Sigh.

Here's quick snips from today's BSOD from NirBlueScreen Viewer.

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: Ntfs.sys


*** Ntfs.sys - Address 0xfffff88001628e20 base at 0xfffff88001618000 DateStamp

If I don't hear from Avast by this afternoon, I am going to uninstall, boot and see what happens. I will install MSE in the interim. I'll get back with you after I do that.

Thanks for helping and for your reply,
My System SpecsSystem Spec
18 May 2015   #13

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

Hi Gina.

If you report any further BSOD, attach the data following the Blue Screen of Death (BSOD) Posting Instructions otherwise we will not be able to see what is going on there. BSview is not any info actually.

And, hope you will follow us, and your next reply will confirm that you have uninstalled Avast and installed MSE. No further suggestion will take you anywhere with the crasher present in your system. I hope you can understand it.

Have a closer look at the dialog provided by MBAM.
Attachment 359541
Take it seriously. Scan the system for possible virus infection with the following programs only, not with Avast or MBAM or even MSE.
I hope you will decide to continue with us. A delay in replying is not a big deal, but a delay in action is.
My System SpecsSystem Spec

18 May 2015   #14

Windows 7 Home Premium 64bit


Finally got some health and time this afternoon. Uninstalled Avast, reboot. No BSOD. Installed MSE. Made the boot cd for Windows Defender Offline. (Had already run TDSSKiller, Sophos Virus Removal Tool, McAfee Rootkit Remover, and what I could of Avasts' tool). I could not create the CD on a different computer, I don't have one accessible. I might have access to one in a couple of days.

I can't find a log file at the stated location on the drive, but it didn't seem to find anything during the Quick scan.

When I booted after changing the boot order, I didn't get a BSOD. The boot time is quicker, but it was a good four minutes by count (from start of reboot) before seeing a hit of desktop, and a few more minutes until I got a usable desktop.

I had made some custom views in Event Viewer. This is the last boot time:

Windows has started up:
Boot Duration : 339959ms little over 5.5 minutes I think
IsDegradation : false
Incident Time (UTC) : ‎2015‎-‎05‎-‎18T18:46:28.718400300Z

The only thing I could find in boot degradation other than
File Name : MsMpEng.exe
Friendly Name : Antimalware Service Executable
Total Time : 92541ms
Degradation Time : 84041ms

was something for my Samsung s6 phone that helps with file transfer. Just installed it a few days ago, so not sure if I need it to load at start up or not. Will take a look at it.:
File Name : Samsung Link.exe
Friendly Name : Samsung Link Service
Version :
Total Time : 8304ms
Degradation Time : 3304ms

So, now what? Any other ideas? I need to look at startups and services again. I've mostly preened the startups, but I am not sure what services I can stop, so not sure what else to do about boot time. BUT, it's much better, and no BSOD after two boots at least!
My System SpecsSystem Spec
19 May 2015   #15

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit

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. It will open the system configuration window
  1. Click on the Start button
  2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window, with the "general" tab selected.
    • Click the "startup" tab. Click "Disable all"
      • Add back the antivirus there. > Apply > OK.
    • Click on "services" tab. Check the "Hide all Microsoft Services"; Click "Disable all" > Apply > OK
  3. Accept then restart.
If the boot time is not improved, try The Boot Time Defrag option using Puran Defrag.
Attachment 359606
Is the boot time anyhow improved after doing those? Let us know.
My System SpecsSystem Spec

 Several BSOD, ntoskrnl.exe, aswSP.sys, more.

Thread Tools

Similar help and support threads
Thread Forum
BSOD caused by aswSP.sys & ntoskrnl.exe CRITICAL_OBJECT_TERMINATION
ive been getting a blue screen of death with these two system files. i googled and said its a problem with avast but ive had it for a while and have had no problems since today crash dump .zip in attachments
BSOD Help and Support
BSOD random most times ntoskrnl.exe+748c0 and ntoskrnl.exe+74ec0
BSOD random, probably under heavy load situations. I dont know how to do. DM log collector file attached many thanks
BSOD Help and Support
BSOD caused by driver (ntoskrnl.exe) /adress (ntoskrnl.exe+72a40)
Got my first blue screen of death tonight, had 2 firefox opened one watching youtube video another browsing internet. After bsod it restarted i login but just black screen with cursor, ctrl alt delete worked so i shut my computer down. Boot up normally after, check my minidump file, bsod cause...
BSOD Help and Support
Random BSOD error driver ntoskrnl.exe (address ntoskrnl.exe+74ec0)
Hey guys so I've been getting some random BSOD errors every few days or so. I usually leave my computer on when I am at work or sleep and either when I come home or wake up my computer is off. So I turn it on and it says that the computer didn't shut down properly when I start up. I downloaded...
BSOD Help and Support
BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys
Hi, to make things easier for you,below is the Bug Check String, Driver, and crash address SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0 MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0 SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:28.
Twitter Facebook Google+