I have a 2-yr.-old home build that has worked fine until recently when I started getting random bsod's. It started when I bumped up the ram from 4g to 8g, using identical sticks. But I have eliminated all the possible memory issues as problems. I have set all timings and voltages per the recommendations of the manufacturer. Memtest86+ shows no errors after 9 passes. Tried resetting and moving. At mfr suggestion I also adjusted the cpu and northbridge video voltages (motherboard has built-in video, which what I use). I was then stable for a week, and suddenly have had 3 more crashes. Sysinfo and Whocrashed reports for these crashes:
Processor AMD Phenom(tm) II X4 B45 Processor
Memory (RAM) 8.00 GB
Graphics ATI Radeon HD 4200
Primary hard disk 32GB Free (98GB Total)
Windows 7 Home Premium
System
Manufacturer Gigabyte Technology Co., Ltd.
Model GA-MA785GM-US2H
Total amount of system memory 8.00 GB RAM
System type 64-bit operating system
Number of processor cores 4
On Sat 1/26/2013 3:53:42 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisAllocateTimerObject+0x2F6)
Bugcheck code: 0xD1 (0x41, 0x2, 0x0, 0xFFFFF880014D9226)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 1/25/2013 2:24:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-47658-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800039AAB12, 0xFFFFF88003911030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 1/25/2013 5:39:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-22791-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Processor AMD Phenom(tm) II X4 B45 Processor
Memory (RAM) 8.00 GB
Graphics ATI Radeon HD 4200
Primary hard disk 32GB Free (98GB Total)
Windows 7 Home Premium
System
Manufacturer Gigabyte Technology Co., Ltd.
Model GA-MA785GM-US2H
Total amount of system memory 8.00 GB RAM
System type 64-bit operating system
Number of processor cores 4
On Sat 1/26/2013 3:53:42 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisAllocateTimerObject+0x2F6)
Bugcheck code: 0xD1 (0x41, 0x2, 0x0, 0xFFFFF880014D9226)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 1/25/2013 2:24:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-47658-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800039AAB12, 0xFFFFF88003911030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 1/25/2013 5:39:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-22791-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.