BSOD event log displays critical kernel error 41

[bquig]

*update OS wont boot in AHCI

I got my system to boot last night and tried to let it idle for a couple hours. After about an hour it crashed and displayed the blinking cursor when I came back. I shut it down and left it overnight.

This morning I started it up and let it idle in BIOS for about 40 mins.

I saved the settings and exited after making sure the storage config for SATA1-4 and SATA5-6 was AHCI, made sure the boot drive was set as the SSD.

The system restarted and took a little longer to load asus expressgate (about 10 seconds when set to AHCI, compared to 4 in IDE as before). It then showed AHCI init... in startup. But it only recognizes the other two drives and NOT the SSD.

I spent a few hours trying all possible configurations, and in the end the system will NOT boot unless I set it to IDE.

Again, thanks for reading, I attached the most recent report.

 

[carwiz]

Whooooooooo. Express Gate?

I'll see if someone else want's to look at this.

 

[bquig]

*booted in AHCI

not sure what you mean by that for expressgate, it just loads the settings for the bios i think..anyway

OK, I got it to boot in AHCI. Here's what I did:

I noticed in the SSD corsair toolbox that the firmware was 1.2 and the current one was 5.05 is. When I tried to update it failed.

I found a page on the corsair ssd forum that referenced asimilar problem for updating firmware and said that it must boot in AHCI if the upgrage fails. To set to AHCI after installing in IDE it made reference to a similar tutorial on fixing the registry value's; furthermore, it gave a link for the MS fixit #50470 that fixes the bios not recognizing the SSD in AHCI. I dl'd and ran the fix file from the MS website and afterward, the bios found and loaded the SSD boot drive.

 

[bquig]

I'm not sure if I can post links here, but if anyone wants them I will

 

[bquig]

ok just updated the firmware. Windows recognized it, havent had any issues starting. I'll post if anything happens in the next few days. Thanks so much carwiz!

 

[ICIT2LOL]

My 2 cents bquig mate I would be taking as look at the PSU and run this http://www.sevenforums.com/tutorials/86648-psu-jump-start.html

Check all leads and sockets for reference there is this Voltage Rails - Power Supply 101: A Reference Of Specifications

Specifically look at pin 8 (grey cable) on the 24 pin plug if it is dropping out then the PSU may be gong belly up.

 

[bquig]

Hi Icite I will gladly try your suggestion. But I have a few questions.

What exactly am I doing when I jump the PSU (what am I looking for?).

And how will that help me solve my problem.

Im now getting BSOD everyday, and I cant use my computer for work because its so unstable.
Thanks bQuig

 

[ICIT2LOL]

Hi Icite I will gladly try your suggestion. But I have a few questions.

What exactly am I doing when I jump the PSU (what am I looking for?).

And how will that help me solve my problem.

Im now getting BSOD everyday, and I cant use my computer for work because its so unstable.
Thanks bQuig

The right volts on the different leads and sockets as per that second link. The volts have to be within 0.5% of the required volts ie 11.6v and 12.4V for the 12v rail. anything higher or lower is no good for the operation of the machine or it stability.

 

[bquig]

I read all of the links you sent. I found the part near the end interesting when it referenced a problem starting after a power failure. I was having that problem when my drive was set to IDE: after I would have a BSOD the boot would display the "os not found reboot or press the any key.." or something similar. If I tried ctrl+alt+delete the message would appear again, and similarly with the reset. I would have to press the power button to shut it off then turn it on. Not so much lately it will start right back up now.

I was using HWinfo to monitor the power levels, as per carwize's instruction, and they seemed pretty stable.

Regarding the process of the first link you sent me "test PSU". Is that something similar to HWinfo, or is that something I should do with my voltmeter. I guess I'm still not sure what I am supposed to do throughout the process or what it does by jumping the pins. You suggested I take a look at P8-1, should I be inspecting it physically?

Regarding the BSOD's they seem to come when I am doing a resource intensive task, like photoshop, or using Visual studio, or Chrome. It happens most frequently with chrome as that is what I use it for mostly, streaming a video, using google talk, checking email, etc..Often I may have a couple dozen tabs spaced throughout several windows.

For example, this morning I had CNN streaming on one monitor and I had an incoming call on google voice, so I muted the video, and answered the call. I was talking for approx 10 mins when there was some intermittent disturbance on the call, and windows desktop manager failed, then the call continued while desktop recovered, then chrome became unresponsive and when I tried to kill it, BSOD. It usually happens that I can "feel" it is about to BSOD, because the computer will start to hang and/or be temporarily unresponsive for a couple seconds, then resume normally, which gives me a small window to try to save whatever i'm working on, before BSOD event.

I was curious about the rescources chrome uses and so I used rescource monitor to examine chrome and it seems to be using roughly half of my available physical memory:

Thanks for reading

 

[bquig]

here are the readings from an hour