HP DV6599ea

[bashar666]

Windows 7 BSOD - HP DV6599ea

I own HP Pavilion DV6599ea which became with windows vista installed. I have downgraded to XP and worked on XP for more than a year without any problems. I have recently purchased win7 home premium and i have installed it since 3 months. However i have been getting BSOD from time to time (once every month) and they seem to be related to different problems. I have attached the dump files. Can anyone help me with identifying the source of the problems?

Many thanks

 

[bashar666]

Any news?

 

[Lordbob75]

Bashar, it seems to be a corrupt driver of some kind.

Try opening command prompt as Admin, and type this:

sfc /scannow

~Lordbob

 

[bashar666]

Thanks Lordbob75. I tried it but didn't find any problems. Any other suggestions? Could the problem be because of incompatible BIOS? Although I read on HP website that people upgraded similar HP models that are not compatible with win7 without having any problems.

 

[bashar666]

...

 

[usasma]

The dump files blame BcmBusCtr.sys - a component of your Beceem Mobile WiMAX USB adapter (could be a USB adapter/aircard from Sprint)
There are also issues noted with netw5v32.sys - Intel Wireless WiFi Link Adapter
And nsiproxy - a networking component of Windows

For now, please visit the provider of the Beceem device and download the latest Win7 version of the drivers for it.
Then uninstall the current version on your system and install the freshly downloaded one.

Also, please do the same with the Intel WiFi adapter at the Intel Download Center: http://downloadcenter.intel.com/Default.aspx

Also, please remove the SoftPerfect network software that you have installed and leave it off until we finish troubleshooting (it can interfere with the troubleshooting).

Also, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

000.fcl      Thu Oct 04 22:45:19 2007 - Cyberlink CD/DVD driver
Afc.sys      Wed Feb 23 01:58:55 2005 -  [B][URL="http://www.google.com/search?q=%22Arcsoft%28R%29%20ASPI%20Shell%22"]Arcsoft(R) ASPI Shell[/URL][/B] belongs to the software [B][URL="http://www.google.com/search?q=%22PPdus%20ASPI%20Shell%22"]PPdus ASPI Shell[/URL][/B] by [B][URL="http://www.google.com/search?q=%22Arcsoft,%20Inc%22"]Arcsoft, Inc[/URL][/B]. (CD/DVD program)
rimmptsk.sys Wed Nov 16 21:28:31 2005 - Ricoh memory card driver
rimsptsk.sys Thu Dec 22 03:02:21 2005 - Ricoh memory card driver
rixdptsk.sys Tue Nov 14 20:35:19 2006 - Ricoh memory card driver
smserial.sys Fri Sep 26 04:23:38 2008 -  Motorola SM56 voice modem driver
spfdrv.sys   Tue Apr 29 05:21:47 2008 -  SPFDRV.SYS is related to NDIS packet redirector driver.
Manufacturer: SoftPerfect Research[url=http://www.softperfect.com/]Software for Enterprises, Intranets and the Internet[/url]

Then, if the BSOD's continue, please post back.

Here's a summary of the BSOD's:

BugCheck 1000008E, {c0000005, 82af4cea, 99ff9a5c, 0}
Probably caused by : nsiproxy.sys ( nsiproxy!NsippDispatch+92 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {c0000005, a00ef2f9, 8b3236b8, 8b323290}
Probably caused by : BcmBusCtr.sys ( BcmBusCtr+52f9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {c0000005, 955572f9, 8b31f6b8, 8b31f290}
Probably caused by : BcmBusCtr.sys ( BcmBusCtr+52f9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {c0000005, 9615c2f9, 8b3276b8, 8b327290}
Probably caused by : BcmBusCtr.sys ( BcmBusCtr+52f9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {c0000005, 9c5112f9, 8b32b6b8, 8b32b290}
Probably caused by : BcmBusCtr.sys ( BcmBusCtr+52f9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {c0000005, 963662f9, 8b31f6b8, 8b31f290}
Probably caused by : BcmBusCtr.sys ( BcmBusCtr+52f9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {64, 2, 0, 8ea6cd54}
Probably caused by : netw5v32.sys ( netw5v32+6bd54 )

 

[bashar666]

Hi Usama,

thanks for your response. I understand that beceem driver is the problem. I uninstalled it and i am not using it anymore. But the first and last dump files are the ones where i would like to find the problem cause. The last one i guess it is related to the Wifi driver so i will update it. But can you find out what the cause of the first BSOD? Could it be something related to the BIOS since the laptop is not buit to be compatible with Win7?

Many thanks

 

[usasma]

There's no telling exactly about the first dump file. It cites a Windows file, which usually means that something else caused the Windows file to crash. But, there's no evidence of what it was. We presume that the Beceem card was the problem because of the number of other errors that blamed it.

The WiFi driver may/may not have been at fault (for the same reason as the Windows file), but we can't be sure.

How we track these is by seeing what the most common error is (in this case the Beceem one). Then we fix that and wait for another BSOD. If we don't get a BSOD again - then it's fixed. If we do get one, then we troubleshoot that one. We continue this process until you're BSOD free (or you get fed up and reinstall the operating system