Author Topic: PC Crashes. (Read 4430 times)

Sandra · « **Reply #30 on:** September 12, 2005, 11:51 »

No, its a perceived by XP security issue I think. It may be a false alarm.
We recently had someone with too many connection attempts that was freezing her pc as she had a wi fi enabled connection that wasnt being used.

welshy. · « **Reply #31 on:** September 12, 2005, 15:50 »

How do I check if Wi Fi is on?

Sandra · « **Reply #32 on:** September 12, 2005, 18:03 »

Do you have a Wi Fi enabled device in your pc ?
How do you connect to the internet ?
Look in your Device Manager and see if you have anything saying Wi Fi.

welshy. · « **Reply #33 on:** September 12, 2005, 20:15 »

I connect via Ethernet direct from the modem, no networking involved.

Sandra · « **Reply #34 on:** September 12, 2005, 21:36 »

And you dont have a wi fi adaptor built into your pc at all, either onboard, pci or via a pmcia card ?

welshy. · « **Reply #35 on:** September 13, 2005, 00:32 »

Nope.

Sandra · « **Reply #36 on:** September 13, 2005, 00:45 »

I am as confused as your pc is then as that event ID is pointing us towards something you havent got :?

You could look in the services part of Computer Management and set the IPSEC Services to manually start then that may stop those error messages.
But I cant understand how youre getting them if youre not using XPs firewall or networked :?
If it stops anything working after setting it to manual then reset it to auto again.

welshy. · « **Reply #37 on:** September 13, 2005, 22:52 »

Them errors, don't seem to be effecting my pc it seems, as i've had A few recently, and ironicaly since I started this thread no crashes

welshy. · « **Reply #38 on:** September 22, 2005, 18:56 »

Nooooo crashes are back. This is from the analyze in the minidump.

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 084d769c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804dc0ff, address which referenced memory

There was nothing in the event viewer at the time for the crash, that I can see anyway.