I started encountering a BSODs about 6 months ago, at first I ignorantly decided to ignore these messages and just deal with it. I didn't check into what the error codes I was getting at the time meant and have no idea if they are related to the more recent ones. They have been starting to pop up more and more often as the day goes by. There have been absolutely no hardware changes in the 2 years since I bought the computer new. The machine seems to running at a fine temperature consistently even when presented with a graphically intense workload. The error codes all seem to do with a misbehaving driver(s). I'm not incredibly tech savvy, but I'm trying my best to learn on the fly here. I'll list some specs followed by a WhoCrashed report. I tried to install Microsoft Visual Studio 11 to read the dump files, but it crashes whenever it gets to the .Net framework 4.5 beta. I can attach the actual .dmp files if it's more helpful though, just let me know. I tried the troubleshooting and I'm fairly certain it's not a hardware issue.
Windows 7 64 bit
CPU: AuthenticAMD AMD Phenom(tm) II X4 945 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589074432 total
VM: 2147352576, free: 1951039488
On Wed 4/11/2012 10:09:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041112-29437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF6FC5041B9C0, 0x0, 0xFFFFF800030F45F1, 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 which cannot be identified at this time.
On Wed 4/11/2012 10:09:11 PM 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: 0x50 (0xFFFFF6FC5041B9C0, 0x0, 0xFFFFF800030F45F1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 which cannot be identified at this time.
On Tue 4/10/2012 10:53:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041112-37767-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800BCA6478, 0xFFFFF8800BCA5CD0, 0xFFFFF80003365956)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.
On Tue 4/10/2012 8:18:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-32869-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003393728, 0xFFFFF88003392F80, 0xFFFFF880012A0043)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.
On Tue 4/10/2012 1:30:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-23041-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA8305D15A6B, 0x0, 0xFFFFF8000307089F, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 1:12:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-25833-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA830391D2A8, 0x0, 0xFFFFF800031C7717, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 5:31:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-35131-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDE10)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880033855C8, 0xFFFFF88003384E20, 0xFFFFF88001437E10)
Error: CACHE_MANAGER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 which cannot be identified at this time.
On Tue 4/10/2012 4:46:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-37409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000332D43F, 0xFFFFF8800C5EECC0, 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 which cannot be identified at this time.
On Tue 4/10/2012 4:38:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-23821-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF6C0003B8DF8, 0x0, 0xFFFFF800030CD64B, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 4:17:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-23275-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4C7B6E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003527B6E, 0xFFFFF880033A8768, 0xFFFFF880033A7FC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 which cannot be identified at this time.
On Tue 4/10/2012 1:40:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-25038-01.dmp
This was probably caused by the following module: symds64.sys (SYMDS64+0xD92C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880010F092C, 0xFFFFF880033C4368, 0xFFFFF880033C3BC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\N360x64\0502000.00D\SYMDS64.SYS
product: SymDS
company: Symantec Corporation
description: Symantec Data Store
Bug check description: This indicates that a system thread 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.
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: symds64.sys (Symantec Data Store, Symantec Corporation).
Google query: symds64.sys Symantec Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 4/10/2012 12:32:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-34101-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A384060, 0xFFFFFA800A384340, 0xFFFFF8000338F5F0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.
On Tue 4/10/2012 12:28:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-31886-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF9A00C4BA6A0, 0x0, 0xFFFFF88001125F10, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 12:05:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-33524-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF800C010AB90, 0x0, 0xFFFFF96000166BCE, 0x5)
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 which cannot be identified at this time.
On Mon 4/9/2012 11:42:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-33477-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x9AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000719AF2, 0xFFFFF8800AD6DCE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Windows 7 64 bit
CPU: AuthenticAMD AMD Phenom(tm) II X4 945 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8589074432 total
VM: 2147352576, free: 1951039488
On Wed 4/11/2012 10:09:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041112-29437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF6FC5041B9C0, 0x0, 0xFFFFF800030F45F1, 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 which cannot be identified at this time.
On Wed 4/11/2012 10:09:11 PM 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: 0x50 (0xFFFFF6FC5041B9C0, 0x0, 0xFFFFF800030F45F1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 which cannot be identified at this time.
On Tue 4/10/2012 10:53:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041112-37767-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800BCA6478, 0xFFFFF8800BCA5CD0, 0xFFFFF80003365956)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.
On Tue 4/10/2012 8:18:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-32869-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003393728, 0xFFFFF88003392F80, 0xFFFFF880012A0043)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.
On Tue 4/10/2012 1:30:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-23041-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA8305D15A6B, 0x0, 0xFFFFF8000307089F, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 1:12:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-25833-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFFA830391D2A8, 0x0, 0xFFFFF800031C7717, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 5:31:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-35131-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDE10)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880033855C8, 0xFFFFF88003384E20, 0xFFFFF88001437E10)
Error: CACHE_MANAGER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 which cannot be identified at this time.
On Tue 4/10/2012 4:46:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-37409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000332D43F, 0xFFFFF8800C5EECC0, 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 which cannot be identified at this time.
On Tue 4/10/2012 4:38:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-23821-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF6C0003B8DF8, 0x0, 0xFFFFF800030CD64B, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 4:17:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041012-23275-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4C7B6E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003527B6E, 0xFFFFF880033A8768, 0xFFFFF880033A7FC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 which cannot be identified at this time.
On Tue 4/10/2012 1:40:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-25038-01.dmp
This was probably caused by the following module: symds64.sys (SYMDS64+0xD92C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880010F092C, 0xFFFFF880033C4368, 0xFFFFF880033C3BC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\N360x64\0502000.00D\SYMDS64.SYS
product: SymDS
company: Symantec Corporation
description: Symantec Data Store
Bug check description: This indicates that a system thread 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.
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: symds64.sys (Symantec Data Store, Symantec Corporation).
Google query: symds64.sys Symantec Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 4/10/2012 12:32:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-34101-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A384060, 0xFFFFFA800A384340, 0xFFFFF8000338F5F0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 which cannot be identified at this time.
On Tue 4/10/2012 12:28:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-31886-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF9A00C4BA6A0, 0x0, 0xFFFFF88001125F10, 0x5)
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 which cannot be identified at this time.
On Tue 4/10/2012 12:05:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-33524-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x50 (0xFFFFF800C010AB90, 0x0, 0xFFFFF96000166BCE, 0x5)
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 which cannot be identified at this time.
On Mon 4/9/2012 11:42:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040912-33477-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x9AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000719AF2, 0xFFFFF8800AD6DCE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
