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

Lock Up On Cold Boot...help Please


  • Please log in to reply
9 replies to this topic

#1 purple69

purple69

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:35 AM

Posted 22 November 2005 - 05:32 PM

When I start my puter after it has been off all day or night, it hangs on boot-up. It hangs on a DOS screen that says "verifying DMI pool" at the bottom. Also all the device irq's are listed higher up on the page. This only happens on cold boot up's. When it happens I hit reset and it boot's up fine. Then boots fine the rest of the day. I have flashed my bios and that did not help. I re-formatted not to long ago and that didn't help. Could this be a power supply problem? Maybe on the initial cold boot up's it is not getting the voltage correct or whatever and needs a second start up to get right? All help appreciated. Thanks.

BC AdBot (Login to Remove)

 


m

#2 acklan

acklan

    Bleepin' cat's meow


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

Posted 23 November 2005 - 12:37 AM

Start by replacing the BIOS battery.
"2007 & 2008 Windows Shell/User Award"

#3 purple69

purple69
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:35 AM

Posted 24 November 2005 - 07:51 AM

Nope. Not the problem. Replaced battery. Its still doing it.

#4 acklan

acklan

    Bleepin' cat's meow


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

Posted 24 November 2005 - 08:32 AM

If you are using XP try chkdsk from RUN.
http://www.microsoft.com/resources/documen...-us/chkdsk.mspx
If you are using '9x try scandsk from command prompt in Safe Mode.
http://support.microsoft.com/default.aspx?...kb;en-us;186365

Lets make sure the hard drive is not acting up.
"2007 & 2008 Windows Shell/User Award"

#5 purple69

purple69
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:35 AM

Posted 24 November 2005 - 07:28 PM

Ok I did the checkdisk from run and it came back with no errors. Also in the last couple days when playing my favorite flight sim, it has crashed twice. The game crashes to a completely blue, blank screen and reboots. I am pretty sure this is not because of the game. The last time this happened when the system was rebooting I went into my bios and checked temps. The mobo was 29c and the cpu 45c. Perfectly exceptable. I am thinking power supply here but dont want to waste what little money I have if this is not the problem. My video card is an ATI 9800 pro and maybe two months old. I am using the latest Catalyst drivers. If it is a vid card issue how would that hang a cold boot?

#6 acklan

acklan

    Bleepin' cat's meow


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

Posted 25 November 2005 - 07:55 AM

Low voltage does strange things to computers. How many watts is your power supply.
"2007 & 2008 Windows Shell/User Award"

#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:35 AM

Posted 25 November 2005 - 11:12 AM

Presuming that you're using XP and haven't changed the error logging features in it (not the error-reporting).

1) Go to your Event Viewer and look for errors in the event logs. When you find an error, right click on it and select "Properties". You'll be looking for, in particular a series of numbers/letters about the error. Post the text of the error message back here and let the troubleshooting begin!

2) Also, a search of your hard drive for "mini*.dmp" (without the quotes) may reveal some mini memory dumps which can be analyzed to find out the cause of the error.
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.

#8 purple69

purple69
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:35 AM

Posted 25 November 2005 - 06:04 PM

Ok. Here's what I've got. My power supply is an Antec 430w.

Mini111005-01.dmp
Mini111505-01.dmp
Mini111905-01.dmp
Mini111905-02.dmp
Mini112205-01.dmp
Mini112405-01.dmp

These are all in C:\WINDOWS\Minidump and 92 KB.

Windows error reporting:

10/21/2005 4:30 PM Application Hang Hanging application iexplore.exe, version 6.0.2900.2180, hang module hungapp, version 0.0.0.0, hang address 0x00000000.&#x000d;&#x000a;

10/21/2005 9:18 PM Application Error Faulting application hpoevm08.exe, version 1.0.0.0, faulting module ole32.dll, version 5.1.2600.2726, fault address 0x0002d8f5.&#x000d;&#x000a;

10/22/2005 8:27 AM Application Error Faulting application hpoevm08.exe, version 1.0.0.0, faulting module ole32.dll, version 5.1.2600.2726, fault address 0x0002d8f5.&#x000d;&#x000a;

10/27/2005 4:10 PM Application Error Faulting application autorun.exe, version 0.0.0.0, faulting module , version 0.0.0.0, fault address 0x00000000.&#x000d;&#x000a;

11/1/2005 7:28 PM Application Error Faulting application autorun.exe, version 0.0.0.0, faulting module autorun.exe, version 0.0.0.0, fault address 0x000030e8.&#x000d;&#x000a;

11/11/2005 5:00 PM Application Error Faulting application uninstall.exe, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.&#x000d;&#x000a;

11/18/2005 7:12 PM Application Hang Hanging application lockon.exe, version 1.1.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.&#x000d;&#x000a;

11/18/2005 7:12 PM Application Hang Hanging application lockon.exe, version 1.1.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.&#x000d;&#x000a;

11/19/2005 2:48 PM Application Hang Hanging application QuickTimePlayer.exe, version 7.0.3.50, hang module hungapp, version 0.0.0.0, hang address 0x00000000.&#x000d;&#x000a;

11/20/2005 11:02 PM Application Error Faulting application lockon.exe, version 1.1.0.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00011f6c.&#x000d;&#x000a;

11/21/2005 4:01 PM Application Error Faulting application lockon.exe, version 1.1.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.&#x000d;&#x000a;

11/22/2005 4:21 PM Application Error Faulting application lockon.exe, version 1.1.0.0, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00011f6c.&#x000d;&#x000a;

