ive been receiving this error during windows normal functioning and i cannot identify whats wrong, can anyone help me?

thanks in advance

the windos minidump and hijackthis logs:

Attached Files

errorlogs.zip (21.7 KB, 2 views)

The .tmp file is unreadable by the Windows Debugger Tool. We need your minidump files as they appear in your minidump folder.

How to find your Minidump Files:

My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

It is these files that we need (not the folder). Attach to your next post. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip. Please do us a favor and don’t Zip each one individually.

sorry, i dont have a minidump folder, ill try to post the windbg:

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {719ddf5d, 2, 0, 719ddf5d}

Probably caused by : svchost.exe ( INVALID_CONTEXT )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 719ddf5d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 719ddf5d, address which referenced memory

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


READ_ADDRESS: 719ddf5d

CURRENT_IRQL: 2

FAULTING_IP:
+0
719ddf5d ?? ???

PROCESS_NAME: svchost.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

DEFAULT_BUCKET_ID: DRIVER_FAULT

FAILED_INSTRUCTION_ADDRESS:
+0
719ddf5d ?? ???

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: svchost.exe

IMAGE_NAME: svchost.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_svchost.exe_CODE_AV_BAD_IP_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_svchost.exe_CODE_AV_BAD_IP_INVALID_CONTEXT

Followup: MachineOwner
---------
the hijackthis log is attached

hope this helps

Attached Files

hijackthis.log (8.3 KB, 2 views)

0xD1 errors are usually caused by faulty drivers but your analysis doesn't lend to any specific driver(s).

I am not a reader of hijackthis logs but I need to ask about your security software. I notice Symantec, AVG8, and the Outpost Firewall. Are you running more than two firewalls, antiviruses, or antispyware programs?

im using avg8, outpost and symantec norton ghost for recovery purposes, and thats the cuestion, the bsod doesnt point to any driver

We have seen TONS of people having issues with AVG 8 and we have advised them to uninstall and then use AVG's removal tool. By the way, is this the security suit or just the antivirus?

Outpost Firewall is known to cause that crash. See the following thread for the same crash.

http://www.techspot.com/vb/showthrea...NVALID_CONTEXT

I just got REALLLY tired of the system rebooting for no apparent reason, so
I decided to clean up the Services issue. THEELDERGEEK.COM has some
inneresting info on what you DO need versus what you DON'T need when running XP HOME (or PRO) without a home-network...which pertains perhaps
to Most of us, me included.

Forget dump analysis, installing a new graphics board or memory,
or whatever else you've seen. This seems to have worked for me, at least
to the point where things will run fine for HOURS instead of MINUTES. But, no,
I'm not overclocking nor am I gaming, so my approach might fit your
circumstances. BUT..a clean(er) machine is a happy(er) machine, and mine
runs happily with (only) 22 processes; I can probably decrease that by another
five, I betcha.

I can post a 'works with these settings' list here when I get time, but for now
I'll just say that >>killing the DCOM stuff<< seems to have also killed the bugchecks. (I was actually amazed...) Apparently Windoze has advanced to the point where interactions between it's plethora of parts are not actually understandable.

Getting a (more) stable system by disabling DCOM doesn't mean that DCOM
was the problem but that it, plus something else, had a wierd synergistic BAD
effect on XP, even with SP2 installed. Could've been a memory leak, a conflict
of some kind...or just the bad memory reclamation protocols I've heard are
present in XP. I can only =imagine= what Win7 must be like...yikes.

I hope this helps. Let me know, thanks.
If it works...hey, send cash!! <G>

First remove Norton Ghost when you get BSOD screens. Norton Ghost 9.0 can cause random BSOD crashes.

Albert