According to the dumps from this month: memory problems are most occuring, second are network drivers and last graphics drivers.
A 0xBE(ATTEMPTED_WRITE_TO_READONLY_MEMORY) is mostly caused by drivers or bad memory.
Same with 0x4E(PFN_LIST_CORRUPT)
As some others also show memory issues
This one shows a write error probably caused by NETIO.sys which points to the network drivers as it is the Network Input/Output System driver from Windows.
Code:
Probably caused by : NETIO.SYS
Processing initial command '!analyze -v; !thread; !sysinfo machineid; !sysinfo cpuspeed; .bugcheck; .time'
( NETIO!NsiEnumerateObjectsAllParametersEx+187 )
Followup: MachineOwner
---------
3: kd> !analyze -v; !thread; !sysinfo machineid; !sysinfo cpuspeed; .bugcheck; .time
*******************************************************************************
* *
* 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: 0501062f, 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: 82eb6059, address which referenced memory
This one almost the same, except that it is a read error.
Code:
Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+187 )
Followup: MachineOwner
---------
Processing initial command '!analyze -v; !thread; !sysinfo machineid; !sysinfo cpuspeed; .bugcheck; .time'
0: kd> !analyze -v; !thread; !sysinfo machineid; !sysinfo cpuspeed; .bugcheck; .time
*******************************************************************************
* *
* 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: 00000008, 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: 82ed9011, address which referenced memory
Then finally an ethernet driver being flagged, although due to a read error.
Code:
*** WARNING: Unable to verify timestamp for Rt86win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
Probably caused by : Rt86win7.sys ( Rt86win7+ce8a )
Followup: Processing initial command '!analyze -v; !thread; !sysinfo machineid; !sysinfo cpuspeed; .bugcheck; .time'
MachineOwner
---------
3: kd> !analyze -v; !thread; !sysinfo machineid; !sysinfo cpuspeed; .bugcheck; .time
*******************************************************************************
* *
* 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: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8bee32bf, address which referenced memory
3: kd> lmvm Rt86win7
start end module name
91e60000 91e85000 Rt86win7 T (no symbols)
Loaded symbol image file: Rt86win7.sys
Image path: \SystemRoot\system32\DRIVERS\Rt86win7.sys
Image name: Rt86win7.sys
Timestamp: Thu Feb 26 10:04:22 2009 (49A65B16)
CheckSum: 0002BDEF
ImageSize: 00025000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Last there is a 0x119(VIDEO_SCHEDULER_INTERNAL_ERROR) which points to the graphics drivers as we can see
Code:
1: kd> k
ChildEBP RetAddr
8d167c48 8c2d6276 nt!KeBugCheckEx+0x1e
8d167c70 9234095a watchdog!WdLogEvent5+0xc6
8d167c88 923409a1 dxgmms1!VidSchiCheckConditionDeviceCommand+0x7a
8d167ca4 92344d3f dxgmms1!VidSchiCheckPendingDeviceCommand+0x33
8d167cf0 92344d77 dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x485
8d167cfc 9236a329 dxgmms1!VidSchiProcessCompletedQueuePacket+0xd
8d167d18 9236b2c7 dxgmms1!VidSchiSubmitDeviceCommand+0x45
8d167d28 9236b516 dxgmms1!VidSchiSubmitQueueCommand+0xaf
8d167d3c 9236b5bd dxgmms1!VidSchiRun_PriorityTable+0x24
8d167d50 8301dfdf dxgmms1!VidSchiWorkerThread+0x7f
8d167d90 82ec4699 nt!PspSystemThreadStartup+0x9e
00000000 00000000 nt!KiThreadStartup+0x19
1: kd> lmvm atikmpag
start end module name
92235000 92281000 atikmpag (deferred)
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Tue Apr 30 04:47:51 2013 (517F30D7)
CheckSum: 000546A3
ImageSize: 0004C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
My suggestions:
Run MemTest86+ to test the memory, update the network drivers and update AMD drivers.
Please follow instructions below.
Please update your Realtek ethernet driver
Driver Reference Table - Rt86win7.sys
Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Please ONLY install the drivers, via custom/advanced options.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums
Note
MemTest86+ needs to be run for
at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for
zero errors here. Even a single error will indicate RAM failure.
Quote