New
#1
Bsod bad_pool_header
My computer could not boot without safe mode. Its failing every time I am trying to boot in normal mode.
Log traces grabbed from SF_Diagnostic_Tool is attached?
Thanks in advance
My computer could not boot without safe mode. Its failing every time I am trying to boot in normal mode.
Log traces grabbed from SF_Diagnostic_Tool is attached?
Thanks in advance
When following microsoft knowledge base How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista to fix BAD_POOL_HEADER.
Now I am getting PAGE_FAULT_IN_NON_PAGED_AREA BSOD.
Log generated from SF_Diagnostic_Tool is attached.
Before appearing BAD_POOL_HEADER BSOD, my windows 7 update could not be completed showing following message
"Failure configuring Windows updates. Reverting changes. Do not turn off your computer" error when you try to install Windows updates
When trying to boot multiple times, luckily able to boot in normal mode. After successful boot in normal mode, enabled required services which was disabled when setting up clean boot.
I also updated wifi, graphics driver as suggested by yowanvista. It's been week and no more blue screen of death
Thank you youwanvista for your help.
Last edited by baha; 15 Aug 2013 at 06:32. Reason: Fixed messages
Dumps point to Intel Wifi driver (netw5s64.sys)
Update it using update utility: Intel® Driver Update Utility or from Sony. Install it in Safe Mode with Networking.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BugCheck D1, {fffff8800c5d2b80, 2, 0, fffff88005adee75} Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for NETw5s64.sys *** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys Probably caused by : NETw5s64.sys ( NETw5s64+30e75 ) DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff8800c5d2b80, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88005adee75, address which referenced memory
Now my system is running properly without any problem though SF diagnostic tool grabbed log file is attached to know if there is any error .