Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › ntoskrnl.exe BSOD while playing games ...pls help I'm desperate
New Posts  All Forums:Forum Nav:

ntoskrnl.exe BSOD while playing games ...pls help I'm desperate

post #1 of 4
Thread Starter 
All above...here is my config DxDiag.txt 22k .txt file ...BSOD started 2-3 weeks after I bought new GPU (that one in DxDiag ) first with atimdag.sys BSOD and now this frown.gif ...pls help...oh yeah and this

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 25.2.2013. 17:42:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022513-20187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF80002CC3A50, 0xFFFFF88007E20110, 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 Mon 25.2.2013. 16:50:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022513-29750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x5560049, 0x2, 0x0, 0xFFFFF80002C8F4C2)
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 that cannot be identified at this time.



On Mon 25.2.2013. 16:07:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022513-15500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8EE33, 0xFFFFF880075DB0A0, 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 Mon 25.2.2013. 15:08:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022513-19734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFFF6800002A108, 0x2, 0x0, 0xFFFFF80002C9965F)
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 that cannot be identified at this time.



On Fri 22.2.2013. 18:23:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022213-15593-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF880012C6C7E)
Bugcheck code: 0x50 (0xFFFFFB800FA94C18, 0x0, 0xFFFFF880012C6C7E, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 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 Wed 20.2.2013. 20:25:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022013-15500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFFA800756FD60, 0x0, 0xFFFFF80002CDA25B, 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 Tue 19.2.2013. 17:00:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021913-26187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x8661D, 0x2, 0x0, 0xFFFFF80002C8B65F)
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 that cannot be identified at this time.



On Tue 19.2.2013. 15:11:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021913-15140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002ADFFD5)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 17.2.2013. 11:52:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021713-21062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFFA8007D40340, 0x1, 0xFFFFF80002ABD226, 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 13.2.2013. 20:17:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021313-47921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x50 (0xFFFFF88071FD8853, 0x0, 0xFFFFFA80049B0569, 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 that cannot be identified at this time.



On Sun 10.2.2013. 16:22:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021013-41671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A96711, 0xFFFFF880073507F0, 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 Sun 10.2.2013. 15:09:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021013-47437-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960001079E2)
Bugcheck code: 0x50 (0xFFFFFA80066D0A30, 0x1, 0xFFFFF960001079E2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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 Sun 10.2.2013. 14:33:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021013-37250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFFA8001738306, 0x2, 0x3C00)
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 that cannot be identified at this time.



On Mon 4.2.2013. 19:19:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-14015-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960002C856D)
Bugcheck code: 0x50 (0xFFFFFB00C0167034, 0x0, 0xFFFFF960002C856D, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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.
post #2 of 4
Have you recently installed any new programmes ?? quick search on google reveals that this happens when there are conflicting drivers on the system. Maybe two programs running simultaneously to achieve same results (AV). Its suggested that you install driver verifier to identify issues that may cause errors like these.
Also, have you tried system restore
post #3 of 4
Thread Starter 
I've only updated drivers and tried driver sweeper or smth like that,haven't tried restore but it started long ago,I've cleaned my hardware and checked,did Memtest and no errors,checked disk everything ok....how can i start verifier? And I didn't install any new programs
post #4 of 4
Thread Starter 
I used verifier on win7 64 bit on all drivers and second time (I have deleted past settings first and then started 2nd time) only on ntoskrnl. and no bsod or anything :// btw this is crashdump from my latest crash debuglog.txt 21k .txt file
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › ntoskrnl.exe BSOD while playing games ...pls help I'm desperate