New
#1
BSOD Bad Pool Caller 0xC2
BSOD Bad Pool Caller 0xC2
BSOD Bad Pool Caller 0xC2
Rule 4
No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.
One of the main reasons for this is that the act of pirating the software will inevitably change the working of the software and make investigation and repair impossible. Please install a legitimate copy of the software and if you are still experiencing the issue we will be please to assist - No further assistance will be provided until we are satisfied that the software is genuine
my software is ilegal
Look at the pic
Attachment 131905
You got PN
Hi i generate new logs
Code:0x0000009F: DRIVER_POWER_STATE_FAILURE (20.04.2017 17:23:23) [Windows 10] CAUSED BY: ndis.sys [28.03.2017] * NDIS 6.20 Wrapper Driver (Windows System File) PROCESS: System Usual causes: Device driver TO RESOLVE: 1. Check Drivers 2. Disable security software for testingCode:0x0000009F: DRIVER_POWER_STATE_FAILURE (17.04.2017 15:58:10) [Windows 10] CAUSED BY: memory_corruption wwussf64.sys [5.09.2011] * SSNDIS filter service * => http://support.dell.com/support/downloads/index.aspx?c=us&l=en&s=dhs PROCESS: svchost.exe Usual causes: Device driver
ndis.sys and wwussf64.sys is network related. Updating your network drivers would be the first step:
wwussf64.sys [5.09.2011] * SSNDIS filter service Mobile Broadband Driver * => Drivers Downloads | Dell US
Its also recommended to update your BIOS. Your is very old:
BIOS_VERSION: 68SCF Ver. F.08
BIOS_DATE: 08/26/2011
Link to BIOS Update: http://ftp.hp.com/pub/softpaq/sp77501-78000/sp77971.exe
Last edited by BSODHunter; 28 Apr 2017 at 03:35.
Word of caution, please do some research on how to update/flash your BIOS and don't go rushing in.
It is a delicate procedure that should be done correctly.
i will remove the eset and update the bios
and i will tacking if the bsod again
any news?