Windows 7 isn't booting properly

[LinktheDeme]

Pretty much what the thread title says,

CPU i7
OS Hardrive: 128 SDD Corsair
16 GB of DDR RAM
GTX 570

What's happening is when it's booting up windows rather than going immediately to my account it says please wait, after a while it goes to my username I type in the information and a black screen loads until it loads windows. The theme is completely different and it tells me to check event viewer for the admin logs of what went wrong.

I assumed it was my hard drive so I started doing tests and everything checks back clean.
I didn't think it'd be RAM but for shits and giggles I did memtest and everything came back clean as well.

In event viewer a lot of entries by source: Kernel-PnP came up Theres a bunch of these with different strings of text
These levels are warnings

The driver \Driver\AiCharger failed to load for the device PCI\VEN_8086&DEV_1E26&SUBSYS_84CA1043&REV_04\3&115 83659&0&E8

.

This level is error Source :volmgr

Crash dump initialization failed!

Source: Kernel-Eventtracing

Session "Microsoft-Windows-Setup" stopped due to the following error: 0xC000000D

Source: Win login

The winlogon notification subscriber <GPClient> was unavailable to handle a critical notification event.

Im not sure if this is enough but I have no idea what's going wrong here. I am using HD Tune Pro 5.50 to test my HDD currently. Nothing wrong with it so far. . .

[LinktheDeme]

Hm it seems to be working fine after a system restore currently, still trying to figure out what the whole cause was.

[orinthia]

Did a quick search on that device; appears to be Intel's USB host controller. Either something attached to it messed up, some software using it messed up, or the controller itself messed up. Since a system restore allowed you to progress and for the machine to work again, something you installed, updated, or added recently that was USB might have done something.

At least, I would check with that first. This could be entirely misleading though, especially if nothing was changed recently. Perhaps something was plugged in on boot that caused some problems?

Also, what is "AiCharger"? Is this the ASUS charging software for usb things? Looking that up; it's mainly to allow for charging a USB device while under different power states, like standby and such. I'd probably get rid of it but I don't have any devices that are in need of my computer being their charging station. ...or you might not even have/use this.

Quickly looking at other results, like the setup error, could be any number of things unfortunately...

[LinktheDeme]

Did a quick search on that device; appears to be Intel's USB host controller. Either something attached to it messed up, some software using it messed up, or the controller itself messed up. Since a system restore allowed you to progress and for the machine to work again, something you installed, updated, or added recently that was USB might have done something.

At least, I would check with that first. This could be entirely misleading though, especially if nothing was changed recently. Perhaps something was plugged in on boot that caused some problems?

Also, what is "AiCharger"? Is this the ASUS charging software for usb things? Looking that up; it's mainly to allow for charging a USB device while under different power states, like standby and such. I'd probably get rid of it but I don't have any devices that are in need of my computer being their charging station. ...or you might not even have/use this.

Quickly looking at other results, like the setup error, could be any number of things unfortunately...

Well apperantly i've been getting these for a while im assuming they trigger because my phone charger in my computer. Connecting and disconnecting it probably causes them I'd presume. Maybe it was just a bad windows update or something

[xopher]

Probably a bad driver got installed or something. All a System Restore does is roll back the registry.

[LinktheDeme]

Probably a bad driver got installed or something. All a System Restore does is roll back the registry.

Most likely, still trying to figure out why this appears in my event viewer almost every bootup

Session "Microsoft-Windows-Setup" stopped due to the following error: 0xC000000D

I tried the sfc/scannow via this link
http://answers.microsoft.com/en-us/w...f-7aee8b31f49a

No errors found or corrected im assuming its some minor issue though and not relate. Thanks again for the help everyone!

[LinktheDeme]

I may have figured out what causes it after repeating it the issue seems to come back but I don't understand why?

When I go to my volume, right click and go to recording devices I go to my line in, right click then properties. From here I go to the listen tab and check the box to listen to this device. Upon rebooting the issue repeats if I boot it after this and I have to do a system restore to fix it. How do I stop it from doing this? ._.

What I'm wondering is that if I check it then uncheck it then shutdown to boot if this issue returns. I can't do a proper shut down once it happens and this doesn't seem like something that normally should be occuring.

edit: I Was able to do a proper shut down while unchecking it and it rebooted with no issues. This is a picture apparently if the circled box is checked it causes the issues I mentioned. I don't understand why or if this is a common issue. . . I couldn't find anything on google regarding it

[orinthia]

Weird... The realtek drivers probably have issues then. See if there's an updated/alternate version on their website.

[LinktheDeme]

Weird... The realtek drivers probably have issues then. See if there's an updated/alternate version on their website.

Yeah I was fiddling with my audio drivers as I posted that, a very odd issue to have. I don't have the issue anymore after I re-installed the realtek drivers however they don't start their software when I boot my computer now which makes me wonder if that's part of the issue as well as they were conflicting on what to do. I don't feel like testing it to that point as it's all working now. Thank you orinthia!

I appreciate everyone's help and feedback it helped me out a lot. I didn't even think about my drivers until after xopher mentioned it was a driver issue then I recalled I recently made that change in my driver area. So thank you again orinthia and Xopher you helped out a lot!