BSOD for unknown reasons, IRQL_NOT_LESS_OR_EQUAL

[MrPatko0770]

Hi,
ive been having BSOD crashes since this Monday. Ive tried to fix them by cleaning up some space, defragment disks and used various programs to find and fix problems, but nothing helped.
So I came here to ask for help.

The crash occurs at least once a day.
I used BlueScreen to view the dump file:
Bug check string: IRQL_NOT_LESS_OR_EQUAL
Bug check code: 0x1000000a
Parameter 1: 0x00000000
Parameter 2: 0x00000002
Parameter 3: 0x00000001
Parameter 4: 0x8304e813
Caused by driver: ntoskrnl.exe

I included a .zip file which contains dump file, System Health Report and Windows_NT6_BSOD_jcgriff2 folder.

My PC specs:
Windows 7 Ultimate 32bit
I dnot know what Original OS means, but my PC has AMIBIOS N6-8 and Win7 was the only OS on this PC.
OEM version
PC has 2 or 3 years.
OS has the same.

Thank You in advance.

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\BSODDmpFiles\MrPatko0770\Windows_NT6_BSOD_jcgriff2\021012-26265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x83010000 PsLoadedModuleList = 0x83158810
Debug session time: Fri Feb 10 12:05:39.015 2012 (GMT-7)
System Uptime: 0 days 0:44:34.499
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {0, 2, 1, 8304e813}

Probably caused by : ndis.sys ( ndis!NdisMIndicateReceiveNetBufferLists+52 )

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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8304e813, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 83178718
Unable to read MiSystemVaType memory at 83158160
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!memcpy+33
8304e813 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  javaw.exe

LAST_CONTROL_TRANSFER:  from 8881bab7 to 8304e813

STACK_TEXT:  
807e6d0c 8881bab7 00000000 8821f74a 000005c8 nt!memcpy+0x33
WARNING: Frame IP not in any known module. Following frames may be wrong.
807e6e10 8ccefc1e 8cd449cc 87e44120 8735b0e0 0x8881bab7
807e6ee4 8cd44309 87579000 00000000 807e6f10 ndis!NdisMIndicateReceiveNetBufferLists+0x52
807e6f20 8ccef9f4 8755fe3c 0055fe28 00000000 ndis!ndisMiniportDpc+0xe2
807e6f48 830784b5 8755fe3c 8755fe28 00000000 ndis!ndisInterruptDpc+0xaf
807e6fa4 83078318 807c6120 a6982620 00000000 nt!KiExecuteAllDpcs+0xf9
807e6ff4 83077adc b2bc8ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e6ff8 b2bc8ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
83077adc 00000000 0000001a 00d6850f bb830000 0xb2bc8ce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ndis!NdisMIndicateReceiveNetBufferLists+52
8ccefc1e f6432804        test    byte ptr [ebx+28h],4

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ndis!NdisMIndicateReceiveNetBufferLists+52

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ndis

IMAGE_NAME:  ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf58

FAILURE_BUCKET_ID:  0xA_ndis!NdisMIndicateReceiveNetBufferLists+52

BUCKET_ID:  0xA_ndis!NdisMIndicateReceiveNetBufferLists+52

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

ndis.sys is related to your network, so the first things to check are network adapter drivers being up to date, possible corruption of network adapter drivers, and antivirus software problems. Other possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Backup... Hardware...

Re-install your network adapter drivers (if you already have up to date drivers they may be corrupt and need to be re-installed) using the following method.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

Uninstall and re-install your antivirus software. Use How do I manually uninstall my Windows ESET security product? - ESET Knowledgebase to completely remove ESET software before installing it again.