How to Fix Windows Update Errors?: BSOD from ntoskrnl.exe and other issues

BSOD from ntoskrnl.exe and other issues

This is a new build, new CPU/mobo, etc., have a brand new video card.
Three hard drives are in my system (1 SSD and 2 HDD).
I'm not really sure where to start looking at what the issue may be.
I thought it was the video card, so I replaced it, but I'm
still getting similar issues.

The BSOD is sporadic, and the issue doesn't seem to be the same every time, but ntoskrnl.exe has come up a couple of times.
What are the possible issues I could be having?

Here is what WhoCrashed has said about the most recent crashes:

On Fri 2/8/2013 4:59:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-8751-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x33F79)

Bugcheck code: 0xA (0xFFFFF88042F698C0, 0x2, 0x1, 0xFFFFF80002AD574F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error.
It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).

Google query: Advanced Micro Devices, Inc.
IRQL_NOT_LESS_OR_EQUAL

On Fri 2/8/2013 4:59:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0xA (0xFFFFF88042F698C0, 0x2, 0x1, 0xFFFFF80002AD574F)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Thu 2/7/2013 8:41:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020713-8564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)

Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x8, 0xFFFFFFFFFFFFFFFF, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Tue 2/5/2013 11:53:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020513-9063-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)

Bugcheck code: 0x50 (0xFFFFF80006BC3FF6, 0x8, 0xFFFFF80006BC3FF6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Wed 1/30/2013 3:26:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012913-9110-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2333)

Bugcheck code: 0xD1 (0x301A460, 0xD, 0x1, 0x6FD35E33)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Mon 1/28/2013 10:35:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012813-8314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)

Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002AE3305, 0xFFFFF8800DEEA090, 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 Sat 1/26/2013 4:26:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-9500-01.dmp
This was probably caused by the following module: hal.dll (hal+0x5472)

Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 5:35:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012413-11622-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)

Bugcheck code: 0x3B (0xC0000096, 0xFFFFF80002A91846, 0xFFFFF8800CCB9600, 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 Wed 1/23/2013 5:06:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012213-9328-01.dmp
This was probably caused by the following module: pci.sys (pci+0x25F1)

Bugcheck code: 0xA (0x4722, 0x2, 0x1, 0xFFFFF80002ACEF85)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\pci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Plug and Play PCI Enumerator
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

Keys to the Problem BSOD from ntoskrnl.exe and other issues

Download SmartPCFixer for Free Now

Open Action Center by clicking the Start button Picture of the Start button, clicking Control Panel, and then, under System and Security, clicking Review your computer's status.

Update and run your antivirus software. Windows doesn't come with antivirus software, but Action Center can often monitor the antivirus software that you or your computer manufacturer have installed.