New
#1
Random BSOD, errors 0x0000018 and 0x000003b
I know this is a lot, but this thing keeps crashing on me randomly. please give it a read.
thank you guys.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 6/25/2012 8:03:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-32775-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FC8EB0, 0xFFFFF8800B0FA050, 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 Mon 6/25/2012 8:00:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-31434-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB7EB0, 0xFFFFF88007528CC0, 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 Mon 6/25/2012 5:26:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-32151-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F82EB0, 0xFFFFF8800A50AEA0, 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 Sun 6/24/2012 9:15:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-44101-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x18 (0xFFFFFA8003D2A2C0, 0xFFFFFA80059E4400, 0x1, 0x10000000000000)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 6/24/2012 9:15:04 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: 0x18 (0xFFFFFA8003D2A2C0, 0xFFFFFA80059E4400, 0x1, 0x10000000000000)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 6/24/2012 8:02:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-41465-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB1EB0, 0xFFFFF8800655CD30, 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 Sun 6/24/2012 5:16:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-44429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002C9C853)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 which cannot be identified at this time.
On Sun 6/24/2012 3:44:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062412-42697-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x19E4D4)
Bugcheck code: 0x116 (0xFFFFFA8006A08010, 0xFFFFF8800FFA34D4, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 301.42
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 301.42
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 301.42 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR
On Sun 6/24/2012 4:38:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062312-32869-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x242758)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88010080758, 0xFFFFF88003884360, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 301.42
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 301.42
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 301.42 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
On Sat 6/23/2012 11:13:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062312-38906-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xB26F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002A51565, 0xFFFFF88002FFC558, 0xFFFFF88002FFBDB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating Saystem
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 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.