Asus G73JH PSOD, Out of Warrenty

Hello everyone,

I was just hit by PSOD (Psychedelic Screen of Death). Yay me

Some Background on the Problem/Research:

I hadn't even heard about it before this morning when I started researching . It looks very similar to the example in this video, though the left side is scrolling horizontal lines instead:

Asus G73JH PSOD Hardware Failure on Originally purchased X1 model - YouTube

My external monitor still works completely fine. It seems to have happened when I accidentaly brushed the FN + F8 keys (change projection mode, Laptop/Projector/Both) which may hove changed the resolution (seems to be the common cause of PSOD) though it could have been caused by my intended target FN + F7 (Turn off/on LCD).

All of this seems to match what has been said on another thread of this forum:

http://forum.notebookreview.com/asu...us-g73jh-originals-owners-didnt-get-psod.html

My Question:

As the title says I'm pretty sure I'm out of the warrenty as I purchased the laptop June of 2009 (I think). So I can't take the advice that everyone seems to be giving, "Just RMA it back".

If I replace the LCD will it fix the problem?

I saw some cases of multiple PSOD incidents. What is the likelyhood that this will happen to me as I will be forking out about $100 to replace the LCD?

And just general advice, I'm more than a little frustrated

Thanks in advance!


*********EDIT*********

Some more info in post 3

 

Well, if you read about the cause of the PSOD, you'd know that it's caused by (insert solution 1 here) and can be linked back to a faulty (insert solution 2 here).

Solution 1 is...
a) a short in the screen
b) a GPU voltage spike
c) pebkac related errors
d) not the same in every case
e) all of the above
f) none of the above

Solution 2 is...
a) Manufacturing problems
b) Installation problems
c) Humidity problems
d) GPU that gives off voltage spikes
e) Pebkac errors
f) ID 10-t errors (check the error log).

So, that means that you will/wont (true/false) have problems if you get a new screen. It also means you should/not (true/false) get a qualified ASUS repair depot to do the work for you.

 

Well I suppose that's the problem really. Everyone has a different hypothosis as to what caused it but very few methods (viable for the average person) of testing these guesses. From everything I've read its all just speculation then "RMA it".

If anyone has any way for me to do some tests listed above or otherwise it would be appreciated as I'm guessing it wouldn't be cheap to have Asus or anyone else run a battery of tests.

******EDIT******

I did look at the "Event Veiwer" around the time that it happened (I assume that is what is ment by "error log" as its pretty vauge and i have no idea what a 10-t error is) and found this:



0000000022: 2011-12-03 11:47:48:231 Unable to obtain Color Correction information, dem status: -1
Error Called by: ATI.ACE.CLI.Aspect.DeviceCRT.Graphics.Runtime.RT_DeviceCRT:arse processID:05612 threadID ) domainNameCCC.exe ) assemblyNameCLI.Aspect.DeviceCRT.Graphics.Runtime, Version=2.0.3638.29658, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
-----------------------------------------------------------------------------------------------------------------------



0000000021: 2011-12-03 11:47:48:231 iDEMDriverSettings.GetCRTDisplayLimitsInfo failed with status -1
Error Called by: ATI.ACE.CLI.Aspect.DeviceCRT.Graphics.Runtime.RT_DeviceCRT:rivateRefresh processID:05612 threadID ) domainNameCCC.exe ) assemblyNameCLI.Aspect.DeviceCRT.Graphics.Runtime, Version=2.0.3638.29658, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------




0000000024: 2011-12-03 11:47:48:571 Exception: Thread was being aborted.
Exception Called by: System.Threading.ExecutionContext::runTryCode processID:05612 threadIDDashboard DisplayColour Refresh Thread) domainNameCCC.exe ) assemblyNamemscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
************************************************************************************************************************


0000000018: 2011-12-03 11:47:48:231 iDEMDriverSettings.GetCRTDisplayInfo failed with status -1
Error Called by: ATI.ACE.CLI.Aspect.DeviceCRT.Graphics.Runtime.RT_DeviceCRT:rivateRefresh processID:05612 threadID ) domainNameCCC.exe ) assemblyNameCLI.Aspect.DeviceCRT.Graphics.Runtime, Version=2.0.3638.29658, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------



0000000017: 2011-12-03 11:47:48:231 iDEMDeviceCommonSettings.GetDeviceHDTVForceModeInfo failed with status -1
Error Called by: ATI.ACE.CLI.Aspect.DeviceCRT.Graphics.Runtime.RT_DeviceCRT:rivateRefresh processID:05612 threadID ) domainNameCCC.exe ) assemblyNameCLI.Aspect.DeviceCRT.Graphics.Runtime, Version=2.0.3638.29658, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------



0000000020: 2011-12-03 11:47:48:231 iDEMDriverSettings.GetCRTControllerSupportedResolution failed with status -1
Error Called by: ATI.ACE.CLI.Aspect.DeviceCRT.Graphics.Runtime.RT_DeviceCRT:rivateRefresh processID:05612 threadID ) domainNameCCC.exe ) assemblyNameCLI.Aspect.DeviceCRT.Graphics.Runtime, Version=2.0.3638.29658, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------


0000000019: 2011-12-03 11:47:48:231 iDEMDriverSettings.GetCRTDisplayConfig failed with status -1
Error Called by: ATI.ACE.CLI.Aspect.DeviceCRT.Graphics.Runtime.RT_DeviceCRT:rivateRefresh processID:05612 threadID ) domainNameCCC.exe ) assemblyNameCLI.Aspect.DeviceCRT.Graphics.Runtime, Version=2.0.3638.29658, Culture=neutral, PublicKeyToken=90ba9c70f846762e)
------------------------------------------------------------------------------------------------------------------------



All of these errors orccured in the same min. These errors and a few others that pop in and out repeat throughout the day (it started this morning). I'll do some searching bt any insight would be helpful.


I can also confirm that these errors only appear in the log when the main monitor is turned on. (I have turned it off by setting the laptop to external projector only but they reapear as soon as i switch back to it).


Also of note there are sets of errors that are similar to the ones above (though there are some different ones) leading up to the incident they appear about once everyother day and the ones that appear vary but

"Unable to obtain Color Correction information, dem status: -2"

seems to be pretty consistant. I had no knowledge of these errors.

 

bumping as i would still love some advice from some people who have experienced this problem

 

I believe Asus G73jh is released in Feb 2010 (showcased in Jan 2010), therefore it's impossible to get it on June 2009? Check your receipt if you still have it, or call customer support and give them your laptop number located at the bottom. They will be able to find out the manufacturer date for you as well.

If the asus g73 laptop is model comes with 1 year warranty, it could be out of warranty.