Computer throwing fits

Spjong · Apr 24, 2007

Machine specs:

CPU: AMD 64x2 3800+, Fatal1ty motherboard, A-Data 512 mb DDR, nVidia GF 6800GS 256mb, WinXP SP2

Latest BIOS, firmware, drivers etc.

Have it configured to complete memory dump. Ran it through ms debug tools and got the below from it, which I dont have a smoldering clue as to what it means:

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Apr 24 12:55:26.875 2007 (GMT+2)
System Uptime: 0 days 4:53:39.583
Loading Kernel Symbols
.............................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c000001d, 805bf05c, b4909c94, 0}

Probably caused by : hardware ( nt!NtWaitForSingleObject+7a )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: c000001d, The exception code that was not handled
Arg2: 805bf05c, The address that the exception occurred at
Arg3: b4909c94, Trap Frame
Arg4: 00000000

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

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UNDANTAG} Ogiltig instruktion Ett f rs k gjordes att utf ra en ogiltig instruktion.

FAULTING_IP:
nt!NtWaitForSingleObject+7a
805bf05c f08b4048 lock mov eax,dword ptr [eax+48h]

TRAP_FRAME: b4909c94 -- (.trap ffffffffb4909c94)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=b4909d50 edx=821e5b90 esi=b4909d1c edi=00000000
eip=805bf05c esp=b4909d08 ebp=b4909d50 iopl=0 nv up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
nt!NtWaitForSingleObject+0x7a:
805bf05c f08b4048 lock mov eax,dword ptr [eax+48h] ds:0023:00000048=????????
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: explorer.exe

MISALIGNED_IP:
nt!NtWaitForSingleObject+7a
805bf05c f08b4048 lock mov eax,dword ptr [eax+48h]

LAST_CONTROL_TRANSFER: from 804fe6bb to 804f9deb

FAILED_INSTRUCTION_ADDRESS:
nt!NtWaitForSingleObject+7a
805bf05c f08b4048 lock mov eax,dword ptr [eax+48h]

STACK_TEXT:
b490985c 804fe6bb 0000008e c000001d 805bf05c nt!KeBugCheckEx+0x1b
b4909c24 805412d5 b4909c40 00000000 b4909c94 nt!KiDispatchException+0x3b1
b4909c8c 8054126e b4909d50 805bf05c badb0d00 nt!CommonDispatchException+0x4d
b4909ca4 80544beb 813de598 b4909cc4 8060c789 nt!Kei386EoiHelper+0x172
b4909d50 8054086c 00000a98 00000000 b4909d1c nt!KiSwapContext+0x2f
b4909d50 48783f74 00000a98 00000000 b4909d1c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
8b5e5dd0 00000000 00000000 00000000 00000000 0x48783f74

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!NtWaitForSingleObject+7a
805bf05c f08b4048 lock mov eax,dword ptr [eax+48h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!NtWaitForSingleObject+7a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner
---------
Click to expand...

Major Attitude · Apr 25, 2007

Ok.... dont know why. What problem are you having?

Spjong said: ↑

Machine specs:
Have it configured to complete memory dump. Ran it through ms debug tools and got the below from it, which I dont have a smoldering clue as to what it means:
Click to expand...

Log in or Sign up

Computer throwing fits

Spjong Private E-2

Major Attitude Co-Owner MajorGeeks.Com Staff Member

Log in or Sign up

Computer throwing fits

Spjong Private E-2

Major Attitude Co-Owner MajorGeeks.Com Staff Member

Useful Searches