New
#1
BSOD from multiple drivers
I have been getting these crashes over and over for a very long time, but it only started getting unbearable since i started playing Battlefield 3. The crashes inexplicably increases the occurrence of crashes from randomly to about 75% of the time upon running the game for a short period. The latest crash appears to be caused by my graphics driver which i updated today so if you say all my problems are caused by that one driver it is unlikely (though i don't entirely discount it, simply doubt). Finally while I was getting the crash dumps together for this thread and a random error occurred which i have NEVER seen before, i copied and pasted the information i saw in a txt file in hopes that it may help. I should also note that i have done a bunch of research on resolving the issue myself, but everything that they are asking others to do is just enough over my head that applying it to my issue flabbergasts me. I also don't have my install disc to windows 7 ultimate x64, so if you conclude a system repair is required i don't think i will be able to do it (just letting any of you know). Finally i will post some information on my latest crashes from whocrashed in the possibility it will help along with my dmp files attached (and the aforementioned txt file).
Thank you for any and all help in advance
On Thu 1/17/2013 5:55:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-23571-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x205D21)
Bugcheck code: 0xA (0xFFFFEE7FFFFFFFD8, 0x2, 0x1, 0xFFFFF800032EFFD4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 310.90
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 310.90
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 310.90 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL
On Thu 1/17/2013 5:55:14 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 (0xFFFFEE7FFFFFFFD8, 0x2, 0x1, 0xFFFFF800032EFFD4)
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 which cannot be identified at this time.
On Wed 1/16/2013 7:59:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-26332-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032C5810, 0xFFFFF8800C323970, 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 1/15/2013 4:00:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011513-21684-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1 (0x76E9FA1A, 0x0, 0xFFFF0000, 0xFFFFF8800783CCA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 1/15/2013 3:13:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-25256-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x4A (0x76D2FC0A, 0x2, 0x0, 0xFFFFF880096A2CA0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 1/15/2013 2:43:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-29281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x90FD4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003295FD4, 0xFFFFF880009A9968, 0xFFFFF880009A91D0)
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 1/15/2013 2:32:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-22869-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x34 (0x50830, 0xFFFFF8800319A548, 0xFFFFF88003199DB0, 0xFFFFF800032EDFD4)
Error: CACHE_MANAGER
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 1/14/2013 10:47:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-23431-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x34 (0x50830, 0xFFFFF880031856C8, 0xFFFFF88003184F30, 0xFFFFF800032BF7A5)
Error: CACHE_MANAGER
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 1/14/2013 5:40:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-19796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF800033400BF)
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 Mon 1/14/2013 5:31:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-19843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032CF7A5, 0x0, 0xFFFFFFFFFFFFFFFF)
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 which cannot be identified at this time.
On Sun 1/13/2013 12:39:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-25755-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x401, 0xFFFFF6FB831FDE50, 0x80000000134FB863, 0xFFFFF6BB831FDE50)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.