Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 10 Crashing - please help


  • Please log in to reply
3 replies to this topic

#1 Jdb23

Jdb23

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 26 November 2016 - 08:40 AM

For about few weeks I am facing constant crashing to BSOD. I noticed that Windows crash when I start Google Chrome. 

Latest program I installed is new NetLimiter, but I am not sure if it could be a problem as I already had NetLimiter on PC installed before updated to latest version.

I noticed hight CPU usage 100% even I do not think it is using 100% or not showing on task manager.

I tried to do Systerm Restore, but I am getting some error completing this.

Attached are photos of BlueScreenView too

 

This is report I got from WhoCrashed:

 

System Information (local)

Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LX
CPU: GenuineIntel Intel® Core™ i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 25711878144 bytes total


 

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 11/26/2016 2:22:08 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-18593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFF838EA7AFD388)
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 Sat 11/26/2016 2:09:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-9453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x1, 0xA9910000, 0xFFFFDE88B2C460A8)
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 Sat 11/26/2016 11:29:05 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-18281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFFD20A153E74E8)
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 Sat 11/26/2016 2:50:47 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-23390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFFAF895E31C928)
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 Sat 11/26/2016 2:16:10 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-32796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFF8601476CB818)
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.



 

Conclusion

31 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 

 

 

 

Attached Files

  • Attached File  2.png   9.35KB   0 downloads
  • Attached File  1k.png   8.63KB   0 downloads


BC AdBot (Login to Remove)

 


#2 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 26 November 2016 - 09:14 AM

For about few weeks I am facing constant crashing to BSOD. I noticed that Windows crash when I start Google Chrome. 

Latest program I installed is new NetLimiter, but I am not sure if it could be a problem as I already had NetLimiter on PC installed before updated to latest version.

I noticed hight CPU usage 100% even I do not think it is using 100% or not showing on task manager.

I tried to do Systerm Restore, but I am getting some error completing this.

Attached are photos of BlueScreenView too

 

This is report I got from WhoCrashed:

 

System Information (local)

Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., P8Z77-V LX
CPU: GenuineIntel Intel® Core™ i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 25711878144 bytes total


 

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 11/26/2016 2:22:08 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-18593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFF838EA7AFD388)
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 Sat 11/26/2016 2:09:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-9453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x1, 0xA9910000, 0xFFFFDE88B2C460A8)
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 Sat 11/26/2016 11:29:05 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-18281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFFD20A153E74E8)
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 Sat 11/26/2016 2:50:47 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-23390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFFAF895E31C928)
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 Sat 11/26/2016 2:16:10 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\112616-32796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFF8601476CB818)
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.



 

Conclusion

31 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 

 

 

 

Hi,

You might want to try to uninstall NetLimiter first and then run a driver verifier test.

Thanks.



#3 Jdb23

Jdb23
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 26 November 2016 - 11:30 AM

I tried to run Driver verifier, but after restart windows is just loading and loading but login page is not showing....

 

How to get back to login page now?



#4 Jdb23

Jdb23
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 26 November 2016 - 01:23 PM

OK, fixed.

NetLimiter removed. No BSOD for now....






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users