Asus c90 bluescreen...

I have often blue screen every time I restart from suspend or similar ...

 

Yes, I also gets that bluescreen, and i cant find the damn solution. I have never overclockt exept from turbogear, so i dont think that its the problem. I guess we just have to wait for a new BIOS upgrade, or Vista SP 1...

 

What if you don't overclock? Run for a few weeks with the stock clocks, see if you get the BSOD in that case. Otherwise the culprit is clear...

 

Here I got BSOD about the 10 first times after re-installing vista. It stops after.

 

But i need the turbogear overclock, so i dont think i can try without it for 3 weeks... I hope there will come up an solution soon though!

 

That error mean nothing without the info code from: STOP 0x00000...., we need that code to see in what area you are getting this error. Listen m8, just tried to help because I have been there in the past and I fixed it but BSOD could be cause by many things in your computer from VIDEO to SOUND, BIOS, CHIPSET etc...

Anyway, I hope you solve your troubles,

SIncerely,

RG

 

I got BOSD even if I don't overclock the cpu ...

 

Damn, i gets bluescreen evertime i start the comp. now :S
Something is wrong with this c90 types, and its killing me to not find a solution... Have anyone tested Vista SP1 Beta and figured out if it helps?

 

If you still experience unknown BSOD try the following:
First uninstall Turbo Gear, ATK Media, ATK OSD, ATK Hotkey, ATK Driver(from the control panel)…they are all connected somehow.
Reboot
Then install the ATK Driver first (I took ATK_XP_VT from the Asus support site).
Reboot
Then install Turbo Gear (I took TurboGear_xp_vista_070808, this build has no “top-left” bug)
Next install the ATK Hotkey (ATK_Hotkey_Vist_070710) and Reboot.
Do not use the other ATK Stuff and the Wireless console, useless and made problems (for me).
Finally make sure to have all the other devices installed and updated like the IR Port (ITE_Romote_VT), this gave me also some BSOD.
With this configuration I made it to stay without any BSOD for a long time. It took me some time to find the right setup.
I hope it may help you.

 

I read somewhere on technet that ATK seems to be to blame for alot of BSOD.

For my C90S I'm now about 99% sure its actually a power issue, namely power issues related to the CPU, GPU and devices that draw power. I still get BSOD if I use device in all USB and Express Slot while booting (wireless mouse, WD Passport HDD, 3G Modem and charging mu BT Headset). I also have the boot Affinity set to use both cores. I've done experimenting with the OC and different combos of devices hooked up to it or OC while a something is active and that when BSOD tend to happen. By being aware of this and letting my notebook fully boot (which is alot quicker by using both cores) and being aware of OC while plugging and unplugging devices that use power I tent to avoid BSOD.

Also doesn't hurt to run chkdsk if you have a series of BSOD tends to end a streak, was something that sometimes helped with XP when certain anti virus programs corrupted XP installes.

Don't know why, but with XP on my C90S I tend not to get any BSOD, only in Vista, but then again Vista also uses new a new power management system.

 

BSOD will obviously be blamed on the memory byt this can also be related to a corrupted OS, driver or a bad hardrive, controller or GPU. I suggest that you backup your data then restore the system to factory to start it fresh and see if the BSOD will go away but make sure User Default was loaded in the BIOS before the process.

If the problem persists after that, try a different memory or hardrive to isolate the problem. If still the same results, this can be a power issue then you need to contact ASUS for RMA service.

 

I got my c90 last week pre configed from internet retailer.
I was getting many blue screens, After I reinstalled Vista and downloaded all new drivers fron Asus I have'nt had a blue screen since. Thats 4days now.

Before i reinstalled when i was in gaming mode the fans were quiet now they spin up like 4 little turbine back there. and temps are better now.


John

 

Ok, thank you guys for the help. I think i will try to reinstall Vista and see if the problems continues or not, and of i dont find a solution, i will go back to XP for some time ;-)

 

Brand new notebook, factory settings, 10min use and BSOD (the IRQL_NOT_LESS_OR_EQUAL error reported here)…. Wasn’t happy…

I ran windb on the memory dump from the BSOD and it identified itecir.sys as the likely cause of the problem. Bit of searching around and found this to be a driver used by the infrared hardware.

I ran with the driver enabled for a few days until I could take no more crashes. It was driving me mad but I was too lazy to do anything about it. What made matters worse was I bought it in Taiwan and caught a plane back to London and spend 16h looking at a blue screen on the back of my seat telling me flight information, smack in the face! Kept waking up freeking looking at a blue screen….

I tried to get an updated driver from the vendors website ( http://www.ite.com.tw/) but no luck. Searching on the net and some guy had a similar problem (cant find the link sorry) which he fixed by installing some newer IR driver from ASUS site, but that didn’t work for me and caused crashes on power down.

I don’t care about the infrared…. I uninstalled it (selecting ‘delete the driver software for this device’) and have had no problem since. The specific device can be found in the device manager under “Human Interface Devices -> ITECIR Infrared Receiver (EC RTC_A6)”, click the drivers tab to ensure you have the right one. I had this problem with Vista home premium that came with the machine. I also had it with vista ultimate which in installed after I upgraded the Disk (seggate 7200) and Ram (transcend 3gb). It’s now running Vista ultimate SP1 and so far so good , other than that It’s a sweet laptop, I love the turbo gear on the back.

 

This is a known memory compatibility problem with C90s as incompatible memory modules will cause BSODs. Check out the C90s Memory success report thread for details for compatible ram and how to fix your problem. Unfortunately there is no fix for this problem other than getting the ram replaced. I would suggest selling your incompatible modules to recover your losses.

 

Don’t think it was memory in my case, the debug analysis suggested itecir.sys, after uninstalling that I've had no problem. In my case it appears the IRQL_NOT_LESS_OR_EQUAL error is due to a dodgy driver, but I'll reserve my opinion until im a week or 2 without a BSOD .... so far so good.

 

@ D3X: I think _keith does not have problems with memory compatibility rather with the ITECIR driver.

I had the same issue and I solved it by using this Driver

I recently reinstalled Vista with SP1, and there was no need to install that driver.

 

Just reporting back on the IRQL_NOT_LESS_OR_EQUAL issue...

Since I uninstalled that drive (mentioned previously in this thread) I haven't had any problems with the machine.... in fact I love it, performance is great.

Only thing I'm about to do now is swap the ctrl and fn keys around....

 

If you manage to do that do let us know. I'm not sure anybody confirmed they were able to do it. (many never try they just get used to it)

 

Hi!

Long time, no see I tried to install Vista SP 1, but that didnt solve the problem. I logged in here a few days ago, and installed the driver you linked to, and i think its working!!! NO MORE BLUESCREENS

 

Have somebody heard something new about the 8800 card that asus announced for C90? Or will asus wait for the 9000 series for 15" laptops?

 

I used to get those ....finally got my drivers sorted and it pretty much stopped. Don't get any crashes whatsoever in Kubuntu. It's all Vista/drivers related. If you have incompatible ram, then that will show up in other places too.

 

Installed Vista when I first got this machine and was in BSOD hell. Installed XP and everything was fine. So that probably means my problems are software not hardware. Just reinstalled Vista, and I am back into BSOD hell. I shall try the above workaround and report back.