New
#1
BSOD with ntoskrnl.exe
Hey, my computer keeps BSOD most of the time. It almost always BSOD when I am playing BF3, but most other games like d3 almost never crash. It does BSOD sometimes when watching videos or just using basic programs like firefox.
The BSOD I get are mostly IRQL_NOT_LESS_OR_EQUAL or UNEXPECTED_KERNEL_MODE_TRAP.
Once it does BSOD, sometimes it will keep BSOD on bootup at the windows 7 startup page, which I have to turn off my computer for about 10 mins, and then it will bootup alright. I though that it was overheating, but all of my temps are always good, and are never in the red. I even took out my CPU and took off it's old thermal paste and apply a new coat hoping that may help.
I have also run memtest and it run a few passes with no problems. I even put my ram sticks in another computer for a few days and it never once crash, so I don't think it's my ram.
I have also try formatting my computer and reinstall Windows with no luck.
I have run WhoCrashed and it says that it is my nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 301.42 , NVIDIA Corporation), which I just updated a few days ago.
This is what WhoCrashed says:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 7/1/2012 8:34:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-22448-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x109 (0xA3A039D89C1564FE, 0xB3B7465EEE9236F4, 0xFFFFF80002B9D410, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 7/1/2012 8:34:56 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: 0x109 (0xA3A039D89C1564FE, 0xB3B7465EEE9236F4, 0xFFFFF80002B9D410, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 7/1/2012 1:30:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-22604-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x109 (0xA3A039D8997B953A, 0xB3B7465EEBF86730, 0xFFFFF80002B9DC90, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 Sat 6/30/2012 6:00:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-22105-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x189E6C)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF8800FFBDE6C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 UNEXPECTED_KERNEL_MODE_TRAP
On Thu 6/28/2012 1:39:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062712-27955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFF0A00C1E3270, 0x0, 0xFFFFF880041B6586, 0x7)
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 Thu 6/21/2012 4:57:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-24960-01.dmp
This was probably caused by the following module: usbstor.sys (USBSTOR+0x3140)
Bugcheck code: 0xD1 (0xFFFFFFFF88E551E3, 0x2, 0x1, 0xFFFFF88006B2F140)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbstor.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Mass Storage Class 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 which cannot be identified at this time.
On Thu 6/21/2012 12:25:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062012-40669-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800028978E5, 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 Wed 6/20/2012 1:54:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061912-29156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0xA (0xFFFFF80082A81260, 0x2, 0x1, 0xFFFFF8000288752C)
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 6/18/2012 11:20:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061812-26052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x109 (0xA3A039D898AF574E, 0xB3B7465EEB2C298C, 0xFFFFF80002A0D6F0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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.
Conclusion
9 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 301.42 , NVIDIA Corporation)
My Computer specs are:
Windows 7 64-bit
Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GH
Nvidia GTX 275
8GB DDR2 Ram