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

Getting blue screen when booting up


  • Please log in to reply
5 replies to this topic

#1 GT80

GT80

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:01 AM

Posted 02 June 2009 - 11:40 AM

Yesterday I noticed my computer checking the floppy drive every 10 seconds or so. I figured then I must have gotten a virus or just needed a reboot. Before I could reboot I started getting all kinds of random pop-ups for virus protection and what-not. I immediately ran Malwarebytes' anti-malware and it found 28 items. I removed them and then rebooted, and now I get the blue screen with the info below. It happens at the same time every reboot, at the welcome screen just before windows comes up. I can still boot into safe mode no problem and have run anti-malware again and found 9 more items. Since I can boot in safe mode, is there any way I can diagnose this? Thanks for any help, my computer is unusable at the moment. Oh yeah, it's XP Home.

I have gone years with no virus problems at all and recently it's like the door to my computer is wide open or something. I used to use McAfee but it slowed my system down so much I deleted it about a year ago and installed ZoneAlarm and AVG. If I can resolve this problem I would like some advice on how to prevent it from happening again. I don't visit sketchy sites and I never run any programs I'm not sure are 100% safe.

************************************************
A problem has been detected and Windows has been shut down to prevent damage to your computer.

blah blah blah...

blah blah blah...

Technical Information

*** STOP: 0x0000008E (0xC0000005, 0xF79F78D3, 0xF7C4A968, 0x00000000)

*** 0000099D - Address F79F78D3 base at F79F7000, DateStamp 49c97a84

Physical memory dumped
*************************************************

Edit: Moved topic from XP to the more appropriate forum. ~ Animal

BC AdBot (Login to Remove)

 


#2 Supreme Edgeboy Max

Supreme Edgeboy Max

  • Members
  • 52 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Krym, Ukraine
  • Local time:01:01 PM

Posted 03 June 2009 - 03:31 PM

Ctrl+F in My Computer window, Search All Files and Folders with keywords *.dmp and *.mdmp.

This topic here will help you with this - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/ "How to recieve help diagnosing Blue Screens and Windows crashes".

Posted Image


#3 GT80

GT80
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:01 AM

Posted 04 June 2009 - 06:44 AM

I just noticed another problem. I can boot into safe mode but cannot use the keyboard. Mouse ok but one keystroke and it locks the computer.

I'll check the link thanks.

Edited by GT80, 04 June 2009 - 05:32 PM.


#4 GT80

GT80
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:01 AM

Posted 04 June 2009 - 12:58 PM

Ok, here is my crashdump analysis from the latest minidump file

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


Loading Dump File [C:\Documents and Settings\DMACKERM\Desktop\Mini060409-01.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 Personal
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Jun 4 10:05:25.750 2009 (GMT-4)
System Uptime: 0 days 0:00:58.312
Loading Kernel Symbols
...............................................................
...........................................
Loading User Symbols
Loading unloaded module list
..
Unable to load image 00000913, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for 00000913
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f0b788d3, f9a0b968, 0}

Probably caused by : 00000913 ( 00000913+8d3 )

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

kd> !analyze -v
*******************************************************************************
* *
* 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: f0b788d3, The address that the exception occurred at
Arg3: f9a0b968, 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:
00000913+8d3
f0b788d3 6603463c add ax,word ptr [esi+3Ch]

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from f0b78da4 to f0b788d3

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f9a0ba18 f0b78da4 f9a0ba38 0007f9f8 000003fe 00000913+0x8d3
f9a0ba74 f93a26bb 00000000 e2160d80 f9a0bc98 00000913+0xda4
f9a0ba84 f93cb387 ff915390 ff8011f8 00000000 Ntfs!NtfsCompleteRequest+0xac
f9a0ba94 f93cb307 ff8011f8 ff801340 ff78c578 Ntfs!NtfsQueryDirectory+0xc96
f9a0bc98 f93ca2e8 ff915390 ff8011f8 81b09100 Ntfs!NtfsQueryDirectory+0xb89
f9a0bccc f93a96e0 ff915390 e2160be8 ff915490 Ntfs!NtfsCommonDirectoryControl+0xbc
f9a0bd74 804e426b ff915390 00000000 ff9a8da8 Ntfs!NtfsFspDispatch+0x1a3
f9a0bdac 8057aeff ff915390 00000000 00000000 nt!ExpWorkerThread+0x100
f9a0bddc 804f88ea 804e4196 80000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
00000913+8d3
f0b788d3 6603463c add ax,word ptr [esi+3Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: 00000913+8d3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: 00000913

IMAGE_NAME: 00000913

DEBUG_FLR_IMAGE_TIMESTAMP: 49c97a84

FAILURE_BUCKET_ID: 0x8E_00000913+8d3

BUCKET_ID: 0x8E_00000913+8d3

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

#5 GT80

GT80
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:01 AM

Posted 07 June 2009 - 07:49 AM

bump

#6 GT80

GT80
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:02:01 AM

Posted 08 June 2009 - 11:53 AM

Just used F8 on reboot and chose "Last known good configuration" option. Booted up normally and everything seems fine. Did MBAM scan and nothing was found. Hopefully I'm ok now. Still wish I knew what got me. :thumbsup:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users