BSOD after installing driver for EnGenius WiFi receiver

paulking · 19 May 2013

While the WiFi might be a red herring, the moment I observed a BSOD was from Windows Update, which ran as the computer was shutting down.

WHen I checked C:\Windows\Minidump, I actually found two dump files, one from yesterday, and another from over a month ago. The one from yesterday was curious, since the timestamp reads 11:23 PM, and I didn't reboot until after midnight.

There should have been a third one from the day before "BAD_POOL_DATA" (this occurred on reboot immediately after installing the WiFi driver), but I didn't see it there. When the machine rebooted last night, according to Windows Update, the three updates that were in the process of installing were "Successful".

I guess it would be fair to mention the laptop: it is an HP TouchSmart TM2 1070ca running W7 HE (factory image).

Paul

Arc · 19 May 2013

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

paulking · 20 May 2013

Here is the dump file: Attachment 268868

Arc · 21 May 2013

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff8a001d474f0, fffff8a001d474f0, dffff8a001d474f0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )

Followup: Pool_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a001d474f0, the pool entry being checked.
Arg3: fffff8a001d474f0, the read back flink freelist value (should be the same as 2).
Arg4: dffff8a001d474f0, the read back blink freelist value (should be the same as 2).

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.