BSOD_driver_irql_not_less_or_equal

[Torey]

Hi I don't get BSOD Often maybe I would say once a night if I am using it all day. Weird enough it only seems to happen to me very early in the morning like 3AM to 6AM. I know that might seem like coincidence but it's only really when it happens.

Anyhow I really am not sure where to start I was wondering if someone could look at my dump files and maybe point out what is causing it.View attachment 50594

i use windows 7 32 bit
amd althon 64x2 5600 2.8ghz
9800gtx
2 gb ram
590sli mobo
also my net sometimes randomly stops working and i have to trouble shoot it, it gets fixed right away but is a big annoyance, says it has to reset something, certain web pages will do it when i first load them after a restart quit annoying

 

[Torey]

If anyone needs anymore info tell me please

 

[ickymay]

windows debugger came up with hardware error for 3 of your minidumps but the others showed ntkrpamp.exe .......

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {2420016, 2, 0, 82e57a5b}

Probably caused by : ntkrpamp.exe ( nt!KiSignalNotificationObject+18 )

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

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

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: 02420016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82e57a5b, address which referenced memory

I reckon this is going to be your antivirus or a memory problem ?

I suggest completely unninstall your antivirus and if your still having problems burn to CD and run from boot memtest86+ for at least 3 passes to check your ram

your network problem is another matter and we would need more information about any error messages and what windows claims it's fixed in order to be able to help