11/24/2005 8:06 AM Application Error Faulting application lockon.exe, version 1.1.0.0, faulting module dxrenderer.dll, version 0.0.0.0, fault address 0x00036ff1.&#x000d;&#x000a;

11/5/2005 5:10 PM Application Error Faulting application naturalpoint.exe, version 3.1.2.0, faulting module naturalpoint.exe, version 3.1.2.0, fault address 0x000161ca.&#x000d;&#x000a;

11/5/2005 5:16 PM Application Error Faulting application naturalpoint.exe, version 3.1.2.0, faulting module naturalpoint.exe, version 3.1.2.0, fault address 0x000161ca.&#x000d;&#x000a;

11/6/2005 10:53 AM Application Error Faulting application lockon.exe, version 1.0.0.1, faulting module flight.dll, version 0.0.0.0, fault address 0x0000a058.&#x000d;&#x000a;

11/6/2005 10:53 AM Application Hang Hanging application LockOn.exe, version 1.0.0.1, hang module hungapp, version 0.0.0.0, hang address 0x00000000.&#x000d;&#x000a;

11/6/2005 2:48 PM Application Error Faulting application lockon.exe, version 1.1.0.0, faulting module , version 1.1.0.0, fault address 0x00041074.&#x000d;&#x000a;

11/7/2005 4:09 PM Application Error Faulting application naturalpoint.exe, version 3.1.2.0, faulting module naturalpoint.exe, version 3.1.2.0, fault address 0x000161ca.&#x000d;&#x000a;

11/7/2005 4:16 PM Application Error Faulting application naturalpoint.exe, version 3.1.2.0, faulting module naturalpoint.exe, version 3.1.2.0, fault address 0x000161ca.&#x000d;&#x000a;

11/7/2005 4:21 PM Application Error Faulting application naturalpoint.exe, version 3.1.2.0, faulting module naturalpoint.exe, version 3.1.2.0, fault address 0x000161ca.&#x000d;&#x000a;

11/7/2005 4:30 PM Application Error Faulting application naturalpoint.exe, version 3.1.2.0, faulting module naturalpoint.exe, version 3.1.2.0, fault address 0x000161ca.&#x000d;&#x000a;

11/9/2005 8:29 PM Application Hang Hanging application Ventrilo.exe, version 2.3.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.&#x000d;&#x000a;

The natural point (Track IR), Ventrilo and Lock On are all usually running at the same time. (flight sim) I don't see how these app. errors would cause a hang at boot up.

There ya go
Thanks.

Edited by purple69, 25 November 2005 - 06:09 PM.


#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:35 AM

Posted 27 November 2005 - 09:39 AM

OK, since you've found the minidump files - go here for a tutorial on how to use the Dump Check utility: http://forums.majorgeeks.com/showthread.php?t=35246

You won't necessarily use the -v option. So, just cut and paste the information from the report into your next post. The most important parts are the error code and it's parameters along with the file that probably caused it. This one is the most recent one - Mini112405-01.dmp

The application errors won't necessarily cause an error at bootup - but, if a component of that program loads during startup it could be causing a problem.

This procedure won't necessarily solve the problem - but it will let us rule out software problems as a part of the cause. Also, quite a few of the BugCheck and STOP errors will point us towards a piece of hardware that is malfunctioning (which I suspect is the case since the process happens early in the boot).

Right now, I'm guessing power supply or errors in the RAM - but that's just a guess. The results of the dumpcheck should point us in the right direction (generally these errors won't point out power supply issues - but will point out memory problems).
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.

#10 purple69

purple69
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:35 AM

Posted 27 November 2005 - 12:50 PM

Ok here is what I got from debugging my last minidump. It looks like maybe a video card driver or video card problem. I have an ATI Radeon 9800pro.


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


Loading Dump File [C:\WINDOWS\Minidump\Mini112405-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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Thu Nov 24 19:15:55.531 2005 (GMT-5)
System Uptime: 0 days 1:12:29.125
Loading Kernel Symbols
...................................................................................................................................................
Loading unloaded module list
.........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bfb1fc96, b2709a9c, 0}

Unable to load image ati3duag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
Probably caused by : ati3duag.dll ( ati3duag+9ec96 )

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: bfb1fc96, The address that the exception occurred at
Arg3: b2709a9c, 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:
ati3duag+9ec96
bfb1fc96 8985ac080074 mov [ebp+0x740008ac],eax

TRAP_FRAME: b2709a9c -- (.trap ffffffffb2709a9c)
ErrCode = 00000002
eax=00000009 ebx=00c30418 ecx=e16c6018 edx=00010000 esi=e16c66fc edi=00000009
eip=bfb1fc96 esp=b2709b10 ebp=e364a010 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
ati3duag+0x9ec96:
bfb1fc96 8985ac080074 mov [ebp+0x740008ac],eax ss:0010:5764a8bc=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to bfb1fc96

STACK_TEXT:
e364a010 00000000 e364a010 e16af010 e16b0cfc ati3duag+0x9ec96


FOLLOWUP_IP:
ati3duag+9ec96
bfb1fc96 8985ac080074 mov [ebp+0x740008ac],eax

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: ati3duag+9ec96

MODULE_NAME: ati3duag

IMAGE_NAME: ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4328e01f

STACK_COMMAND: .trap ffffffffb2709a9c ; kb

FAILURE_BUCKET_ID: 0x8E_ati3duag+9ec96

BUCKET_ID: 0x8E_ati3duag+9ec96

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

I did a search for this file/folder and it is located in C:\WINDOWS\system32 and C:\WINDOWS\ServicePackFiles\i386. Driver issue?

Edited by purple69, 27 November 2005 - 01:00 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users