Crashes at shutdown

[conoflex]

My computer is running win7 professional RTM (waiting for my bought retail to arrive) and every now and then it crashes when I shutdown with seemingly different error messages BSOD this is the dump(see sysdata dump as well) from the last time it happened was wondering if anyone could tell me why and what to do about it.

TIA Andy

<?xml version="1.0" encoding="UTF-16" ?>
- <WERReportMetadata>
- <OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7600</Build>
<Product>(0x30): Windows 7 Professional</Product>
<Edition>Professional</Edition>
<BuildString>7600.16385.amd64fre.win7_rtm.090713-1255</BuildString>
<Revision>1</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
- <ProblemSignatures>
<EventType>BlueScreen</EventType>
</ProblemSignatures>
- <DynamicSignatures>
<Parameter1>6.1.7600.2.0.0.256.48</Parameter1>
<Parameter2>2057</Parameter2>
</DynamicSignatures>
- <SystemInformation>
<MID>33B04190-79E8-4A13-A9A4-25BA9723BA97</MID>
<SystemManufacturer>System manufacturer</SystemManufacturer>
<SystemProductName>P5Q DELUXE</SystemProductName>
<BIOSVersion>2201</BIOSVersion>
</SystemInformation>
</WERReportMetadata

 

[Tews]

Hi conoflex, welcome to the forums ... Nice specs you have there, but what we really need is the .dmp file that windows generates on a BSOD.. Navigate to C:/Windows/Minidump and upload the most recent file...

 

[conoflex]

