Windows XPPost your Windows XP related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
Stop 0x00000050 ntfs.sys problem [now with dump data]
Hi.
I have added a few new programs to my XP installation over thew past month, and last night I thought it was about time to make a new disk image of it.
One of the new programs was Norton System Works 2005 premiere - which includes the new version of ghost V.9. I set it off backing up before going to bed last night, and this morning I awoke to find a BSOD - page fault in nonpaged area - stop 0x00000050 Ntfs.sys.
I checked about online, found lots of suggestions to check the memory - and sure enough after running memtest86 - my memory had errors, I swapped another stick of RAM in, ran memtest again - fine.
Tried rebooting - same thing. my system is dual boot - both OS's give this same problem.
Tried booting to the recovery console - same thing.
I have removed all cards apart from my graphics card checked it with yet another stick of RAM but what ever I do does not seem to make the slightest bit of difference.
I'm stuck! Can anyone offer any assistance?
Thanks
Spotta.
Last edited by spotta; 23rd February 2005 at 10:52.
Reason: now have dump data
Didn't find the information you thought to find? Check out these Similar Threads
After experimenting
I have managed to boot up using my original stick of RAM in slot 3 rather than slot 0 and by disconnecting every hard drive and optical on the system apart from my boot drive.
I have three minidumps for today - here is the data from the most recent one
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022305-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Feb 23 09:40:24.732 2005 (GMT+0)
System Uptime: 0 days 0:02:07.222
Loading Kernel Symbols
........................................................................... .....................................................................
Loading unloaded module list
....
Loading User Symbols
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {18e, 2, 0, 804e3f27}
*** ERROR: Module load completed but symbols could not be loaded for a347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for d347bus.sys
Probably caused by : memory_corruption
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000018e, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804e3f27, address which referenced memory
I see it says memory corruption near the top - is this definately the cause of my problems?
Have to go and do some work now, but I'll be leaving it running - hopefully it'll be alright when I get back.
This is the debugger telling you that the in-memory version of this file does not match the on-disk version. For the vast majority of these cases, its a direct result of bad ram, overclocking, bad timing, etc.
I have managed to boot up using my original stick of RAM in slot 3 rather than slot 0 and by disconnecting every hard drive and optical on the system apart from my boot drive.
im glad that got you into the machine, my guess it was the thermal cycling that made that ram behave, more than swapping slots. Have you tried putting it back in slot 0? wonder if you lost that slot..
This is really a hardware problem at this point, not my area of expertise, but you have some swap and fiddle in your future.
Well - if anything it is now worse!
I am using a stick of RAM (256mb) that works in 2 other machines fine and passes Memtest86. every single PCI card and IDE device is disconnected apart from my boot drive.
Now it gets to the verifying DMI pool data screen then reboots. it will just keep doing this if I do not switch it off.
I have tried a different power supply - no joy
Do you think my motherboard could be faulty?
regards
Spotta
passes Memtest86 This is NOT an authoritative test. It can only indicate a positive, and software testers generally cannot report most errors that occur with ram. The machine that tests ram is a dedicated hardware device.
However, i dont think its the ram, since youve tested some good permutations. motherboard, BIOS, CPU are all on the list of 'whats next'
ntfs.sys BSOD was caused by my 60GB drive - the one where ghost 9 was writing the image file too - it caused the same problem on 2 other machines when connected and I have now done a low-level format on it and it seems ok - not sure if I should trust it 100% anymore though....... this drive had my second OS on it which was backed up on another drive so no data lost.
My Main OS drive also had problems - this caused the continual rebooting. once I had it connected to another PC with it's own OS and booted it up disk check ran and found lots of problems. I ended up with 410MB of recovered files in my found.000 folder.
I have been running my original stick of 512MB since last night (still gives errors in memtest) and have not had any further problems yet.....
Do you think my memory has slight errors which although do not cause any problems in day to day running - caused the new Norton Ghost 9 to crash, corrupting both hdd's in the process?
I think I'll go back to the old Ghost for now that backs up drives in pc-dos mode rather than when the OS is running.
Although I have a RAID mobo, after hearing lots of problems people have rebuilding RAID arrays, I have always had lots of hdd's installed without RAID and manually made sure that every important partition in my machine is cloned to a disk image on a seperate hdd somewhere.
I shall stick to doing things this way as otherwise I am sure I would have lost a hell of a lot of important data.
Do you think my memory has slight errors which although do not cause any problems in day to day running - caused the new Norton Ghost 9 to crash, corrupting both hdd's in the process?
This is like playing roulette. at some point, your going to get a winner.
Joe - does this mean you think I am correct?
I have already ordered a new stick - I have spent 2 days pulling my hair out getting my PC back to how it is now and would just like some confirmation from people who probably know a lot more than me.
If I wanted a riddle to solve - I would have gone elsewhere.
I realise that you are trying to help me, but could you be a little less cryptic
