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

BSOD - please help


  • Please log in to reply
14 replies to this topic

#1 Gary002G

Gary002G

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:31 PM

Posted 24 February 2009 - 06:19 PM

I left my laptop in a perfectly working condition and haven't touch it for couple of days.
When I came back I found it on a login screen. I did not logout.
When I logged in it shows me a blue screen of death for a fraction of a second and went into automatic reboot.
I tried to login again and again it BSODed and rebooted.
It happens again and again. It does not react to F8 to go to safe mode.
I can't search for dump file and it happens to quick to read the screen.
BSOD always occurs but sometimes it happens immediately after clicking on login icon and sometimes it does show me my desktop for 1-3 sec while starting something in background.
Can someone help me to get out of this vicious loop.

BTW, I did not install or download anything there for over 3 months and I do have antivirus and spybot software installed and up-to-date.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,876 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:31 PM

Posted 24 February 2009 - 06:46 PM

You can try removing the CMOS battery...in order to get CMOS defaults. See http://www.computerhope.com/issues/ch000976.htm

If you have a Microsoft XP CD, you can try to either do a repair install of XP...or run some of the repair commands from the Recovery Console. Recovery disks/restore disks are not Microsoft XP CDs.

System manufacturer and model?

Louis

#3 Gary002G

Gary002G
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:31 PM

Posted 26 February 2009 - 12:12 AM

You can try removing the CMOS battery...in order to get CMOS defaults. See http://www.computerhope.com/issues/ch000976.htm

If you have a Microsoft XP CD, you can try to either do a repair install of XP...or run some of the repair commands from the Recovery Console. Recovery disks/restore disks are not Microsoft XP CDs.

System manufacturer and model?

Louis

I do not need to remove CMOS battery. I can get to the BIOS (F2) when it is booting. It is windows that is broken.
I do have CD somewhere but find it is a long story.
It is Fujitsu Lifebook (N series) dual core 1.73 GHz, 2GB RAM, WinXP Media Center SP3.

#4 Gary002G

Gary002G
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:31 PM

Posted 26 February 2009 - 02:40 AM

Whoa, a miracle did happen. On cold restart I managed to boot windows in safe mode and log into it without crashing.
I found the last minidump.
I downloaded the debugger and :thumbsup: windows in the safe mode won't let me install it.
I then copied the file on a flash drive and analyzed it on another computer.

It did not give me any insight, though, for the cause of the crash.
Here is the dump report and if someone can explain it to me and tell me how to fix it I'll be very grateful.
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [I:\Minidump\Mini022409-06.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: 
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Tue Feb 24 19:25:54.234 2009 (GMT-8)
System Uptime: 0 days 0:00:54.796
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image 00000C2B, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for 00000C2B
ERROR: FindPlugIns 8007007b
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, a7bad8b3, bacdf968, 0}

Probably caused by : 00000C2B ( 00000C2B+8b3 )

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

kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: a7bad8b3, The address that the exception occurred at
Arg3: bacdf968, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
00000C2B+8b3
a7bad8b3 6603463c		add	 ax,word ptr [esi+3Ch]