Thanks Tews, of course how silly of me (as if I know what i'm doing:roflmao
Right got this from "whocrashed" program, also attached the dump file for you to have butchers at.

Andy

On Sun 20/09/2009 09:39:01 your computer crashed
This was likely caused by the following module: atwpkt264.sys
Bugcheck code: 0x11B (0xFFFFFA80075CE570, 0xFFFFF8800A2B0390, 0x0, 0x0)
Error: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
[FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\atwpkt264.sys[/FONT]
[FONT=Segoe UI, Arial]product: [FONT=Segoe UI, Arial]ATW Protocol Driver[/FONT]
company: [FONT=Segoe UI, Arial]America Online[/FONT]
description: ATW Protocol Driver

[/FONT]

 

[zigzag3143]

conoflex

Actually Right on the money. correct file and this is what may have caused it to fail. Again AOL software AOLacsd.exe. You might want to un-install then re-install the aol software. Good luck and let us know if you need help


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\092009-29265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e53000 PsLoadedModuleList = 0xfffff800`03090e50
Debug session time: Sat Sep 19 13:01:30.404 2009 (GMT-4)
System Uptime: 0 days 8:52:47.996
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 11B, {fffffa80075ce570, fffff8800a2b0390, 0, 0}

Unable to load image \??\C:\Windows\system32\drivers\ATWPKT264.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ATWPKT264.SYS
*** ERROR: Module load completed but symbols could not be loaded for ATWPKT264.SYS
Probably caused by : ATWPKT264.SYS ( ATWPKT264+4390 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* 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: fffffa80075ce570, The address of the IRP that was cancelled (may not be valid).
Arg2: fffff8800a2b0390, The address of the cancel routine.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x11B

PROCESS_NAME: AOLacsd.exe

CURRENT_IRQL: 2

STACK_TEXT:
fffff880`0b298838 fffff800`02f3ea62 : 00000000`0000011b fffffa80`075ce570 fffff880`0a2b0390 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b298840 fffff800`031a7c09 : 00000000`00000001 fffffa80`0d297f48 00000000`00000000 fffffa80`0d297b60 : nt! ?? ::FNODOBFM::`string'+0x3c2e4
fffff880`0b298880 fffff800`031a75f7 : fffffa80`0b697680 fffffa80`0b697680 fffff880`0b298be0 00000000`00000000 : nt!IoCancelThreadIo+0x59
fffff880`0b2988b0 fffff800`03181b3d : 00000000`40010004 00000000`00000000 00000000`78457300 00000000`00000000 : nt!PspExitThread+0x2c7
fffff880`0b298980 fffff800`02ea1a43 : 00000000`02d1fd20 00000000`02d1f170 00000000`74922450 fffff800`02f1065c : nt!PsExitSpecialApc+0x1d
fffff880`0b2989b0 fffff800`02ea1e80 : 00000000`0532fe38 fffff880`0b298a30 fffff800`03182710 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0b298a30 fffff800`02ec41f7 : 00000000`00000000 fffff800`031dedfc fffff880`0b298c60 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff880`0b298b70 00000000`74922dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`02d1f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74922dd9


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
ATWPKT264+4390
fffff880`0a2b0390 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: 456eef6d

FAILURE_BUCKET_ID: X64_0x11B_ATWPKT264+4390

BUCKET_ID: X64_0x11B_ATWPKT264+4390

Followup: MachineOwner
---------

Ken

 

[conoflex]

Cheers Ken will do that and report back either way.

Andy

 

[zigzag3143]

Andy

Good luck and let us know how it turns out

Ken

 

[jfar]

Hi, conoflex, nice little program there, I like it.

 

[conoflex]

Did That but I have had 2 more crashes one I think is related first post, so it uninstalling re-installing didn't help
The latest one occured when putting a usb pen drive in usb hub.
I've uploaded the minidumps so u can analze them.

On Sun 27/09/2009 10:02:09 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031A7FE0, 0xFFFFF88003B0B700, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
[FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe[/FONT]
[FONT=Segoe UI, Arial]product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
[/FONT]


[FONT=Segoe UI, Arial]On Sat 26/09/2009 08:57:41 your computer crashed[/FONT]
[FONT=Segoe UI, Arial]This was likely caused by the following module: [FONT=Segoe UI, Arial]atwpkt264.sys[/FONT]
Bugcheck code: 0x11B (0xFFFFFA800BE59510, 0xFFFFF8800A7A0390, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_RETURNED_HOLDING_CANCEL_LOCK[/FONT]
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\atwpkt264.sys[/FONT]
[FONT=Segoe UI, Arial]product: [FONT=Segoe UI, Arial]ATW Protocol Driver[/FONT]
company: [FONT=Segoe UI, Arial]America Online[/FONT]
description: ATW Protocol Driver
[/FONT]

 

[conoflex]

Could someone give me a clue Please

 

[H2SO4]

Could someone give me a clue Please

Uninstalling/reinstalling the same (buggy) driver rarely results in improvement. In fact, if reinstalling did help, that would imply the problem was previously elsewhere - not in the driver.

That AOL driver has now been fingered in at least two of your crashes, if I understand correctly. I'd suggest trying to find a later version of the driver - or rather the app which put it there - and if that's not available then you've got to ask yourself whether you really need the app/driver.

Have those AOL components actually been certified for use with Win 7?

 

[conoflex]

H2SO4
"Have those AOL components actually been certified for use with Win 7? "

Good point I can't get AOL to answer any of my questions about it.

Andy

 

[H2SO4]

H2SO4
"Have those AOL components actually been certified for use with Win 7? "

Good point I can't get AOL to answer any of my questions about it.

Andy

Most apps written long ago will happily run on newer versions of Windows, including Win 7. However, apps which include a kernel-mode driver, like this AOL one, are sometimes unable to function on newer versions (for which they weren't designed) because their driver does not work properly under the updated driver framework.

 

[conoflex]

I actually got a response from AOL which all in all is rubbish tells me nothing and didn't even say when Win 7 is going to be supported, This is the answer I got most of which I've already done. I have also deleted the "atwpkt264.sys" file and not had a crash since so far.


" Dear Andy,

My Name is Andy from Email Technical Support and I am writing to you regarding your issue with AOL crashing our computer, I apologise for this issue and will advise what I can to resolve this issue for you for you today.

This issue can occur with Windows 7 if you have it, the AOL Software has not been optimised for Windows 7 as of yet. What we could try and do is uninstalling the AOL Software and then reinstalling and if that fails then I would recommend doing a Reg Edit on your AOL Software. I will advise on how to get these steps done below.

To get a new version of the AOL software you can click this link AOL Downloads and you will be able to download a fresh copy there. you can uninstall the AOL software by clicking Start > Control Panel > Add/Remove Programs (Programs and Features for Windows Vista) and then locating your version of AOL and clicking Change/Remove.

To get the Reg Edit done you will need to call in as we cannot advise on how to do a Reg Edit over Email. You can call into our call center here on 0844 499 5555 and then the first level tech team may be able to go over some fixes we cannot, then pass you through to second level tech and they will be able to do a Reg Edit which should resolve your issue.
You will receive a survey to rate the service that you received today. If you can please take a few moments to fill it in for me, as the first two sections relate directly to myself and our interaction via email only :
- Was your query resolved during this contact?
- How satisfied were you with my knowledge of your issue?
- How clear and easy to follow my response?
- How was my overall attitude in the e-mail response?

I hope this has been of help to you today, If you have any further queries, feel free to contact 08444 99 5555 for AOL Technical Support, or email us again.

Thank you for Contacting us at AOL Broadband Email Support

Kindest Regards,
Andy, "

 

[H2SO4]

It's always heart-warming when the amount of space and effort expended on ingratiatingly fishing for positive survey results is at least as great as their technical investment in your issue

I wonder what the (phone-only) "Reg Edit" would have been? (For some reason, I find these massive tech support organisations inherently comical.)

 

[conoflex]

H2SO4
"I wonder what the (phone-only) "Reg Edit" would have been? (For some reason, I find these massive tech support organisations inherently comical.) "

Well they make me larf :roflmao:
It would have been "i'm not sure" pass the buck and 3 hours later none the wiser.
Andy