| | |
Windows XP blue screen error message
![]() |
•
•
Join Date: Dec 2008
Posts: 14
Reputation:
Solved Threads: 0
I am getting a blue screen error when I shut down my computer. I believe it is because I undocked it before it finished shutting down. This is the Error Message:
Technical information:
*** STOP: 0x0000000A (0x00000018, 0x00000002, 0x00000000, 0x804F45AA)
Beginning dump of physical memory
Physical memory dump complete
Contact your system administrator or technical support group for further assistance.
I downloaded a hotfix but it wouldn't work because it said I had more current updates. What should I do?
Technical information:
*** STOP: 0x0000000A (0x00000018, 0x00000002, 0x00000000, 0x804F45AA)
Beginning dump of physical memory
Physical memory dump complete
Contact your system administrator or technical support group for further assistance.
I downloaded a hotfix but it wouldn't work because it said I had more current updates. What should I do?
•
•
Join Date: Mar 2008
Posts: 392
Reputation:
Solved Threads: 40
Does the problem occur both inside and outside the dock? It sounds like a hardware profiles issue. I would create new hardware profiles for each situation. Here's some info on hardware profiles by MS: http://support.microsoft.com/kb/308577
Eric
MCSE, MCP, A+, Network+
Managed IT Services Houston | Outsource IT Support Houston Texas
PinnacleReviews.com | Customer Reviews
MCSE, MCP, A+, Network+
Managed IT Services Houston | Outsource IT Support Houston Texas
PinnacleReviews.com | Customer Reviews
•
•
Join Date: Jul 2008
Posts: 197
Reputation:
Solved Threads: 12
What you do is:
Download, and install WhoCrashed: http://www.resplendence.com/download...ashedSetup.exe
Open it, click Analyze button.
The program will create report
Copy, and paste it into your next reply.
Download, and install WhoCrashed: http://www.resplendence.com/download...ashedSetup.exe
Open it, click Analyze button.
The program will create report
Copy, and paste it into your next reply.
•
•
Join Date: Dec 2008
Posts: 14
Reputation:
Solved Threads: 0
Thanks, here is the report.
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 1/9/2009 1:27:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x18, 0x2, 0x0, 0x804F45AA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Thu 1/8/2009 6:54:54 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x18, 0x2, 0x0, 0x804F45AA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Wed 1/7/2009 11:59:19 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x9F6C7058, 0x2, 0x0, 0x804F45AA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Mon 1/5/2009 7:25:45 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x35 (0x89F43970, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Mon 1/5/2009 1:43:31 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x805E182B, 0xB35437AC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Tue 12/30/2008 8:56:46 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x35 (0x8A345D60, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Mon 12/29/2008 7:54:35 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x35 (0x8B19B860, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Sat 9/27/2008 12:07:37 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xB7AC745C, 0x0, 0x80537AF0, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Fri 8/1/2008 7:05:40 PM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0xEA (0x8A06E430, 0x8A6ABD58, 0x8A7DB1F8, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 101.19
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 101.19
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 1/9/2009 1:27:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x18, 0x2, 0x0, 0x804F45AA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Thu 1/8/2009 6:54:54 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x18, 0x2, 0x0, 0x804F45AA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Wed 1/7/2009 11:59:19 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x9F6C7058, 0x2, 0x0, 0x804F45AA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Mon 1/5/2009 7:25:45 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x35 (0x89F43970, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Mon 1/5/2009 1:43:31 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x805E182B, 0xB35437AC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Tue 12/30/2008 8:56:46 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x35 (0x8A345D60, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Mon 12/29/2008 7:54:35 PM your computer crashed
This was likely caused by the following module: ikfilesec.sys
Bugcheck code: 0x35 (0x8B19B860, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on ikfilesec.sys
On Sat 9/27/2008 12:07:37 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xB7AC745C, 0x0, 0x80537AF0, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.
On Fri 8/1/2008 7:05:40 PM your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0xEA (0x8A06E430, 0x8A6ABD58, 0x8A7DB1F8, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 101.19
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 101.19
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
9 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
![]() |
Similar Threads
- power loss during partition magic resize = blue screen (Troubleshooting Dead Machines)
- windows blue screen of death on xp64 (Windows NT / 2000 / XP)
- blue screen fustration (IT Professionals' Lounge)
- Blue Screen of Mad (Windows NT / 2000 / XP)
- "Blue Screen of Death" Error + various other errors. (Windows NT / 2000 / XP)
- Blue Screen Issues, Please Help (Windows NT / 2000 / XP)
- Windows XP Home refusing to boot (Windows NT / 2000 / XP)
- unique error message (Troubleshooting Dead Machines)
- Blue Screen Error Shows Up Repeatedly (Troubleshooting Dead Machines)
Other Threads in the Windows NT / 2000 / XP Forum
- Previous Thread: Greyed Task Manager
- Next Thread: Retrieving old files
| Thread Tools | Search this Thread |
.net 64bit 2007 2010 a.exe address apache appstore automatically black blue bsod bulletin canonical cellphones chkdsk codeplex computer crash cursor deployment deployments desktop desktops dns dotnetnuke drive dual eartlink error errors explorer fax features firefox folder fontmanagers format framework freeze hardware home install internet interoperability laptop linux load login mac memory microsoft monitor motionle1600 netbooks novell nvidia open operatingsystems options osx palm partition printer product program proxy reformat remotedesktop repair replacingraiddrive retail retrieve screen security sharepoint simplifiedchinese sitetositevpn slowperformance technology ubuntu uninstall update videodrivers videogames virus vista visual vpn vulnerability wab win win32/heur windows windows7 windowsxp windowsxpnotstartingup. worm xp xpde





