«

[jg007]

Hi guys,

For a few months I have been getting ocasional BSOD's and this month so far I have already had 8 . I have analysed the dumps and nothing shown indicates where the problem is , scanning the net I can see sugestions for BSOD's advising to replace the memory, PSU, graphics card etc.

but.... here is the problem , I have no money at present so where can I start as I can't just run through them all and as my current machine is a 754 Athlon chipset if I go and replace the memory and the MOBO fails shortly then any new mobo will not use the same memory and as it is AGP graphics the same problem aplies for that.

so basically looking for people's opinions and any sugestions for further checks

I have stuck an example dump below in case anybody knows about reading them -


************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 00480800, The address that the exception occurred at
Arg3: bacdbc80, Exception Record Address
Arg4: bacdb97c, Context Record Address

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


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

FAULTING_IP:
+480800
00480800 ?? ???

EXCEPTION_RECORD: bacdbc80 -- (.exr 0xffffffffbacdbc80)
ExceptionAddress: 00480800
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00480800
Attempt to execute non-executable address 00480800

CONTEXT: bacdb97c -- (.cxr 0xffffffffbacdb97c)
eax=bad0b148 ebx=00000000 ecx=00000000 edx=8860db88 esi=8860db98 edi=00000000
eip=00480800 esp=bacdbd48 ebp=bacdbd60 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
00480800 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

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

WRITE_ADDRESS: 00480800

FAILED_INSTRUCTION_ADDRESS:
+480800
00480800 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 805af80f to 00480800

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacdbd44 805af80f 8860dbb0 00000000 8860dbb0 0x480800
bacdbd60 805afcca 8860dbb0 00000001 80558b20 nt!ObpRemoveObjectRoutine+0xdf
bacdbd74 80533fe6 00000000 00000000 89ac5b30 nt!ObpProcessRemoveObjectQueue+0x38
bacdbdac 805c4cce 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
bacdbddc 805411c2 80533ee6 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
nt!ObpRemoveObjectRoutine+df
805af80f 8b4d08 mov ecx,dword ptr [ebp+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ObpRemoveObjectRoutine+df

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9c

STACK_COMMAND: .cxr 0xffffffffbacdb97c ; kb

FAILURE_BUCKET_ID: 0x7E_BAD_IP_nt!ObpRemoveObjectRoutine+df

BUCKET_ID: 0x7E_BAD_IP_nt!ObpRemoveObjectRoutine+df

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

[Eagle of Fire]

And what might be a BSOD? Sorry, but I seem to be less technically knowledgable in such terms. :P

[_r.u.s.s.]

http://www.google.com/

[The Fifth Horseman]

Blue Screen Of Death - a slang description for the Windows' critical failure report screen.

[velik_m]

pointless and stupid acronyms aside:
os version?

cpu?
mobo?
graphics card?
...
you know important info...

have you tried contacting MS support? What did they say?

anyway, if the crashes are completely random and you're sure it's not some viruses, it's probably motherboard.

[Eagle of Fire]

Blue Screen Of Death? You mean, normal operation when using Windows 98???

BSOD doesn't exist in XP. You either can close the faulty applications, the computer freeze altogether or one of your hardware components is dying. End of story.

[_r.u.s.s.]

no .. there is also bsod in win xp. your computer is just defaultly set to hard-reset itself. and why dont you just use the link i provided you before posting anything hm?

[Eagle of Fire]

I'd do if you had posted anything usefull up to now, Russ...

[_r.u.s.s.]

cause asking kind of questions like "WHAT IS MACROMEDIA'S OFFICIAL SITE PLZ?" is absolutely useful

by the way, in the post above i explained why dont you see bsod on your xp

[Eagle of Fire]

Any thought on helping the thread starter instead of posting random nonsense?