TRAP_FRAME:  bacdf968 -- (.trap 0xffffffffbacdf968)
ErrCode = 00000000
eax=00000058 ebx=0007f9f8 ecx=00000000 edx=00000000 esi=0007f9f8 edi=00000000
eip=a7bad8b3 esp=bacdf9dc ebp=bacdfa18 iopl=0		 nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00010202
00000C2B+0x8b3:
a7bad8b3 6603463c		add	 ax,word ptr [esi+3Ch]	ds:0023:0007fa34=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  6

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from a7badd44 to a7bad8b3

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
bacdfa18 a7badd44 bacdfa38 0007f9f8 000003fe 00000C2B+0x8b3
bacdfa74 ba6176bb 00000000 e345f268 bacdfc98 00000C2B+0xd44
bacdfa84 ba640387 89ba6910 8892d458 00000000 Ntfs!NtfsCompleteRequest+0xac
bacdfa94 ba640307 8892d458 8892d5e8 888ff368 Ntfs!NtfsQueryDirectory+0xc96
bacdfc98 ba63f2e8 89ba6910 8892d458 8a175100 Ntfs!NtfsQueryDirectory+0xb89
bacdfccc ba61e6e0 89ba6910 e345f0d0 89ba6a10 Ntfs!NtfsCommonDirectoryControl+0xbc
bacdfd74 80534c12 89ba6910 00000000 8a238d20 Ntfs!NtfsFspDispatch+0x1a3
bacdfdac 805c61ec 89ba6910 00000000 00000000 nt!ExpWorkerThread+0x100
bacdfddc 80541de2 80534b12 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
00000C2B+8b3
a7bad8b3 6603463c		add	 ax,word ptr [esi+3Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  00000C2B+8b3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 00000C2B

IMAGE_NAME:  00000C2B

DEBUG_FLR_IMAGE_TIMESTAMP:  494ecb6d

FAILURE_BUCKET_ID:  0x8E_00000C2B+8b3

BUCKET_ID:  0x8E_00000C2B+8b3

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


#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:31 AM

Posted 26 February 2009 - 08:15 AM

The dump seems to indicate an problem with the file system (NTFS.SYS) on your hard drive - but the details aren't very clear.

So, I'd first suggest that you run CHKDSK /R from the command prompt (go to Start...Run and type in "cmd" (without the quotes) and press Enter)
Once in the command prompt, type "chkdsk /r" (without the quotes) and press Enter. It may tell you it has to reboot to do this - tell it Yes and then reboot.

Beyond that, I'd suggest a bootable hard drive diagnostic from the manufacturer of your hard drive. A list of the most common one's are here: http://www.bleepingcomputer.com/forums/t/28744/hard-drive-installation-and-diagnostic-tools/
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 Gary002G

Gary002G
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:31 PM

Posted 27 February 2009 - 11:29 PM

I did as recommended and more.
I did run chkdsk /r and after that it BSODed again.
I defragmented the HD but it did not help.
I followed provided link but unfortunately it appears that Toshiba (manufacturer of my HD) does not provide any diagnostic tools.
I found the original CDs that came with the laptop but there is now Windows CD there.
There is a so called recovery CD that will reformat the HD and restore the very original Windows installation.

Any more ideas will be very appreciated.

#7 PcTestCard

PcTestCard

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:11:31 PM

Posted 28 February 2009 - 12:44 AM

Whoa, a miracle did happen. On cold restart I managed to boot windows in safe mode and log into it without crashing.


If you have selected the "Last Know Good Configuration" from the F8 boot menu before the safe mode, you may be able to fix many BSOD error by booting to the windows.

Now, seems too late to do so since you already run the safe mode that aleady earsed the :thumbsup: last known good profile.

Try F8 again and use system restore and restore back to the date when the PC is OK.

Hope this helps!
Bill

#8 Swordie

Swordie

  • Members
  • 792 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Miami, Florida
  • Local time:11:31 PM

Posted 28 February 2009 - 12:47 AM

How do you get onto the last known good config? F8? Or on the reboot?
Who said I couldn't have everything?

#9 blake.403

blake.403

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Local time:11:31 PM

Posted 28 February 2009 - 01:37 AM

Seeing as you managed to get into safe mode (which as we all know is default f8), press f8 on boot again, but instead of selecting safe mode, go to advanced boot options. Once there then disable automatic reboot on system failure, and boot into windows. Once it gives you the BSOD, the system shouldn't reboot, and it will give you an error code. You can type that error code in @ http://support.microsoft.com/ and it will tell you a few solutions to try. Normally its a corrupt registry file or corrupt NTLDR, sometimes you can repair these will little to no data loss by booting off a windows XP disc and going into the recovery console and replacing the 5 registry hive files from a previous snapshot. It will explain the steps on the support page if that's the route to go.

#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:12:31 AM

Posted 28 February 2009 - 08:07 AM

Test your hard drive with the Hitachi Drive Fitness Test ( http://www.hitachigst.com/hdd/technolo/dft/dftnew.htm )
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 Gary002G

Gary002G
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:31 PM

Posted 01 March 2009 - 02:54 AM

Test your hard drive with the Hitachi Drive Fitness Test ( http://www.hitachigst.com/hdd/technolo/dft/dftnew.htm )

But my disk is not Hitachi, it is Toshiba.

#12 blake.403

blake.403

  • Members
  • 23 posts
  • OFFLINE
  •  
  • Local time:11:31 PM

Posted 05 March 2009 - 03:44 PM

Seeing as you managed to get into safe mode (which as we all know is default f8), press f8 on boot again, but instead of selecting safe mode, go to advanced boot options. Once there then disable automatic reboot on system failure, and boot into windows. Once it gives you the BSOD, the system shouldn't reboot, and it will give you an error code. You can type that error code in @ http://support.microsoft.com/ and it will tell you a few solutions to try. Normally its a corrupt registry file or corrupt NTLDR, sometimes you can repair these will little to no data loss by booting off a windows XP disc and going into the recovery console and replacing the 5 registry hive files from a previous snapshot. It will explain the steps on the support page if that's the route to go.


Have you tried this yet?

#13 Gary002G

Gary002G
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:31 PM

Posted 08 March 2009 - 05:26 PM

I tried to do it but it was still rebooting after BSOD.
However, I was able to go to the advance boot menu and restore the previous configuration.
Now for three days I do not have problems.

Thanks a lot to everybody.

#14 helen1963

helen1963

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 07 April 2009 - 09:36 PM

OK I have read 5million ( not exaggerating) things in my google search to get rid of this damnedable freaking "login loop" I am going to go :thumbsup: .........I have windows 2000 professional and when I hit F8 and my options come up pleaseeeeee tell me where you see so called..... advanced boot options...that screen is burned into my brain and I see nothing of the sort on there.....
thanks
Helen

#15 helen1963

helen1963

  • Members
  • 73 posts
  • OFFLINE
  •  
  • Local time:12:31 AM

Posted 07 April 2009 - 09:53 PM

sheeeeeeesh you are talking about windows XP aren't you......OK I have officially gone :thumbsup: ......well does anyone have an idea for W2k professional?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users