BSOD on Shutdown or restart

Nikilet · Jul 3, 2011

Within the last month or so, I have had three instances of the BSOD when I have restarted or shutdown.

The first two times it was on restart. After the BSOD, it switched to the screen to run the startup repair, but it took forever. Both times I was about to just shut it off at the button when it finally went ahead with the restart.

Tonight I was attempting to just shut the computer down for the night and got it. On its own it switched from the BSOD to running through the normal startup screens, I signed in and the desktop came up. But then the screen went all completely white, switched back to the desktop and all fine from there. Except that I just noticed that my internet icon in the taskbar has a red x through it.

Even though it would appear that the Internet is not functioning, it apparently is since I am online doing this. I wonder why the red x???

Does anyone have any advice for me please?

Vista Home Premium SP2 / 2 GB RAM / 360 GB hard drive / Avast Internet Security 6 / Malwarebytes / Win Patrol / Diskeeper

richc46 · Jul 3, 2011

If you follow these posting instructions, I will be able to give you the best possible help.
If no one else offers constructive help, I will be here to help tomorrow
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Nikilet · Jul 3, 2011

Here are the files you asked for. I must tell you that my Health Report hasn't been reporting accurately for a while. It says there is no anti-spyware or anti-virus, but when I go to my security center everything shows correctly. I was told that this commonly happens and not to worry about it so I haven't.

In order to run that Windows_NT6_BSOD_jcgriff2 file as administrator I had to first place it in a folder. Why is that? I'm sure I never used to have to do this.

32 bit
Vista Home Premium originally installed
OEM
System/hardware I believe nearly 5 years this July
Dell factory reinstall about 1 year ago

richc46 · Jul 3, 2011

I just happen to see your post before logging off, it was easy so here it is.

First the good news. The problem was clearly defined and easy to solve

The Bad News: You have given us only one minidump report. It usually takes a few to give a clear indication of the problem. If you have more BSODs please post all the minidumps that you have

In this situation the cause was your anti virus
Aswsp.sys file description
avast! Antivirus System avast!
self protection module
ALWIL Software

Please uninstall use the uninstall tool at their website.
Replace with Microsoft Security Essentials and Malwarebytes for free scans once a week.
After you are uninstalled, go to search type
cmd
in cmd type
driverquery and make sure that the driver that I mentioned above is not shown.
Your reports do not show that you have any anti virus, this is a known bug. If not using Security Essentials many times it does not show correctly.

Nikilet · Jul 4, 2011

Hi!

First, as to reports not showing that I have any antivirus, this just came about not too long ago. That health report always worked before so something has happened to make it stop working correctly. The bug has developed somewhere along the way because I never had a problem with it before. It worked after I installed Avast because I run it from time to time.

When I booted my computer this morning it again gave me the BSOD. I selected to start normally from the next screen and that went ok -- except the screen did flash to white for a few seconds after the desktop loaded, which is not normal.

Probably you only got the most recent mini dump because I run CCleaner a few times a week. Please see the screenshot of what I have checked for cleaning under System and tell me what I should uncheck in order to maintain the mini dump info.

Also see the screen shots I took this morning of the Windows info box that appeared explaining the BSOD of this morning.

I am going to confer with Avast before I just uninstall this program. Had I heard about this Microsoft Security Essentials earlier, I probably would have tried it before purchasing Avast, but please understand that this program has been working beautifully for me and I just purchased it about 6 months ago. I recently installed the paid version of MBAM. There haven't appeared to be any conflicts, but could that have any bearing?

Thank you for your help!

Nikilet · Jul 4, 2011

Sorry!

I forgot to attach the files. Here they are.

richc46 · Jul 4, 2011

Nikilet said:
Hi!

First, as to reports not showing that I have any antivirus, this just came about not too long ago. That health report always worked before so something has happened to make it stop working correctly.
Its a bug and it does not always work, this is not a big problem, however

The bug has developed somewhere along the way because I never had a problem with it before. It worked after I installed Avast because I run it from time to time.

When I booted my computer this morning it again gave me the BSOD. I selected to start normally from the next screen and that went ok -- except the screen did flash to white for a few seconds after the desktop loaded, which is not normal.

