BSOD after clean Win7 installation on new SSD Kingston

P911T · 03 Mar 2012

writhziden said:

Okay, I think I understand now. Sorry, was not aware you had already tried those steps.

Can you post the hardware ids for the devices listed as not known for the laptop? To find the hardware IDs, go to device manager, right click any unknown devices, Properties, the details tab, and then change the property to Hardware IDs.

first device: broadcom ush

Code:

USB\VID_0A5C&PID_5800&REV_0101&MI_00
USB\VID_0A5C&PID_5800&MI_00

for the second and third device (listed as unknown devices) there is no property ID

do you want to know any other property?

writhziden · 03 Mar 2012

I would try right clicking each device and clicking update driver. I do not usually recommend this because Windows usually does not have the most up to date driver in the database, but Windows sometimes can find drivers that we cannot, and this helps.

Also, I recommend trying the hardware device fix it tool: Hardware devices are not working or are not detected in Windows

P911T · 03 Mar 2012

Right clicking to update drivers and fix it tool didnt help

What about to disable these devices? Is there possibility that then they stop to cause bsod?

writhziden · 03 Mar 2012

You could try it. I do not know what devices are missing other than the Broadcom device. Something seems off about the driver installation for the system...

P911T · 04 Mar 2012

Hi I tried to disable it and it seemed to be a bit stable. So I planned disk check, but after reboot and startin diskcheck I got BSOD BAD_SYSTEM_CONFIG_INFO (0x00...074) . I attached info about it (I am not sure if there is correct info because latest dump file has wrong date).

writhziden · 04 Mar 2012

Yeah, I already analyzed the most recent crash you have in there...

For the crash that did not show up in your .dmp files:

Bug Check 0x74: BAD_SYSTEM_CONFIG_INFO

Cause
The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is unlikely, because the boot loader, known as NT Loader (NTLDR) in versions of Windows prior to Vista, checks a hive for corruption when it loads the hive.
This bug check can also occur if some critical registry keys and values are missing. Thee keys and values might be missing if a user manually edited the registry.
Resolution
Try restarting the computer by selecting "last known good configuration" in the boot options.
If the restart does not fix the problem, the registry damage is too extensive. You must reinstall the OS or use the Emergency Repair Disk (ERD) that you previously created by using the Windows Backup tool.