Windows 7: Problem Event Name: BlueScreen

Elle · 10 Jul 2011

Help please. I keep getting the bluescreen. It used to happen after every few days now its happening everyday. I've attached my dump, hopefully I did it right.

I'm currently running on Windows 7 Home Premium 64bit. I purchased from retailer over a year ago. Everything is in its original state from when I purchased it. I didn't change anything. I'm not very savvy with stuff like this so direction and any help will be appreciated.

FredeGail · 10 Jul 2011

Hello Elle & Welcome to SevenForums!

Easy.

Looks like you have a bckd.sys which is K9 parental web filter. Could you uninstall this? It appears in most of your completed .dmp files.

The web filter is taking from http://www1.k9webprotection.com/, does this look familiar?

BSOD Summary

Code:

Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : bckd.sys ( bckd+d50e )
---------------------------------------------------
Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : bckd.sys ( bckd+d50e )
---------------------------------------------------
Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : bckd.sys ( bckd+d50e )
---------------------------------------------------
Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : bckd.sys ( bckd+d50e )
---------------------------------------------------
Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : bckd.sys ( bckd+d50e )
---------------------------------------------------
Unable to load image \SystemRoot\system32\drivers\bckd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bckd.sys
*** ERROR: Module load completed but symbols could not be loaded for bckd.sys
Probably caused by : bckd.sys ( bckd+d50e )

And so on..

After the uninstallation, go to the path (\SystemRoot\system32\drivers\bckd.sys) where the driver was supposed to be, and make sure it's gone.

Best Regards,
FredeGail

Elle · 11 Jul 2011

Thank you FredeGail! I've uninstalled K9 with no problem and rebooted. I went to that folder and I still see bckd.sys is still there. Is it possible for it to be a common file with another program? Why is it still there if I've uninstalled K9?

FredeGail · 11 Jul 2011

Quote: Originally Posted by Elle

Thank you FredeGail! I've uninstalled K9 with no problem and rebooted. I went to that folder and I still see bckd.sys is still there. Is it possible for it to be a common file with another program? Why is it still there if I've uninstalled K9?

Did you have any sort of crash after the uninstallation?
I think, if you really want it to be gone, you could download Malwarebytes and expect it to find it as malware. My option two, I don't know if it's possible, make a backup, and then delete it right away in safe-mode. But if there's no crashes for now, I'd call it fixed

Looks like this file is some leftover file, not being in-use, right?

Best Regards,
FredeGail

Elle · 12 Jul 2011

It's been 2 days since I've had my last bluescreen and 1 day since I've uninstalled K9. I think uninstalling K9 did the trick and the file is some leftover like you said. Now that I'm not getting the bluescreen, I'm good! So it's all fixed thanks to you.

Thanks a motherload, lol!

FredeGail · 13 Jul 2011

Quote: Originally Posted by Elle

It's been 2 days since I've had my last bluescreen and 1 day since I've uninstalled K9. I think uninstalling K9 did the trick and the file is some leftover like you said. Now that I'm not getting the bluescreen, I'm good! So it's all fixed thanks to you.

Thanks a motherload, lol!

That's great news!

If you have any trouble, just return to this forum!

Best Regards,
FredeGail

Elle · 21 Jul 2012

Previous BSOD is resolved, this is a new BSOD that I'm now getting. I've attached a zip file containing all the information listed in the "Posting Instructions" post. I'm using Windows 7 Home Premium 64bit, it is still in it's original state from when I first purchased my lap top a little over 2 years ago.

FredeGail · 29 Jul 2012

Hello again Elle! Nice to see you around again. I've hopefully got skilled since last visit.

BSOD Analyse

Your BIOS is from 2009 which could be problematic.

Here are some of my suggestions:

Search your hardware parts on the Windows 7 Compatibility Center, and ensure that Microsoft has approved the product to be 7 ready.
- (For an automatic check, you can use the Upgrade Advisor)

Windows 7 Upgrade Advisor - Download - Microsoft Windows

Code:

BIOS Version/Date	Hewlett-Packard F.04, 10/26/2009

Best Regards,
Frederik.

Elle · 30 Jul 2012

I've had only 1 BSOD maybe about 4 days after I last posted here. I haven't had one since then so I'm not sure if it somehow fixed itself or what. However I did experience lots of freezing, random restart/reboot of windows, and occasional beeps. Do you have any ideas what may be the cause of all those problems?

FredeGail · 30 Jul 2012

Quote: Originally Posted by Elle

I've had only 1 BSOD maybe about 4 days after I last posted here. I haven't had one since then so I'm not sure if it somehow fixed itself or what. However I did experience lots of freezing, random restart/reboot of windows, and occasional beeps. Do you have any ideas what may be the cause of all those problems?

Yes, you BIOS. What are the results of post #8?

Best Regards,
Frederik.

Windows 7: Problem Event Name: BlueScreen

Problem Event Name: BlueScreen problems?