Probably you only got the most recent mini dump because I run CCleaner a few times a week. Please see the screenshot of what I have checked for cleaning under System and tell me what I should uncheck in order to maintain the mini dump info.

Also see the screen shots I took this morning of the Windows info box that appeared explaining the BSOD of this morning.

I am going to confer with Avast before I just uninstall this program. Had I heard about this Microsoft Security Essentials earlier, I probably would have tried it before purchasing Avast, but please understand that this program has been working beautifully for me and I just purchased it about 6 months ago. I recently installed the paid version of MBAM. There haven't appeared to be any conflicts, but could that have any bearing?

Thank you for your help!

I can just tell you one thing, and do not let Avast talk you out of it. This dump says that Avas is the cause. I am not saying that if I had other dumps my conclusion would be the same, but the driver mentioned in this dump is an Avast driver.

With Avast, you should have gotten the free version of Malwarbytes. You have to exclude malwarebytes from the Avast protection process to insure no conflicts.

In conclusion Avast is fine software and does its job. There was a problem, however, per this one report. Its your computer and you have to decide what course of action you should take. I am just giving facts as shown in a report.

Untick memory dumps, log files and error reporting in CC, to have all the dumps amd reports in case it happens again.

Nikilet · Jul 4, 2011

The dump I had this morning should still be on file as I haven't run CCleaner. Should I send you the info so you can see if it's the same problem? And do I do that by running that one file and then running a health report again?

Also, please understand that I do not doubt what you told me about Avast, not for one second. I am just hoping that Avast has a solution, a workaround.

richc46 · Jul 4, 2011

And please you understand, my function is only to give you the best information available. It is up to you to take all the available information supplied by me and others and do what is best for you. Whatever you decide I will continue to offer the best possible help.
Yes, if you have more BSODs please send the report. You can tell Avast what we have found, give the driver name and see what they say.
This is all that I need, it is the same for Vista
http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

Nikilet · Jul 4, 2011

You said this is all that you need. If I need to run that other file you gave me yesterday and then a health report please advise. I see that I apparently can't open these files, but was able to send it to zip.

Thanks!

Nikilet · Jul 4, 2011

So sorry! I think I gave you the file from yesterday, rather than the one for the BSOD today. I have attached the other.

richc46 · Jul 4, 2011

Send it the way you sent the first one, a few days ago, this one cant be read.

Nikilet · Jul 4, 2011

Here you go.

richc46 · Jul 4, 2011

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Windows_NT6_BSOD_jcgriff2 (3).zip\Windows_NT6_BSOD_jcgriff2\Mini070311-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x82e4c000 PsLoadedModuleList = 0x82f63c70
Debug session time: Sun Jul  3 23:56:43.395 2011 (GMT-4)
System Uptime: 2 days 9:34:10.172
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {7, 8d5b242c, d7094f68, 0}
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
[B]Probably caused by : aswSP.SYS ( aswSP+b42c )[/B]
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[B]DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)[/B]
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 00000007, IRP passed to IoCompleteRequest still has cancel routine set
Arg2: 8d5b242c, the cancel routine pointer
Arg3: d7094f68, the IRP
Arg4: 00000000
Debugging Details:
------------------
 
BUGCHECK_STR:  0xc9_7
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  7
IRP_CANCEL_ROUTINE: 
aswSP+b42c
8d5b242c 8bff            mov     edi,edi
FAULTING_IP: 
aswSP+b42c
8d5b242c 8bff            mov     edi,edi
FOLLOWUP_IP: 
aswSP+b42c
8d5b242c 8bff            mov     edi,edi
IRP_ADDRESS:  d7094f68
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  AvastSvc.exe
CURRENT_IRQL:  1
LAST_CONTROL_TRANSFER:  from 8312fad3 to 82f19b3f
STACK_TEXT:  
8db72b28 8312fad3 000000c9 00000007 8d5b242c nt!KeBugCheckEx+0x1e
8db72bac 8d5b2251 000006e8 000006e8 91ad3234 nt!IovCompleteRequest+0x5c
WARNING: Stack unwind information not available. Following frames may be wrong.
8db72bf0 8d5addde 00000000 000006e8 00000000 aswSP+0xb251
8db72c08 8d5b637b 00000000 000006e8 00000000 aswSP+0x6dde
8db72c2c 8d5b6457 00000000 00000000 000006e8 aswSP+0xf37b
8db72c44 8303d55e 91ad0ad8 000006e8 00000000 aswSP+0xf457
8db72c74 830649d1 00000001 219839f1 91a331f8 nt!PspExitProcess+0x99
8db72cdc 830413e7 00000000 ac5caac8 ac5cab01 nt!PspExitThread+0x574
8db72cf4 82efffba 91a331f8 8db72d20 8db72d2c nt!PsExitSpecialApc+0x22
8db72d4c 82e96d26 00000001 00000000 8db72d64 nt!KiDeliverApc+0x1dc
8db72d4c 77d55ca4 00000001 00000000 8db72d64 nt!KiServiceExit+0x56
02feff88 00000000 00000000 00000000 00000000 0x77d55ca4
 
