Ntfs.sys bsod infinite reboot cycle

Status
Not open for further replies.

BrandonC

Posts: 8   +0
So..the title basically completely describes the problem. My girlfriends computer decided it wouldn't reboot one day. Nothing new was added, there were no previous issues...but when they tried rebooting it one day it decided to go to a blue screen instead of loading. you can get to the option where it asks about safe mode, but once you try to execute it...it doesn't work...i don't know if i need minidumps for you to help me, but i don't know how to get those. i figured you would need to get onto the desktop for it..but i can't do that. If it helps at all someone posted one of these in a thread i was looking at earlier, but he was the ONLY one in the thread not answered..which figures...i'll post what he said.
 
purpleclub
Newcomer, in training Member since: Sep 2005, 3 posts

BSOD & NTFS.SYS-infinite reboot - STUCK!!!

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

Hiya,

I've been reading your responses about the BSOD and ntfs.sys files. Hopefully someone can lend a hand with their expertise!

I got the bsod one day out of the blue. Nothing changed. I've reseated ram, same thing. I cannot boot to the drive at all. Infininte reboot cycle. Can't load ghost as it locks. Can't boot hdd as slave as pc reboots. Cannot get to safe mode. Cannot access drive in anyway, shape or form except via ntfsdos but read only. Cannot chkdsk /f...Nothing. I'm stuck and have been banging my head for 3 days now until I came across the posts.

Thanks so much in advance if anyone can help.


dump below-------


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


Loading Dump File [C:\Documents and Settings\Administrator\Desktop\RBEAR PC CRASH FILES\MINI08~1.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: Tue Aug 30 01:20:11.843 2005 (GMT-4)
System Uptime: 0 days 0:20:45.428
*********************************************************************
* 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 10000050, {f12ac544, 1, f84b4f4e, 3}

***** 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
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
 
Status
Not open for further replies.
Back