Start-up problem

Kristopherus

Booting up is sometimes a real pain for me.I have a Medion 8800 Pentium 4 machine.Sometimes it will start ok, and the shut down again.When I restart it it will take ages (3-5 mins) to go from the Windows XP screen to the Welcome screen. Then it will show the following message: "The system has recovered from a Serious Error . Click here to see the details." When you click "here" you can read the Error Signature. It goes as follows: "BCCode:ea BCP1:822919A0 BCP2: 82ACCEF8 BCP3:82AA1700 BCP4:00000001 OS Ver:5_1_2600 SP 2.0 Product 768-1"

Can anyone explain/ help ?

Standard Toaster

When it says "Click here to see details", can you post up that info?

Kristopherus

"BCCode:ea BCP1:822919A0 BCP2: 82ACCEF8 BCP3:82AA1700 BCP4:00000001 OS Ver:5_1_2600 SP 2.0 Product 768-1"

These are the details. There is another message coming up referring to files in Documents & Settings that I will give next time it happens. Funnily enough it started up perfectly today !!!!

Standard Toaster

The file that it mentions in "Documents & Settings" is a crash dump file....can be extremely helpful.

Before closing the error browse to where the dump file is and copy it to your desktop. Reason is, once you close the error message down the dump file is deleted.

Feel free to post the file here and we'll have a look. Otherwise, have a look in the event viewer under system and see if the logs report anything.

Start/Run and type "Eventvwr.msc"

cloinsigh

Check the stability of your harddrive. Failing hardware can often throw up odd and intermittent issues.
Click start>Run and type in CMD
In the black window type in chkdsk and press enter. If this reports any error your can attempt a fix by typing in chkdsk /f
This will reboot your PC and attempt to correct issues on your harddrive.

Good luck and let us know how you get on...

Kristopherus

Been away for the past day. Thanks for your help, Edge and Cloinsigh. Have run chkdsk and restarted ok after that. The technical info is:
Document & Settings\name\name\Temp\WERb2d3.dir00\mini072008_01.dmp. There is a second file listed similarly: \WERb2d3.dir00\sysdata.xml.

I hope I have given enough info.

Standard Toaster

Is the file "c:\Document & Settings\name\name\Temp\WERb2d3.dir00\mini072008_01.dmp" still there? Can you email it to me??

Kristopherus

I'm away for the next few hours. Will do it when I get back.

Standard Toaster

No problem. Like I said in my second post if you close the error it tends to delete these two files. So you may find they're no longer there when you get back.

The time to copy them is when the error is displayed.

If you do manged to get the dmp file pm me and you can fire it over.
It will most likey tell us the cause of the crash.

Standard Toaster

Ok, Chris has sent me the minidump. See below from crash dump:

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


Loading Dump File [C:\Users\***\Desktop\Mini071708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*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_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
Debug session time: Thu Jul 17 22:35:26.452 2008 (GMT+1)
System Uptime: 0 days 0:12:47.022
Loading Kernel Symbols
................................................................................................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {82972410, 82aa5e10, 82aab648, 1}

Probably caused by : nv4_disp.dll ( nv4_disp+4bc4 )

Followup: MachineOwner

---

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 82972410, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 82aa5e10, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 82aab648, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

Debugging Details:

---

FAULTING_THREAD: 82972410

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from bf9d6322 to bf9d9bc4

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8aa1878 bf9d6322 e20c9010 00000001 00000010 nv4_disp+0x4bc4
b8aa1c0c bf9d73a9 e1e71e90 e127b4e8 00000000 nv4_disp+0x1322
b8aa1fb0 bf9f75eb e1e71e90 e127b4e8 00000000 nv4_disp+0x23a9
b8aa1fdc bf805cfa e1e71e90 e127b4e8 00000000 nv4_disp+0x225eb
b8aa2028 bf83e767 e1e71e90 e127b4e8 00000000 win32k!WatchdogDrvCopyBits+0x53
b8aa2250 bf84c385 e1e71e90 00000000 00000000 win32k!EngCopyBits+0xcb
b8aa230c bf84a640 00000020 00000000 00000010 win32k!GreGetDIBitsInternal+0x79f
b8aa2398 bf84a4ee 04050a21 b8aa2448 00000000 win32k!ProcessAlphaBitmap+0xeb
b8aa23c8 bf84a24f e1249168 b8aa244c b8aa2468 win32k!_SetCursorIconData+0x1a3
b8aa248c 804de7ec 000103b7 014bdd64 014bdd74 win32k!NtUserSetCursorIconData+0x166
b8aa248c 7c90eb94 000103b7 014bdd64 014bdd74 nt!KiFastCallEntry+0xf8
014bdd84 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .thread 0xffffffff82972410 ; kb

FOLLOWUP_IP:
nv4_disp+4bc4
bf9d9bc4 6639500e cmp word ptr [eax+0Eh],dx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp+4bc4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3d4722bd

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2002_07_31

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2002_07_31

Followup: MachineOwner

---

It's your Nvidia video card driver causing the bluescreens....nv4_disp.dll to be exact.
Try the lastest driver from them for your card.
Also, see here regarding the driver being stuck in an infinite loop.