General discussion

Locked

Crash Test

By coffey2go ·
My Dell XPS L701X Windows 7 Ultimate keeps freezing and I also got BSOD but it came back on what do the crash test results mean and what do I need to do to fix this problem.

Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 9/3/2011 5:44:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090211-19890-01.dmp
This was probably caused by the following module: atwpkt264.sys (ATWPKT264+0x4390)
Bugcheck code: 0x11B (0xFFFFFA800CCE74E0, 0xFFFFF8800981C390, 0x0, 0x0)
Error: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
file path: C:\Windows\system32\drivers\atwpkt264.sys
product: ATW Protocol Driver
company: America Online
description: ATW Protocol Driver
Bug check description: This bug check indicates that a driver has returned from a cancel routine that holds the global cancel lock. This causes all later cancellation calls to fail, and results in either a deadlock or another bug check.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atwpkt264.sys (ATW Protocol Driver, America Online).
Google query: atwpkt264.sys America Online DRIVER_RETURNED_HOLDING_CANCEL_LOCK


On Sat 9/3/2011 5:44:12 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x11B (0xFFFFFA800CCE74E0, 0xFFFFF8800981C390, 0x0, 0x0)
Error: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
Bug check description: This bug check indicates that a driver has returned from a cancel routine that holds the global cancel lock. This causes all later cancellation calls to fail, and results in either a deadlock or another bug check.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 8/30/2011 4:12:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083011-21855-01.dmp
This was probably caused by the following module: atwpkt264.sys (ATWPKT264+0x4390)
Bugcheck code: 0x11B (0xFFFFFA800DCA2010, 0xFFFFF88007410390, 0x0, 0x0)
Error: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
file path: C:\Windows\system32\drivers\atwpkt264.sys
product: ATW Protocol Driver
company: America Online
description: ATW Protocol Driver
Bug check description: This bug check indicates that a driver has returned from a cancel routine that holds the global cancel lock. This causes all later cancellation calls to fail, and results in either a deadlock or another bug check.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atwpkt264.sys (ATW Protocol Driver, America Online).
Google query: atwpkt264.sys America Online DRIVER_RETURNED_HOLDING_CANCEL_LOCK


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atwpkt264.sys (ATW Protocol Driver, America Online)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Thank you
Coffey2go

This conversation is currently closed to new comments.

0 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Back to Software Forum
0 total posts (Page 1 of 1)  

Related Discussions

Related Forums