Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows XP stop error


  • Please log in to reply
8 replies to this topic

#1 bishop743

bishop743

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:49 AM

Posted 04 August 2005 - 05:45 PM

Good evening, everyone. I'm here today because I am getting an annoying stop error in Windows XP Pro. Sometimes while I'm doing various things I get this error:

--------------------------------------------------------------------
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 8/4/2005
Time: 6:14:11 PM
User: N/A
Computer: OWNER-9BPJCGIBT
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x001902fe, 0xfab386c4, 0xfab383c0, 0x804ed63a). A dump was saved in: C:\WINDOWS\Minidump\Mini080405-04.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------------------------------------------------

I have no idea what's causing this. Also, so that it might aid someone in solving this problem, I took the liberty of downloading a debugging tool and loaded the DMP file in there. Here are the results:

--------------------------------------------------------------------

Microsoft ® Windows Debugger Version 6.5.0003.7
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Owner\Desktop\Mini080405-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Thu Aug 4 18:01:10.426 2005 (GMT-4)
System Uptime: 0 days 2:13:21.996
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................
Loading unloaded module list
...............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1902fe, fab386c4, fab383c0, 804ed63a}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image Ntfs.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : hardware ( Ntfs+ac8 )

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 001902fe
Arg2: fab386c4
Arg3: fab383c0
Arg4: 804ed63a

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

