New
#61
First, disable your current adapter. That will tell us if you need a new one or not.
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.
@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
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
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
Driver Verifier - Enable and Disable
[quote]
BUGCHECK SUMMARY: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)
Regard,Code:BugCheck 1E, {ffffffffc0000005, 102e58c7c, 8, 102e58c7c} Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) Followup: MachineOwner --------- PROCESS_NAME: System
Tuan
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
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.