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 :unsure: 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
---------

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

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

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.

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

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.

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?

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

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

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

Your Windows version is most important info. BSOD is indeed normal operation in Win9X, the first normal step would be formatting the Windows partition. BSODs can appear in XP as an anomality caused, I heard, either by hardware failures, or by low-level software such as drivers, firewalls, antivirus etc --not by high-level normal applications which are closed upon malfunction by Windows. I'd suggest that you run Windows without these low-level programs running, or better yet you boot in safe mode, and see if the BSODs still appear, the affirmative case would reinforce the idea that it's caused by hardware, but don't assume the worst right from the start.

Win XP SP2 , and i've already ran the re-install everything game.

Zonealarm is occasionaly buggy but I have never had it cause BSOD, I re-installed it anyway.
Problem was happening although a little less frequently before xp re-install about 1 1/2 months ago
Graphics, network card and sound drivers all re-installed. (twice :)

I may go for another XP re-install , I am just starting to think that it is more likely hardware at present as it is very random and doesn't seem to be caused by any specific driver also the crash analysis is not showing anything usefull, ie: any driver at fault and only mentions ntoskrnl

BSOD does happen in SP2 as said when you set the computer to not reboot, I had never seen it previously at least on my machine but it seems to be ahappening all too frequently now although as it is still only once a day at most and cannot be caused to happen it is a bit difficult to start running in safe mode etc.

ms support :w00t: , what at about £33 a shot!, at least that was about the price last time I saw it .

<div class='quotetop'>QUOTE(Eagle of Fire @ Aug 9 2007, 07:47 PM) [snapback]303967[/snapback]</div>what did you just do with your post? go in a corner.

Stop trolling this thread Russ, else I'm going to report you. Moderator flag or not.

jg007: If you have an old model or you moved your computer recently, I'd check if all the cards were all well placed in their slots. Old models had a lot of problem of this kind before they created the new fit slots, but even the new slots are not 100% full proof from big bumps on the road if you moved the tower.

If it's indeed an hardware problem... You'd probably have no other option than find the culprit and replace it. It would be best if you simply take the computer to a computer store for them to check everything, but since you said you don't have a lot of money to waste on the problem right now...

Hope I can be of help in any way.

Review:
"0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not
catch. There are numerous individual causes for this problem, including
hardware incompatibility, a faulty device driver or system service, or some
software issues. Check Event Viewer (EventVwr.msc) for additional
information."

A majority of the readout seems to to point at network driver compatibility issues.

Should you have Vista,
lots of users are having issues with Vista incompatibility to older hardware/software drivers.

From what the data reads, it may be having trouble with your network card , "Bad ip" IP fault.

If this is the case, query which software/hardware that you installed in the past caused the computer to crash.

Ntkrnlpa.exe can also be corrupted.
I would go to the windows recovery console using your xp/vista cd and run sfc /scannow to find and replace corrupted system driver.

Can you log into safe mode normally without experiencing crashes?

If so go into that mode, Check device manager for any network card conflicts.

Try disabling the network card drivers one by one (wireless, bridge, mac, local area) until you finally find the culprit of the blue screens.

There may be background services, startup applications creating a conflict with other drivers.
go to Start/ run, msconfig. Then check the services tab, and check the box (hide all microsoft services).

Disable all of the services temporarily, repeat this in the startup tab.
uncheck all running non-microsoft services.

Warning, disabling services in msconfig is not recommended it (unchecking services is like disabling them).
To manually restart,start or stop a service, go to start, run services.msc.

If it allows the system to function properly again, slowly re-enable each service/startup app. until the one causing the trouble is discovered.

This is the last, and usually most unlikely solution for some machines.
Run memtest and check for possible memory/motherboard errors.
Try running memtest86
http://www.memtest86.com/. To see if you get any errors,and you have replaced the ram and or cpu, then the motherboard may be at fault.

<div class='quotetop'>QUOTE(strider @ Aug 10 2007, 06:37 AM) [snapback]304018[/snapback]</div>Thanks,

I did wonder if it might be the network card but I am also not sure if that ip bit is a red herring as it could relate to another type of ' ip ' as the other text doesn't seem to be network pointing but then I'm not to sure at that level!.

one of the bigest problems is that it can be fine for a few days making it a bit impractical to run in safe mode or start disabling things!, also I play a lot with the PC and make so many changes it can be difficult to pinpoint which specific one may have caused this :)

might try SFC fix , i'm never too sure how this works though when some files in the OS might have been upgrade by service packs / IE 7 etc. I don't tend to have many services running so not sure what is left to disable but I will look again

<div class='quotetop'>QUOTE(Eagle of Fire @ Aug 10 2007, 03:04 AM) [snapback]304011[/snapback]</div>hmm , probably should check that as I did move it again before it got worse so maybe if it was loose I may have unseated it, at the same time I will remove the extra 512MB that I stuck in incase that has made it worse