Sign in with
Sign up | Sign in
Your question

BSOD causing by ntoskrnl.exe

Last response: in Windows 7
Share
January 27, 2013 6:52:30 AM

Pls help me, i've got bsod 2 time in 5 minute, very annoying :( 
Here is the whocrashed analyzed data:

On Sun 27-Jan-13 07:55:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012713-15397-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFF80003024D58)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 27-Jan-13 07:46:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012713-15381-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FB5B05, 0xFFFFF8800B7A4750, 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.

More about : bsod causing ntoskrnl exe

January 27, 2013 7:05:34 AM

Using your windows disc you could try to repair your installation not re-install, there is a a chance that you might need new ram though. You should try this first www.youtube.com/watch?v=2c0onEJXU2E
m
0
l
January 27, 2013 11:34:16 PM

Thanks, i tried SeaTools for Windows and MemTest but no problem was found, i also repaired windows, run sfc scan, still no problem.
I will let you know if BSOD happen again :) 
m
0
l
Related resources
a b $ Windows 7
January 27, 2013 11:58:31 PM

Oddly enough I've been seeing a rash of these BSODs lately related to ntoskrnl.exe. Most of them had other underlying causes such as hardware but there have been a few that were actually triggered by an advanced form of malware or rougeware.

I would recommend running either MalwareBytes Anti-Malware or Super Anti-Spyware or even both to see if it kicks anything out.
m
0
l
January 28, 2013 3:23:36 AM

hedwar2011 said:
Oddly enough I've been seeing a rash of these BSODs lately related to ntoskrnl.exe. Most of them had other underlying causes such as hardware but there have been a few that were actually triggered by an advanced form of malware or rougeware.

I would recommend running either MalwareBytes Anti-Malware or Super Anti-Spyware or even both to see if it kicks anything out.

I already have Kaspersky Anti Virus 2013 and run a full scan but nothing were found
m
0
l
February 2, 2013 11:36:37 PM

Ok, after a week with no problem, my laptop get BSOD again, and still causing by ntoskrnl.exe :( 

System Information (local)
--------------------------------------------------------------------------------

computer name: GALLUS
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4096983040 total
VM: 2147352576, free: 1952079872




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 03-Feb-13 01:24:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-21044-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xB7277)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F11277, 0xFFFFF88003D0F7D8, 0xFFFFF88003D0F030)
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 that cannot be identified at this time.



On Sat 02-Feb-13 10:15:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-14352-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41284, 0x536D001, 0x8BB3, 0xFFFFF70001080000)
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 that cannot be identified at this time.
m
0
l
!