HP dv9235nr - blue screen - video drivers?

I am not very technical and could use some help with two issues. I got a new laptop back in Febuary – HP Pavilion dv9235nr (2GB Memory, 160 GB Hard Drive with over 80% free, Intel Centrino Duo Processor). Didn’t have any issues at first other some of my older software wasn’t compatible with Vista and had to replace.

About three weeks ago I got the dreaded “Blue Screen”. Restarted and everything seemed OK for a while. About three days ago it happened again, and it’s getting more frequent. HP has been helpful in the past, but when I contacted them this time I wasn’t impressed. The rep wants me to re-load everything back to factory settings. I don’t think that is the answer. I also don’t think it is disk space. I think it is the driver identified in the message.

Here’s the message:

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

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 be sure you have adequate disk space. If a driver is identified in the Stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need 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: 0X0000008E (0XC0000005,0X807E4EIC, 0X9C9CF5A4, 0X00000000)

***SSIDRV.SYS – Address 807E4EIC base at 807D9000, DateStamp45b98a10

I have found only one remaining update for my computer. And, it is for a video driver. But here’s the thing - I’m stuck on dial-up because of where I live. Estimated install time download time is over 4 hours! I’ll do it if I need to, but any other opinions out there? Plus, I’ve gotten this message several times so I don’t know if I can stay connected for that long!!

Here’s my second issue: This thing has been slow since I got it. I know dial-up is really slow, but this is so much slower than my old laptop. HP Health Check gives it a grade of “Poor” because of Memory Performance. Does this thing not have enough memory to surf the Internet? Is there anything I can do to tweak it?

Thanks in advance,
Carol

 

for error try a google. it gives you tons of info on error.
If you are annoyed.........
replace it...
sry for not good answers...

 

A quick search of the web lead me to real customer support forums...
http://real.lithium.com/real/board/message?board.id=realplayer&message.id=14483#M14483
From reading the reply the BSOD seems to be related to either realplayer or the Webroot spy sweeper or both. Do you use any/either of these two softwares. If yes, then uninstall them and see if ths BSOD reoccurs.

 

Miner,
Thanks for the info. I had seen info about Realplayer and Spysweeper conflicting, but since I don't use Realplayer didn't think much about it. I had been thinking about uninstalling Spysweeper but hadn't done it yet. I got the BSOD only once yesterday and I was using the PC all day. Then today, I BSOD many times. So, I uninstalled Spysweeper. Hopefully, that is the problem.

Thanks again,
Carol

 

Miner,

I too got the same behavior after installing Real Player on my new laptop (HP dv9208nr). After uninstalling Real Player it stopped for a few weeks then suddenly started happening again yesterday everytime I tried to connect to the Internet. After seeing your message I decided to uninstall Spysweeper and so far it's behaving. Thanks for the info.

-George

 

You're running Spysweeper on your machine, aren't you?

I install the program on hundreds of computers at work. Every now and then we see machines coming back with that problem. That file is part of a keylogger detection feature in Spysweeper. I dunno if it's a problem with Vista, Spysweeper, or some other program interfering with it, but there is a workaround. What I do is I simply disable the errant file. Spysweeper still works fine, minus the keylogger detection feature.

Boot into safe mode, launch explorer, then go to C:\WINDOWS\SYSTEM32\DRIVERS and rename SSIDRV.SYS to SSIDRV.SYS.BAK. The system will no longer load the file, plus if you ever need to reverse it you can do so just by naming the file back to its correct name. I do this for my customers whenever they have a problem with Spysweeper and fixes the problem just fine.