BSOD (does not start in safe mode - or any other mode...)

D

DaddaRule

Contributor
Joined
Oct 16, 2017
Posts
22
Hello. After trying to get a game controller working my (installing/uninstalling windows updates/drivers) PC went in complete BSOD mode. It is not possible to start either in safe mode or any other mode. The first error it stops at when trying safe mode is aswbidsha.sys (removing it only gives me another .sys error it stops at). I am most certain that the problem happened after i tried installing a driver on the HID controller in driver managment (i think that is what it was called, It was six different with the same name). Do anyone please want to help me with this problem or point me in the right direction as I am stumped on how to proceed.

From Daniel
 
I also tried the HDD in a different computer, same results (I don't think it is a hardware problem). The OS is Windows 7. chkdsk and scannow came out fine.
 
Hi DaddaRule,

Your security program, Avast, needs aswbidsha.sys. By removing this driver you indirectly made it impossible for Windows to boot.
This driver is a boot driver, meaning Windows needs it to boot the system so long as Avast is installed. By removing this driver, Avast cannot function properly and Windows can't load.

What Windows version are you using?
Do you have a restore point?
 
axe0 said:
Hi DaddaRule,

Your security program, Avast, needs aswbidsha.sys. By removing this driver you indirectly made it impossible for Windows to boot.
This driver is a boot driver, meaning Windows needs it to boot the system so long as Avast is installed. By removing this driver, Avast cannot function properly and Windows can't load.

What Windows version are you using?
Do you have a restore point?
Click to expand...

Hello. Thank you for replying.
I did copy the sys. file back to it's original place. I removed the file (and placed it back) after the BSOD attack started. I am using Windows 7 (ultimate I think, I'm not sure). I saw one place that a guy went into the reg. files and removed it from the reg list (he had the same avast file poblem). Is this a smart option? I do not have any restore points unfortuantly unfortunantely.
 
I'm not sure I understand what you mean with
I saw one place that a guy went into the reg. files and removed it from the reg list
Click to expand...
What reg. files and what reg list?
 
I am now disabling different drivers in computer management to try and enter the desktop. After disabling different avast startups, it stopped on classpnp.sys. Anyone know what that file is related to (I came across some forum posts that said it was a Fallout 3 file.)
 
Thank you. I am running MemTest now. Does the test end or is it just looping?
ATM: -Time: 1:40min -Test: #8 -Pass:1 -Errors:22
 
I feel like the problem should be in the event logger. Every event stops at the same time, but I'm not sure what I'm looking for... or at. Any ideas
 
The problem looks to be with your RAM, if you have any warranty use it for replacement.
ATM: -Time: 1:40min -Test: #8 -Pass:1 -Errors:22
Click to expand...
 
axe0 said:
The problem looks to be with your RAM, if you have any warranty use it for replacement.
ATM: -Time: 1:40min -Test: #8 -Pass:1 -Errors:22
Click to expand...
Click to expand...

are you sure? I tried the disk in another computer and the same error came. I also tried taking both of them out (one at a time), but it also didn't change. ATM I am cloning the broken disk (so I can mess around with the clone without messing things more up). After I will try switching out the bigger RAMs with older ones.
Thank you axe0 for sticking with me so far. I really appreciate it :)
 
Is it possible that RAM has something to do with the HID controllers when I tried messing with them (trying to put an Xbox one driver on one of them)...
 
Also, I finally managed to get my old clone OS (from nov.2017) up and running. Is there anything I can do to fix the issue (if it's not RAM related) if I try to take Windows files from old OS to the broken one? I'm guessing not.
 
RAM is involved with pretty much everything, it can definitely have something to do with the HID controllers.
Could you run the test with a bootable USB?

If you're not using the right edition of Windows 7, I'm not entirely sure you'll be able to copy files from the working OS to the new OS. With some luck you won't get issues, but with bad luck you'll end up with more trouble, you and I don't know which files were modified and added in between the editions and if you copy a file that has been modified or you don't have a required file, how will it affect the system? If you have bad luck, yet are lucky enough to be able to run SFC and SURT you might be able to replace the old files with the right files and/or add the necessary files.
Nonetheless, if you would like to try and copy files from the old OS to the new OS, I recommend to first make a system backup using software like Acronis or Macrium Reflect in case things go south, if possible. Also, keep in mind that it is best to do this outside of Windows, say in Linux or a WinPE (Windows Preinstallation Environment), because some files cannot be accessed in any way whilst Windows is booted as they are protected by 'System', a user when logged in as 'Administrator' is 1 level below 'System'.
I would recommend the recovery disk from Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums, which is a Win10PE with dozens of software preinstalled that can be used to recover stuff and for testing.
 
Yep. I made a clone. After putting the old (november) HDD into the PC it booted up like normail. Running different tests with bootable USB was not good. I can use different cmd commands, sfc, chkds, regedit, etc. But it would not auto repair (not even install a clean Windows over the old one). Hotfix did also not work.
 
not even install a clean Windows over the old one
Click to expand...
Something I wouldn't do, I'd rather throw away the old one and install Windows.

Could you run the memory test with a bootable USB.
 
I ran the test on the old disk. The old disk boots up fine without any issues, but I see an error on Memtest again. It does not look as bad as it did on the broken disk, though. I can't read the info (don't understand it), but I do believe you had right with the faulty RAM. I will switch out one and go through Memtest again.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top