Solved Getting BSOD on shutdown after logging out of AOL

November 8, 2016 at 09:32:42
Specs: Windows 7 home, Intel Pent., cpu g630, 4.00 GB, 64 bit
Sometime when I close out of AOL and shut down the computer without waiting for a min or two, I get a Blue Screen saying,

"A problem has been detected and Windows has shut down to prevent damage. A driver has returned from a cancellation call holding the global lock . . . Disable BIOS memory option such as caching or shadowing . . ."

Then I click on disk cleanup and it dumps about 500 mb on system memory dump.

I have not installed any hardware of software in quite a while.

I regularly run AdwareCleaner, JRT, Malwarebytes, RogueKiller and ComboFix.



See More: Getting BSOD on shutdown after logging out of AOL

Report •

✔ Best Answer
November 10, 2016 at 21:28:10
"I shutdown aol, shutdown comp 3 times, no BSOD"
Sounds good.

Next step, extract from your Addition log, lets see if you can get these fixed.

==================== Faulty Device Manager Devices =============

Name: Microsoft Teredo Tunneling Adapter
Description: Microsoft Teredo Tunneling Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device cannot start. (Code10)
Resolution: Device failed to start. Click "Update Driver" to update the drivers for this device.
On the "General Properties" tab of the device, click "Troubleshoot" to start the troubleshooting wizard.

Name: Lexmark X422
Description: Lexmark X422
Class Guid: {6bdd1fc6-810f-11d0-bec7-08002be2092f}
Manufacturer: Lexmark
Service: usbscan
Problem: : This device cannot start. (Code10)
Resolution: Device failed to start. Click "Update Driver" to update the drivers for this device.
On the "General Properties" tab of the device, click "Troubleshoot" to start the troubleshooting wizard.



#1
November 8, 2016 at 13:32:57
Hi Warren.

"Disable BIOS memory option such as caching or shadowing . . ."
Have you?

"dumps about 500 mb on system memory dump"
Lets get an minidump.

This guide will be similar, though it may be called small on you Windows version.
BSOD Minidump - Configure to Create in Windows 10
http://www.tenforums.com/tutorials/...

When you get an mini/small dmp file, Copy & Paste the dump (.dmp ) file onto your desktop & then upload it using ZippyShare. No account/registration needed. Post the link please.
http://www.zippyshare.com/
Instructions on how to use ZippyShare.
http://i.imgur.com/naG6t2T.gif
http://i.imgur.com/Vi9ZdIh.gif
http://i.imgur.com/1IZu5kP.gif
Minidump file is located in C:\Windows\Minidump
How to see hidden files in Windows
http://www.bleepingcomputer.com/tut...



Report •

#2
November 8, 2016 at 14:39:02
People still use AOL?

Report •

#3
November 9, 2016 at 13:22:42
"Disable BIOS memory option such as caching or shadowing . . ."

tried this to no avail. HP has a different setup for BIOS. Can't see any cacheing or shadowing. Got a query in to HP help board, guy says hasn't been a problem in quite awhile. Awaiting his response but here is the dmp file:

http://www39.zippyshare.com/v/P4biH...


Report •

Related Solutions

#4
November 9, 2016 at 15:41:25
It looks more like an AOL problem.

* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_RETURNED_HOLDING_CANCEL_LOCK (11b)
A driver has returned from a cancellation routine holding the global cancel
lock. This will result in any subsequent cancellation calls to fail either
resulting in a deadlock or another bugcheck.
Arguments:
Arg1: fffffa80095d6de0, The address of the IRP that was cancelled (may not be valid).
Arg2: fffff880095ce390, The address of the cancel routine.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
ATWPKT264+4390
fffff880`095ce390 4889542410 mov qword ptr [rsp+10h],rdx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x11B

PROCESS_NAME: AOLacsd.exe

CURRENT_IRQL: 2

STACK_TEXT:
fffff880`09891808 fffff800`04b528a8 : 00000000`0000011b fffffa80`095d6de0 fffff880`095ce390 00000000`00000000 : nt!KeBugCheckEx
fffff880`09891810 fffff800`04db2259 : 00000000`00000001 fffffa80`08f9cf40 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3afca
fffff880`09891850 fffff800`04db28fc : 00000000`00000000 00000000`00000000 fffff880`09891be0 00000000`00000000 : nt!IoCancelThreadIo+0x59
fffff880`09891880 fffff800`04d97c2d : fffffa80`40010004 00000000`00000000 fffffa80`78457300 00000000`00000000 : nt!PspExitThread+0x2bc
fffff880`09891980 fffff800`04aceeb4 : fffffa80`077b1e30 fffffa80`04102e90 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`098919b0 fffff800`04b26540 : 00000000`00000003 fffff880`09891a30 fffff800`04d97ba0 00000000`00000001 : nt!KiDeliverApc+0x2e4
fffff880`09891a30 fffff800`04adb3b7 : 00000000`00000000 fffff800`04dc7730 fffff880`09891c60 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff880`09891b70 00000000`73342e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`04c1f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73342e09


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
ATWPKT264+4390
fffff880`095ce390 4889542410 mov qword ptr [rsp+10h],rdx