EXCEPTION_RECORD: fab386c4 -- (.exr fffffffffab386c4)
ExceptionAddress: 804ed63a (nt+0x0001663a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 5c3b0cc9
Attempt to write to address 5c3b0cc9

CONTEXT: fab383c0 -- (.cxr fffffffffab383c0)
eax=00000008 ebx=0000006c ecx=00000009 edx=e1ae2110 esi=e12b6e68 edi=0000000a
eip=804ed63a esp=fab3878c ebp=fab387a0 iopl=0 nv up ei pl nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
nt+0x1663a:
804ed63a 108b5d0c3b5c adc [ebx+0x5c3b0c5d],cl ds:0023:5c3b0cc9=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x24

MISALIGNED_IP:
nt+1663a
804ed63a 108b5d0c3b5c adc [ebx+0x5c3b0c5d],cl

LAST_CONTROL_TRANSFER: from 804ed563 to 804ed63a

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
fab387a0 804ed563 e12b6e68 0000006c fab387c4 nt+0x1663a
fab387e4 fc32eac8 e12b6e68 0000006c 00000000 nt+0x16563
fab38824 fc35f66b e12b6e28 0000006c 00000000 Ntfs+0xac8
fab388a0 fc36824e fab38ae4 81190880 e12b6d90 Ntfs+0x3166b
fab38ac8 fc353d83 fab38ae4 ff6d5008 8126ae88 Ntfs+0x3a24e
fab38c40 804e37f7 8126a408 ff6d5008 81255f38 Ntfs+0x25d83
fab38c60 804e37f7 8126add0 ff6d5008 ff6d5008 nt+0xc7f7
fab38ca4 80566901 811c7488 8126add0 0012019f nt+0xc7f7
fab38cd4 80566aab 811c7488 81190880 8127d730 nt+0x8f901
fab38cfc 80566b1c e1384ba0 81190880 000007f4 nt+0x8faab
fab38d44 80566b66 000007f4 00000001 00000000 nt+0x8fb1c
fab38d58 804de7ec 000007f4 0012ede0 7c90ebab nt+0x8fb66
fab38d64 7c90ebab badb0d00 0012eddc 001e075e nt+0x77ec
fab38d68 badb0d00 0012eddc 001e075e 001e075f 0x7c90ebab
fab38d6c 0012eddc 001e075e 001e075f 00000000 0xbadb0d00
fab38d70 001e075e 001e075f 00000000 00000000 0x12eddc
fab38d74 001e075f 00000000 00000000 00000000 0x1e075e
fab38d78 00000000 00000000 00000000 00000000 0x1e075f


FOLLOWUP_IP:
Ntfs+ac8
fc32eac8 ?? ???

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Ntfs+ac8

IMAGE_NAME: hardware

STACK_COMMAND: .cxr fffffffffab383c0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

If anyone at all has a clue as to what's going on here, I would greatly appreciate some assistance. If you have any questions, I would be glad to answer them the best I can.

BC AdBot (Login to Remove)

 


m

#2 unrepper

unrepper

  • Members
  • 205 posts
  • OFFLINE
  •  
  • Local time:06:49 AM

Posted 04 August 2005 - 06:33 PM

A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

here first

http://support.microsoft.com/?kbid=228888&sd=RMVP
Posted Image

#3 Enthusiast

Enthusiast

  • Members
  • 5,898 posts
  • OFFLINE
  •  
  • Location:Florida, USA
  • Local time:06:49 AM

Posted 04 August 2005 - 08:58 PM

Did this start happening right after you installed SP 2?

#4 bishop743

bishop743
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:49 AM

Posted 04 August 2005 - 10:55 PM

unrepper : Thanks for the reply. I'll be sure go through those methods to see if either one helps remedy the issue. I appreciate your help.


Enthusiast : Actually, yeah it did. I don't remember getting this specific error before installing SP2.

#5 bishop743

bishop743
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:06:49 AM

Posted 21 August 2005 - 06:37 PM

I've went through the various steps unrepper gave to try and remedy the problem, but it still persists. I also have noticed that this error usually happens when my CPU Usage is at 100% for a period of time. So, might that have anything to do with what's causing the problem?

#6 FlatLander

FlatLander

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:07:49 AM

Posted 31 August 2005 - 11:09 PM

I was having the same problem. Also continually gent message from Norton that microsoft print dpooler was attempting to connect. Downloaded and installed MS fix...no problems since

#7 Guest_bg fun_*

Guest_bg fun_*

  • Guests
  • OFFLINE
  •  

Posted 04 November 2005 - 01:21 PM

I was having the same problem. Also continually gent message from Norton that microsoft print dpooler was attempting to connect. Downloaded and installed MS fix...no problems since


I am having the same problem. my debulog says the following:

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4313a6c6

FAULTING_IP:
nt!RtlAreAnyAccessesGranted+4be
8058caff 5d pop ebp

BUGCHECK_STR: 0xc2_43

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80549ea8 to 8053331e

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b891a920 80549ea8 000000c2 00000043 cfb74000 nt!KeBugCheckEx+0x1b
b891a95c 8054ab8b cfb74000 e121af40 e1076000 nt!wcstombs+0x31f8
b891a99c 8058caff cfb74000 00000000 b891aa08 nt!ExAllocatePoolWithTag+0x247
b891a9ac 80657296 cfb74000 00001000 00000000 nt!RtlAreAnyAccessesGranted+0x4be
b891aa08 8060ea81 e11ea008 00000000 00000000 nt!KeFlushQueuedDpcs+0x10d1
b891aa54 805a93c1 e11ea008 00000000 00000001 nt!IoCheckFunctionAccess+0x2eb5a
b891aa6c 805a918c e11ea101 00000005 00000000 nt!IoOpenDeviceRegistryKey+0x1c7c
b891aad8 805aa3f1 b891ab14 00000005 00000000 nt!IoOpenDeviceRegistryKey+0x1a47
b891ab30 805aad2c b891ac3c 00000000 b891ab9c nt!IoOpenDeviceRegistryKey+0x2cac
b891ab58 805aae02 b891ac04 b891aba4 b891ab94 nt!IoOpenDeviceRegistryKey+0x35e7
b891abe4 805aaca2 b891ac1c b891ac04 00000000 nt!IoOpenDeviceRegistryKey+0x36bd
b891ac7c 805aad02 009af990 009af978 00000000 nt!IoOpenDeviceRegistryKey+0x355d
b891ac90 f5e2584f 009af990 009af978 b891ad64 nt!IoOpenDeviceRegistryKey+0x35bd
b891ad54 804de7ec 009af990 009af978 009af9bc vsdatant+0x3184f
b891addc 804fa4da f7673b85 85c7a010 00000000 nt!ZwYieldExecution+0xb78
b891ade0 f7673b84 85c7a010 00000000 4000027f nt!KeInitializeTimer+0x107
b891ade4 85c7a010 00000000 4000027f 03020000 NDIS!___PchSym_+0xc
f7673b85 08458bec 3bf63356 840f57c6 00006fb1 0x85c7a010
f7673b89 3bf63356 840f57c6 00006fb1 54bff08b 0x8458bec
f7673b8d 840f57c6 00006fb1 54bff08b a5f76734 0x3bf63356
f7673b91 00000000 54bff08b a5f76734 ffa5a5a5 0x840f57c6

Can anyone help? It only appears when I am trying to install Nero 7

#8 Enthusiast

Enthusiast

  • Members
  • 5,898 posts
  • OFFLINE
  •  
  • Location:Florida, USA

Posted 04 November 2005 - 01:52 PM

unrepper : Thanks for the reply. I'll be sure go through those methods to see if either one helps remedy the issue. I appreciate your help.


Enthusiast : Actually, yeah it did. I don't remember getting this specific error before installing SP2.



Microsoft offers free support for anyone having problems after installing security updates which definately applies to SP2.

"Microsoft Security Product Support Policy

Technical support is available from Microsoft Product Support
Services at 1-866-PC SAFETY (1-866-727-2338).

There is no charge for support calls associated with security updates.

International customers can get support from their local Microsoft
subsidiaries. Phone numbers for international support can be found
at: [url="http://support.microsoft.com/common/international.aspx""]http://support.microsoft.com/common/international.aspx"[/url]

#9 acklan

acklan

    Bleepin' cat's meow


  • Members
  • 8,529 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Baton Rouge, La.
  • Local time:06:49 AM

Posted 04 November 2005 - 05:30 PM

Does that apply to OEM also? Shorly after I installed an OEM XP, I called for support and they informed me I would have to receive technical support from the company I purchased the software from. This was non-PC brand specific OEM Windows XP and that only retail verisons received MS support.
"2007 & 2008 Windows Shell/User Award"




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users