STACK_COMMAND:  .bugcheck ; kb
SYMBOL_NAME:  aswSP+b42c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: aswSP
IMAGE_NAME:  aswSP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP:  4dc9299f
FAILURE_BUCKET_ID:  0xc9_7_VRF_aswSP+b42c
BUCKET_ID:  0xc9_7_VRF_aswSP+b42c
Followup: MachineOwner
---------

What is the aswsp.sys file?

This is the dump that you sent for July 3
I will not explain it to you. I have given you a link and bolded the cause of the problem.

I did notice something interesting, however. The driver verifier is on (a test to seek out drivers causing BSODs). You may want to turn it off and see if the BSODs continue. It was on during all the BSODs that you sent me.

Keep in mind that once you enable the Driver Verifier Manager it stays active until you disable it. To do so, follow these steps:
Access the Run dialog box by pressing the [Windows]-R keyboard shortcut.
In the Open text box, type the command-> Verifier /reset.
I hope this helps.

Nikilet · Jul 4, 2011

According to what you wrote, I must have again sent you the dump file for July 3, yesterday. Is his correct? I wanted to send you the dump file for the BSOD that occurred this morning when I booted up.

The driver verifier is on (a test to seek out drivers causing BSODs). You may want to turn it off and see if the BSODs continue. It was on during all the BSODs that you sent me.

I have no idea how this driver verifier got turned on. I don't even know what it is. If I didn't activate it, do you know what would have?

I finally got a response from Avast. They asked me to update to the latest version. As I told them, I thought that was done automatically. I have to restart now after this update so it will be interesting to see what happens. I'll let you know.

richc46 · Jul 4, 2011

The dumps give clues and not usually answers.

The most recent dump gave a clue that it was a driver, but not the precise one. July 3 confirms the original analysis and I used that one.
Turn the verifier off and see what happens.
BTW, your AV had driver updates in May, I think there may have been a conflict.

Possibly the verifier may have been turned on inadvertenly, but you see by the report, it is on.

Nikilet · Jul 4, 2011

Do I need to know about this driver verifier -- for instance, how did I inadvertently turn it on?

I did not get a BSOD on restart, but after my desktop had come up and was loading, the screen again turned all white for approximately 10-15 seconds. I know it should not be doing this.

richc46 · Jul 4, 2011

Lets try to get the BSODs fixed. The problems could be related.
I cannot tell you how the Verifier got turned on. Maybe someone was trying to fix your computer, family member or you brought it to a pro. Possibly, if the OS came with the computer, the computer manufacturer turned it on. I really cant answer more definitively.

Nikilet · Jul 4, 2011

That's what I want too. But I would like you to know that I am the only one who uses this computer, and it has never been to a repair shop. I have a reply into Avast forum so will see what they have to say. If there is anything else you want me to try at this point, let me know.

Thanks for your help. I think I will have to shut down as the thunder is booming.

'Night!

richc46 · Jul 4, 2011

You know as much as I do. Dont worry about the verifier, the computer probably came with it on. It does not cause problems, it merely makes bad drivers BSOD.
Night.
Just give Avast the name of the driver and that it caused at least 3 BSODs.
Then see what they say
If they tell you how to fix it and it works great, good luck
If they tell you how to fix it and you still get BSODs from the same driver, you must get rid of Avast.
I and other members will be here for you. To help you in the future
Night.

BSOD on Shutdown or restart

My Computer

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

Attachments

My Computer

Attachments

My Computer

My Computer

Attachments

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer