BSOD Please help me to read my dump files

[Jonathan_King]

First, disable your current adapter. That will tell us if you need a new one or not.

 

[vietnam]

First, disable your current adapter. That will tell us if you need a new one or not.

in this case, how can i connect to internet ? i.e. my work require internet connection always. Or we try to disable for some days ?

 

[Jonathan_King]

Do you have a wired (Ethernet) connection you can use?

 

[ttran]

@JK: I think the b44....sys is the Ethernet connection

 

[Jonathan_King]

Thanks ttran, I wasn't thinking.

Vietnam: I see you have a Dell wireless card installed. Are you using Wireless or Wired at work?

Could you use the wireless network if possible? Then disable the Broadcom device.

 

[vietnam]

@Jonathan : at my office, i can use Wireless to connect internet. At home one choice is cable.
Yesterday, I decide to use DriverScanner to scan and update my drivers.
It's said that i must update Dell Wireless 1390 WLAN MiniCard, i've updated it.
After that, i shutdown my laptop and go to my bed. This morning, start my laptop and MY GOD get a new BSOD.
Windows say me to repaire, and restore...i did it. Maybe this BSOD caused from the new driver on wireless ?

Quang Anh

 

[vietnam]

I used another tool called DriverAgent to scan and here's my result. Just view my driver with older date, can't download the new ones to update.
As i sait before, with DriverScanner, it's sait that one driver to update.
Each tool with different result, can't understand.

Quang Anh

 

[ttran]

I also believe that this is probably driver issue. Unfortunately, the wireless card driver wasn't blamed in the DMP file, so it's hard to conclude that it is the cause.

At this point, I would like you to enable driver verifier, so that we can identify what drivers are working improperly in your system
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature)

BUGCHECK SUMMARY:

BugCheck 1E, {ffffffffc0000005, 102e58c7c, 8, 102e58c7c}

Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )

Followup: MachineOwner
---------
PROCESS_NAME:  System

Regard,

Tuan

 

[vietnam]

Hi Tuan,

As your suggestion some days ago, i enabled driver verifier completely.
So what can i do in the next ? wait for a next BSOD ?

Quang Anh

 

[ttran]

Hi QuangAnh,

Yes, please wait for next BSODs, hopefully Driver Verifier will detect something
When did you enable it? Did you just enable it after my previous post or long ago? If you've enable it long long ago, I should suggest you to turn it off first. If not, keep it on and hopefully we can see something

To double check if DV is working, Open a command prompt and enter verifier /query.

 

[vietnam]

Hi QuangAnh,

Yes, please wait for next BSODs, hopefully Driver Verifier will detect something
When did you enable it? Did you just enable it after my previous post or long ago? If you've enable it long long ago, I should suggest you to turn it off first. If not, keep it on and hopefully we can see something

To double check if DV is working, Open a command prompt and enter verifier /query.

After your post, i did it.
I has double cheked as your suggestion, too.
OK we wait for a next BSOD (Comme on, please ).

 

[vietnam]

drivers updated

No BSOD for 3 days, updated all my drivers by using DriverMax version 5.5, here's the result of my drivers's status :

http://www.drivermax.com/driver/drivers.php?computer_id=27915P0BYIH7JPH6Y517NGXR4N2W34&iduser=1737383

* With memory : bought a new ddr 2, tested with Memtest86+ at least 5 passed without error (red line).

* With drivers : updated all my drivers with their lastest version.

I wish don't get any BSOD.

 

[Jonathan_King]

You can enable driver verifier if you want to test it out faster: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[vietnam]

Finally, the unexpected thing was happened, this morning i locked my Windows to get out for my meeting about 3 hours. When i comeback i get this new BSOD.
Please help me to find out the cause.

 

[cluberti]

This is pool corruption (a driver called ExFreePoolWithTag on an invalid address, and it failed - thus the bugcheck). You will need to enable special pool and pool tracking with verifier:

start > run > verifier > create custom settings > select individual settings from a full list > check "Special Pool" and "Pool Tracking" > Select Drivers from a list > click on "Provider" at the top to sort the list by manufacturer, then select all drivers that are not provided by Microsoft Corporation, and are not amdxata.sys and secdrv.sys > Finish.

Reboot, and let's see if you get another BSOD.

 

[vietnam]

Thanks cluberti, i did it, hope it works.

 

[cluberti]

You still have secdrv.sys checked - if you don't go back and uncheck that, your system may become very unstable. Just FYI.

 

[vietnam]

OK, i removed secdrv.sys checked.
Another thing, i got this error when i goto cmd>run>sfc /scannow. It's ok or not ? anyone helps me to read CBS.zip ?
For repairing this error, as suggestion of Tuan, i try to repair this error by using repair Windows but it doesn't work, i wonder can it be the cause of my BSOD ?

 

[cluberti]

It is complaining about WMP files and some Chinese Traditional language files. Look in the cbs log file for this line:
"2010-08-26 11:39:32, Info CSI 000002f9 [SR] Beginning Verify and Repair transaction"

When you find that, you'll see the repair failures. I do not think they're related to your crashes, however.

 

[vietnam]

OH my god, has received a new BSOD...
What's the problem for my laptop ?

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: vwififlt.sys

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x000000c1 (0xfffff980115b8f30, 0x0000000000000000, 0x00000000000000d0, 
0x0000000000000022)

*** vwififlt.sys - Address 0xfffff88002d35110 base at 0xfffff88002d28000 DateStamp 
0x4a5bcc3a