SYMBOL_NAME: ATWPKT264+4390

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ATWPKT264

IMAGE_NAME: ATWPKT264.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 530ce6d3

FAILURE_BUCKET_ID: X64_0x11B_ATWPKT264+4390

BUCKET_ID: X64_0x11B_ATWPKT264+4390

Followup: MachineOwner


Report •

#5
November 9, 2016 at 15:42:23
Bug Check 0x11B: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
https://msdn.microsoft.com/en-us/li...

Report •

#6
November 9, 2016 at 15:55:53
Please download Farbar Recovery Scan Tool and save it onto your Desktop. If your default download location is not the Desktop, drag it out of it's location onto the Desktop.
http://www.bleepingcomputer.com/dow...
If we have to run Farbar more than once, refer this SS.
http://i.imgur.com/yUxNw0j.gif
Note: You need to run the version compatible with your system. If you are not sure which version applies to your system download both of them and try to run them. Only one of them will run on your system, that will be the right version.
Double-click to run it. When the tool opens click Yes to disclaimer.
Press Scan button.
It will make a log (FRST.txt) on the Desktop.
The first time the tool is run, it makes also another log (Addition.txt)
The logs are large, upload them using Zippy

Report •

#7
November 9, 2016 at 23:44:24
AOL keeps a lot of junk floating around in the background. It you have AOL desktop go to 'edit' in their toolbar then down to 'start-up settings'. Then disable 'enable fast start'.

You can also run msconfig and try disabling some of the AOL stuff on startup.

Of course once you start AOL at least some things will load anyway but you can try the above and see if it helps.


Report •

#8
November 10, 2016 at 07:42:10
Thanks Dave, will try that. I re-install AOL every once in a while and delete all the other versions. Will do what Johnw said too, later.

And please tell Riider we are the only two still on. lol


Report •

#9
November 10, 2016 at 10:34:40

Report •

#10
November 10, 2016 at 15:23:41
" I re-install AOL every once in a while"

I would uninstall again Warren. Use your IObit Uninstaller.
Reinstall & test.

Run Powerful Scan, to remove all the lurking bits.
http://fs5.directupload.net/images/...
http://fs5.directupload.net/images/...

There is still more work to be done after you do the above, small steps so we can identify the problem.

message edited by Johnw


Report •

#11
November 10, 2016 at 19:33:46
OK. uninstalled AOL, ran Powerful Scan and found this:

registry entries deleted 4705
files deleted 203.9 mb

Reinstalled aol.

I shutdown aol, shutdown comp 3 times, no BSOD


message edited by WarrenTSI


Report •

#12
November 10, 2016 at 21:28:10
✔ Best Answer
"I shutdown aol, shutdown comp 3 times, no BSOD"
Sounds good.

Next step, extract from your Addition log, lets see if you can get these fixed.

==================== Faulty Device Manager Devices =============

Name: Microsoft Teredo Tunneling Adapter
Description: Microsoft Teredo Tunneling Adapter
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Manufacturer: Microsoft
Service: tunnel
Problem: : This device cannot start. (Code10)
Resolution: Device failed to start. Click "Update Driver" to update the drivers for this device.
On the "General Properties" tab of the device, click "Troubleshoot" to start the troubleshooting wizard.

Name: Lexmark X422
Description: Lexmark X422
Class Guid: {6bdd1fc6-810f-11d0-bec7-08002be2092f}
Manufacturer: Lexmark
Service: usbscan
Problem: : This device cannot start. (Code10)
Resolution: Device failed to start. Click "Update Driver" to update the drivers for this device.
On the "General Properties" tab of the device, click "Troubleshoot" to start the troubleshooting wizard.


Report •

#13
November 12, 2016 at 15:45:05
"Name: Microsoft Teredo Tunneling Adapter"

fixed.


"Name: Lexmark X422"

fixed.


Report •

#14
November 12, 2016 at 15:50:48
Very good, you should be Ok, now.

Report •

#15
November 12, 2016 at 19:02:45
As usual, thank you

Report •

Ask Question