PDA

View Full Version : a new G74sx owner's worries



kokopuffs
05-29-2012, 08:37 AM
Hi, I just very recently got my G74sx-91185v(3D) on the first day of owning this powerhouse. I already got the blue screen of death. Force shutdown, and it didn't happened anymore. Though till today(about 3 weeks now) I have not seen another one. So to summarize everything,

Google chrome crashes, I cannot exit my Black Ops the normal way, have to force it to shutdown using the task manager. There are instances where my entire screen becomes a shade of RED and freezes. the first time was when I was previewing my torrent download, while fast forwarding, it happened. The second time was when i first plugged my laptop to my TV via HDMI cable, the entire MSN messenger window is a solid shade of RED, I thought it was the HDMI cable not working properly so i unplugged it. But it remained. I restarted my laptop, and it wouldn't go away. I turned off my MSN messenger and when I turned it back on the second day, it was back to normal. What really happened?


Another one was when I tried updating my graphic driver, as prompted by the Asus Live Updater. Though I already fixed it, but I guess I should mention it. It restarted my laptop without asking and when it was back on. It was all fat (low resolution) the highest I could go up to was 1280 D: anyway, I uninstalled the entire graphic driver and downloaded it from the asus site.


Another one of my major concerns would be my bootup time. It is terrible. :( My previous laptop is about 3 years old, and it boots much better. There are a lot of things I do not understand. I even uninstalled a bunch of bloatwares but it didn't help. I am tempted to bring this back to the retailer store and ask them to fix it, but it is soooo far away. -.-

So to all the respected users and veterans of the Asus G-Series. I, a newcomer to the ROG humbly asks for assistance. I really love this laptop. After starting up and when everything is loaded, it runs nicely and I can game pretty much ok. I really hope the things I mentioned above wouldn't kill this laptop :(

cbolin21
05-29-2012, 11:55 AM
Well even though I am still new here, Welcome to the forums. The Blue screen of death I have experience with. You can get information from the the crash using Blue Screen View (http://download.cnet.com/BlueScreenView/3000-2094_4-10965136.html). My problem was that something was loose in my system. Also as I'm sure others will mention it too, I have uninstalled the Asus live updater as well as the the Nvidia update. Seems to be a couple topics on here about screen problems. You could try to read those to see if anyone else is having that problem. As for Google Chrome, I run it too and I have yet to have a problem. You could try to uninstall and re install.

chrsplmr
05-29-2012, 12:14 PM
I would pop off the Memory cover and re-seat it .. first.

Most BSOD issues are Memory related ..
the red part though .. could be a cross between the Lan, Gpu and OS.

If there is return time to the retailer .. it may be worth the drive ..
as a 'just in case' ... not saying there is an issue, no sure .. but why
mess around with it ... for a drive. (up to you.)

Best of Luck...and indeed, Welcome.c.

iluvatar
05-29-2012, 12:39 PM
Since the laptop is still new, I would recommend you format it and install a fresh copy of win7 on it with the newest drivers. If after that there are still issues remaining, they might be related to hardware issues.

If you don't want to reinstall windows, at least clear the laptop of all the bloatware. The only thing you need is the atk package, for everything else windows has its own features which are just as good. (I don't even use Power4Gear)
If you find that you can't uninstall something properly, you might want to consider a program like Revo uninstaller (which removes all traces of a given program). Also go to msconfig->startup and remove all entries that are not needed (out of the +30 entries listed there, I only have 5 selected).
I found this page quite helpful, but i'm not sure if g73 and g74 use same drivers: http://forum.notebookreview.com/asus-gaming-notebook-forum/583215-g73sw-g53sw-latest-drivers-everything-you-need-fresh-install.html
Finally, can you still exchange your laptop? I would get the new g75 instead..

dstrakele
05-29-2012, 01:20 PM
Folks have encountered video issues similar to what you describe after an ASUS Live Update See http://rog.asus.com/forum/showthread.php?15953-Asus-G74sx-91234z-Asus-live-update-result-in-screen-resolution-problem!!-Advise-pls&country=&status=. In this thread, I recommend using Windows System Restore to bring your system back to a time before the ASUS Live Update that caused the video issue.

"Pink screen" issues have also been reported for NVIDIA driver versions 296.10 through 301.24. 295.73 appears to be the most stable of the recent drivers (at least from reports in this forum).

I agree with @cbolin's recommendation to uninstall ASUS Live Update and use BlueScreenView from Nirsoft to further troubleshoot your reported BSOD.

Alternatively, you could do an ASUS Factory Restore by pressing F9 at the ASUS splash screen and choosing to restore Windows to the first partition. It will completely overwrite your OS partition, so backup any important files you've stored there. See if you can reproduce any of your issues and make your decision whether to keep your system if you are still within your retailer's exchange/return period.

kokopuffs
05-29-2012, 03:05 PM
I would pop off the Memory cover and re-seat it .. first.

Most BSOD issues are Memory related ..
the red part though .. could be a cross between the Lan, Gpu and OS.

If there is return time to the retailer .. it may be worth the drive ..
as a 'just in case' ... not saying there is an issue, no sure .. but why
mess around with it ... for a drive. (up to you.)

Best of Luck...and indeed, Welcome.c.



as I am relatively new to these kinda things, is there a picture tutorial on how i can do that? FYI, the last laptop to this current laptop is a huge FLIGHT FOR ME. from a completely non-gaming notebook to a power house. So i'm pretty nervous.. :S

kokopuffs
05-29-2012, 03:08 PM
I really appreciate the warm responses from everyone. I cannot thank you all enough. At least I know I am not alone :) will post my BSOD RESULTS soon

kokopuffs
05-29-2012, 03:10 PM
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path
PSHED.dll fffff880`00ca1000 fffff880`00cb5000 0x00014000 0x4a5be027 7/14/2009 9:32:23 AM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll
ntoskrnl.exe ntoskrnl.exe+11f2b fffff800`03460000 fffff800`03a49000 0x005e9000 0x4e02aaa3 6/23/2011 10:53:23 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17803 (win7sp1_gdr.120330-1504) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
AiCharger.sys fffff880`0fa35000 fffff880`0fa37880 0x00002880 0x4e7be938 9/23/2011 10:04:40 AM ASUS Ai Charger ASUS Charger driver 1.00.01 built by: WinDDK ASUSTek Computer Inc. C:\Windows\system32\drivers\AiCharger.sys
WudfPf.sys fffff880`02a59000 fffff880`02a7a000 0x00021000 0x4ce7a624 11/20/2010 6:42:44 PM
WMILIB.SYS fffff880`00faa000 fffff880`00fb3000 0x00009000 0x4a5bc117 7/14/2009 7:19:51 AM
wmiacpi.sys fffff880`055df000 fffff880`055e8000 0x00009000 0x4a5bc3b6 7/14/2009 7:31:02 AM
win32k.sys fffff960`00020000 fffff960`00333000 0x00313000 0x00000000
wfplwf.sys fffff880`04cbf000 fffff880`04cc8000 0x00009000 0x4a5bccb6 7/14/2009 8:09:26 AM
WDFLDR.SYS fffff880`00f44000 fffff880`00f53000 0x0000f000 0x4a5bc11a 7/14/2009 7:19:54 AM
Wdf01000.sys fffff880`00ea0000 fffff880`00f44000 0x000a4000 0x4a5bc19f 7/14/2009 7:22:07 AM
watchdog.sys fffff880`04db9000 fffff880`04dc9000 0x00010000 0x4a5bc53f 7/14/2009 7:37:35 AM
wanarp.sys fffff880`01c5e000 fffff880`01c79000 0x0001b000 0x4ce7a874 11/20/2010 6:52:36 PM
vwififlt.sys fffff880`047e9000 fffff880`047ff000 0x00016000 0x4a5bcc3a 7/14/2009 8:07:22 AM
vwifibus.sys fffff880`0a926000 fffff880`0a933000 0x0000d000 0x4a5bcc39 7/14/2009 8:07:21 AM
volsnap.sys fffff880`01aca000 fffff880`01b16000 0x0004c000 0x4d67242a 2/25/2011 11:38:18 AM
volmgrx.sys fffff880`00e3f000 fffff880`00e9b000 0x0005c000 0x4ce792eb 11/20/2010 5:20:43 PM
volmgr.sys fffff880`00e2a000 fffff880`00e3f000 0x00015000 0x4ce792a0 11/20/2010 5:19:28 PM
VIDEOPRT.SYS fffff880`04d94000 fffff880`04db9000 0x00025000 0x4a5bc58b 7/14/2009 7:38:51 AM
vga.sys fffff880`04d86000 fffff880`04d94000 0x0000e000 0x4a5bc587 7/14/2009 7:38:47 AM
vdrvroot.sys fffff880`00ff0000 fffff880`00ffd000 0x0000d000 0x4a5bcadb 7/14/2009 8:01:31 AM
usbvideo.sys fffff880`0687d000 fffff880`068aa280 0x0002d280 0x4ce7a692 11/20/2010 6:44:34 PM
USBSTOR.SYS fffff880`068ab000 fffff880`068c6000 0x0001b000 0x4d79a6fc 3/11/2011 12:37:16 PM
USBPORT.SYS fffff880`01564000 fffff880`015ba000 0x00056000 0x4d8c0c08 3/25/2011 11:29:12 AM
usbhub.sys fffff880`01400000 fffff880`0145a000 0x0005a000 0x4d8c0c15 3/25/2011 11:29:25 AM
usbehci.sys fffff880`107e7000 fffff880`107f8000 0x00011000 0x4d8c0c00 3/25/2011 11:29:04 AM
USBD.SYS fffff880`0a96f000 fffff880`0a970f00 0x00001f00 0x4d8c0bfb 3/25/2011 11:28:59 AM
usbccgp.sys fffff880`06860000 fffff880`0687d000 0x0001d000 0x4d8c0c0a 3/25/2011 11:29:14 AM
umbus.sys fffff880`017e5000 fffff880`017f7000 0x00012000 0x4ce7a695 11/20/2010 6:44:37 PM
udfs.sys fffff880`06600000 fffff880`06655000 0x00055000 0x4ce79433 11/20/2010 5:26:11 PM
TurboB.sys fffff880`0332f000 fffff880`03336000 0x00007000 0x4cf43107 11/30/2010 7:02:31 AM
tunnel.sys fffff880`01600000 fffff880`01626000 0x00026000 0x4ce7a846 11/20/2010 6:51:50 PM
TSDDD.dll fffff960`00440000 fffff960`0044a000 0x0000a000 0x00000000
termdd.sys fffff880`023e5000 fffff880`023f9000 0x00014000 0x4ce7ab0c 11/20/2010 7:03:40 PM
tdx.sys fffff880`04c00000 fffff880`04c22000 0x00022000 0x4ce79332 11/20/2010 5:21:54 PM
TDI.SYS fffff880`04c22000 fffff880`04c2f000 0x0000d000 0x4ce7933e 11/20/2010 5:22:06 PM
tcpipreg.sys fffff880`0422e000 fffff880`04240000 0x00012000 0x4ce7a844 11/20/2010 6:51:48 PM
tcpip.sys fffff880`0187c000 fffff880`01a80000 0x00204000 0x4e001123 6/21/2011 11:33:55 AM
SynTP.sys fffff880`05434000 fffff880`05594000 0x00160000 0x4d71325d 3/5/2011 2:41:33 AM
swenum.sys fffff880`05422000 fffff880`05423480 0x00001480 0x4a5bca92 7/14/2009 8:00:18 AM
srvnet.sys fffff880`03200000 fffff880`03231000 0x00031000 0x4dba2aff 4/29/2011 11:05:35 AM
srv2.sys fffff880`066e1000 fffff880`0674a000 0x00069000 0x4dba2b0a 4/29/2011 11:05:46 AM
srv.sys fffff880`0674a000 fffff880`067e2000 0x00098000 0x4dba2b1e 4/29/2011 11:06:06 AM
spldr.sys fffff880`01b16000 fffff880`01b1e000 0x00008000 0x4a0858bb 5/12/2009 12:56:27 AM
secdrv.SYS fffff880`04223000 fffff880`0422e000 0x0000b000 0x4508052e 9/13/2006 9:18:38 PM
RTKVHD64.sys fffff880`068e7000 fffff880`06b99100 0x002b2100 0x4da44036 4/12/2011 8:06:14 PM
Rt64win7.sys fffff880`0a971000 fffff880`0a9e6000 0x00075000 0x4db07445 4/22/2011 2:15:33 AM
rspndr.sys fffff880`03317000 fffff880`0332f000 0x00018000 0x4a5bcc92 7/14/2009 8:08:50 AM
rfcomm.sys fffff880`0653e000 fffff880`0656a000 0x0002c000 0x4a5bcc20 7/14/2009 8:06:56 AM
rdyboost.sys fffff880`01b1e000 fffff880`01b58000 0x0003a000 0x4ce7982e 11/20/2010 5:43:10 PM
rdprefmp.sys fffff880`04ddb000 fffff880`04de4000 0x00009000 0x4a5bce63 7/14/2009 8:16:35 AM
rdpencdd.sys fffff880`04dd2000 fffff880`04ddb000 0x00009000 0x4a5bce62 7/14/2009 8:16:34 AM
RDPCDD.sys fffff880`04dc9000 fffff880`04dd2000 0x00009000 0x4a5bce62 7/14/2009 8:16:34 AM
rdbss.sys fffff880`01800000 fffff880`01851000 0x00051000 0x4ce79497 11/20/2010 5:27:51 PM
rassstp.sys fffff880`0a9e6000 fffff880`0aa00000 0x0001a000 0x4a5bccf1 7/14/2009 8:10:25 AM
raspptp.sys fffff880`01641000 fffff880`01662000 0x00021000 0x4ce7a86f 11/20/2010 6:52:31 PM
raspppoe.sys fffff880`01626000 fffff880`01641000 0x0001b000 0x4a5bcce9 7/14/2009 8:10:17 AM
rasl2tp.sys fffff880`0a61e000 fffff880`0a642000 0x00024000 0x4ce7a872 11/20/2010 6:52:34 PM
PxHlpa64.sys fffff880`01000000 fffff880`0100c040 0x0000c040 0x4addfcaa 10/21/2009 2:08:42 AM
portcls.sys fffff880`0644d000 fffff880`0648a000 0x0003d000 0x4a5bcc03 7/14/2009 8:06:27 AM
peauth.sys fffff880`0333e000 fffff880`033e4000 0x000a6000 0x4a5bd8df 7/14/2009 9:01:19 AM
pcw.sys fffff880`01549000 fffff880`0155a000 0x00011000 0x4a5bc0ff 7/14/2009 7:19:27 AM
PCIIDEX.SYS fffff880`00dda000 fffff880`00dea000 0x00010000 0x4a5bc114 7/14/2009 7:19:48 AM
pciide.sys fffff880`00dd3000 fffff880`00dda000 0x00007000 0x4a5bc115 7/14/2009 7:19:49 AM
pci.sys fffff880`00fbd000 fffff880`00ff0000 0x00033000 0x4ce7928f 11/20/2010 5:19:11 PM
partmgr.sys fffff880`00e00000 fffff880`00e15000 0x00015000 0x4ce792c0 11/20/2010 5:20:00 PM
pacer.sys fffff880`01b9a000 fffff880`01bc0000 0x00026000 0x4ce7a862 11/20/2010 6:52:18 PM
nwifi.sys fffff880`032b1000 fffff880`03304000 0x00053000 0x4a5bcc3b 7/14/2009 8:07:23 AM
nvstusb.sys fffff880`0658a000 fffff880`065aa000 0x00020000 0x4d90057d 3/28/2011 11:50:21 AM
nvlddmkm.sys fffff880`0fa39000 fffff880`106aab80 0x00c71b80 0x4db80525 4/27/2011 7:59:33 PM
nvhda64v.sys fffff880`013bc000 fffff880`013e9000 0x0002d000 0x4d6fbac6 3/3/2011 11:59:02 PM
nvBridge.kmd fffff880`106ab000 fffff880`106ac180 0x00001180 0x4db7fada 4/27/2011 7:15:38 PM
Null.SYS fffff880`04d76000 fffff880`04d7f000 0x00009000 0x4a5bc109 7/14/2009 7:19:37 AM
ntk_PowerDVD_64.sys fffff880`04200000 fffff880`04223000 0x00023000 0x4c57db8c 8/3/2010 5:04:12 PM
Ntfs.sys fffff880`01204000 fffff880`013a7000 0x001a3000 0x4d79997b 3/11/2011 11:39:39 AM
nsiproxy.sys fffff880`01851000 fffff880`0185d000 0x0000c000 0x4a5bc15e 7/14/2009 7:21:02 AM
Npfs.SYS fffff880`04def000 fffff880`04e00000 0x00011000 0x4a5bc114 7/14/2009 7:19:48 AM
NETIO.SYS fffff880`0175a000 fffff880`017ba000 0x00060000 0x4ce79381 11/20/2010 5:23:13 PM

kokopuffs
05-29-2012, 03:11 PM
netbt.sys fffff880`0462a000 fffff880`0466f000 0x00045000 0x4ce79386 11/20/2010 5:23:18 PM
netbios.sys fffff880`0466f000 fffff880`0467e000 0x0000f000 0x4a5bccb6 7/14/2009 8:09:26 AM
NDProxy.SYS fffff880`013a7000 fffff880`013bc000 0x00015000 0x4ce7a864 11/20/2010 6:52:20 PM
ndiswan.sys fffff880`0a642000 fffff880`0a671000 0x0002f000 0x4ce7a870 11/20/2010 6:52:32 PM
ndisuio.sys fffff880`03304000 fffff880`03317000 0x00013000 0x4ce7a7e0 11/20/2010 6:50:08 PM
ndistapi.sys fffff880`05416000 fffff880`05422000 0x0000c000 0x4a5bccd8 7/14/2009 8:10:00 AM
ndis.sys fffff880`01667000 fffff880`0175a000 0x000f3000 0x4d1ad232 12/29/2010 2:16:18 PM
mup.sys fffff880`01b58000 fffff880`01b6a000 0x00012000 0x4a5bc201 7/14/2009 7:23:45 AM
mssmbios.sys fffff880`0185d000 fffff880`01868000 0x0000b000 0x4a5bc3be 7/14/2009 7:31:10 AM
msrpc.sys fffff880`0145e000 fffff880`014bc000 0x0005e000 0x4ce79334 11/20/2010 5:21:56 PM
msisadrv.sys fffff880`00fb3000 fffff880`00fbd000 0x0000a000 0x4a5bc0fe 7/14/2009 7:19:26 AM
Msfs.SYS fffff880`04de4000 fffff880`04def000 0x0000b000 0x4a5bc113 7/14/2009 7:19:47 AM
msahci.sys fffff880`01197000 fffff880`011a2000 0x0000b000 0x4ce7a416 11/20/2010 6:33:58 PM
mrxsmb20.sys fffff880`043c9000 fffff880`043ed000 0x00024000 0x4db781e9 4/27/2011 10:39:37 AM
mrxsmb10.sys fffff880`0437b000 fffff880`043c9000 0x0004e000 0x4e17c104 7/9/2011 10:46:28 AM
mrxsmb.sys fffff880`0434e000 fffff880`0437b000 0x0002d000 0x4db78226 4/27/2011 10:40:38 AM
mpsdrv.sys fffff880`04336000 fffff880`0434e000 0x00018000 0x4a5bcc79 7/14/2009 8:08:25 AM
mountmgr.sys fffff880`00c00000 fffff880`00c1a000 0x0001a000 0x4ce79299 11/20/2010 5:19:21 PM
mouhid.sys fffff880`02bcb000 fffff880`02bd8000 0x0000d000 0x4a5bca94 7/14/2009 8:00:20 AM
mouclass.sys fffff880`0559e000 fffff880`055ad000 0x0000f000 0x4a5bc116 7/14/2009 7:19:50 AM
monitor.sys fffff880`06672000 fffff880`06680000 0x0000e000 0x4a5bc58c 7/14/2009 7:38:52 AM
mcupdate_GenuineIntel.dll fffff880`00c52000 fffff880`00ca1000 0x0004f000 0x4ce7c737 11/20/2010 9:03:51 PM
MBfilt64.sys fffff880`06b9a000 fffff880`06ba8000 0x0000e000 0x4a7267b0 7/31/2009 11:40:32 AM
luafv.sys fffff880`02a36000 fffff880`02a59000 0x00023000 0x4a5bc295 7/14/2009 7:26:13 AM
lltdio.sys fffff880`02a7a000 fffff880`02a8f000 0x00015000 0x4a5bcc92 7/14/2009 8:08:50 AM
ksthunk.sys fffff880`064ac000 fffff880`064b1200 0x00005200 0x4a5bca93 7/14/2009 8:00:19 AM
ksecpkg.sys fffff880`017ba000 fffff880`017e5000 0x0002b000 0x4ce79e9a 11/20/2010 6:10:34 PM
ksecdd.sys fffff880`014bc000 fffff880`014d7000 0x0001b000 0x4ce7930b 11/20/2010 5:21:15 PM
ks.sys fffff880`015ba000 fffff880`015fd000 0x00043000 0x4ce7a3f3 11/20/2010 6:33:23 PM
klmouflt.sys fffff880`05594000 fffff880`0559e000 0x0000a000 0x4aef081e 11/3/2009 12:26:06 AM
klim6.sys fffff880`04cc8000 fffff880`04cd1000 0x00009000 0x4d78e1d2 3/10/2011 10:36:02 PM
klif.sys fffff880`04cd3000 fffff880`04d76000 0x000a3000 0x4daeb6b7 4/20/2011 6:34:31 PM
kl2.sys fffff880`04c2f000 fffff880`04c36000 0x00007000 0x4d70ae2b 3/4/2011 5:17:31 PM
kl1.sys fffff880`01c7d000 fffff880`023dc000 0x0075f000 0x4d70aec3 3/4/2011 5:20:03 PM
kdcom.dll fffff800`00bc6000 fffff800`00bd0000 0x0000a000 0x4d4d8061 2/6/2011 12:52:49 AM
kbfiltr.sys fffff880`055ad000 fffff880`055b5000 0x00008000 0x4a643726 7/20/2009 5:21:42 PM
kbdhid.sys fffff880`02bd8000 fffff880`02be6000 0x0000e000 0x4ce7a3f5 11/20/2010 6:33:25 PM
kbdclass.sys fffff880`055b5000 fffff880`055c4000 0x0000f000 0x4a5bc116 7/14/2009 7:19:50 AM
intelppm.sys fffff880`055c9000 fffff880`055df000 0x00016000 0x4a5bc0fd 7/14/2009 7:19:25 AM
iaStor.sys fffff880`01010000 fffff880`01164000 0x00154000 0x4cd50774 11/6/2010 3:44:52 PM
i8042prt.sys fffff880`0a600000 fffff880`0a61e000 0x0001e000 0x4a5bc11d 7/14/2009 7:19:57 AM
hwpolicy.sys fffff880`023dc000 fffff880`023e5000 0x00009000 0x4ce7927e 11/20/2010 5:18:54 PM
HTTP.sys fffff880`0424f000 fffff880`04318000 0x000c9000 0x4ce793ce 11/20/2010 5:24:30 PM
hidusb.sys fffff880`02bbd000 fffff880`02bcb000 0x0000e000 0x4ce7a665 11/20/2010 6:43:49 PM
HIDPARSE.SYS fffff880`068d6000 fffff880`068de080 0x00008080 0x4a5bcbf9 7/14/2009 8:06:17 AM
HIDCLASS.SYS fffff880`065cf000 fffff880`065e8000 0x00019000 0x4ce7a665 11/20/2010 6:43:49 PM
HECIx64.sys fffff880`0fa24000 fffff880`0fa35000 0x00011000 0x4c98e458 9/22/2010 12:59:04 AM
HDAudBus.sys fffff880`0fa00000 fffff880`0fa24000 0x00024000 0x4ce7a65e 11/20/2010 6:43:42 PM
hal.dll fffff800`03417000 fffff800`03460000 0x00049000 0x4ce7c669 11/20/2010 9:00:25 PM
fwpkclnt.sys fffff880`01a80000 fffff880`01aca000 0x0004a000 0x4ce79321 11/20/2010 5:21:37 PM
fvevol.sys fffff880`01c00000 fffff880`01c3a000 0x0003a000 0x4ce793b6 11/20/2010 5:24:06 PM
Fs_Rec.sys fffff880`0155a000 fffff880`01564000 0x0000a000 0x4a5bc111 7/14/2009 7:19:45 AM
FLxHCIh.sys fffff880`06ba8000 fffff880`06bbf000 0x00017000 0x4f0bfa5d 1/10/2012 4:44:13 PM
FLxHCIc.sys fffff880`0a933000 fffff880`0a96f000 0x0003c000 0x4f0bfa55 1/10/2012 4:44:05 PM
fltmgr.sys fffff880`011ad000 fffff880`011f9000 0x0004c000 0x4ce7929c 11/20/2010 5:19:24 PM
fileinfo.sys fffff880`00c1a000 fffff880`00c2e000 0x00014000 0x4a5bc481 7/14/2009 7:34:25 AM
fastfat.SYS fffff880`02a00000 fffff880`02a36000 0x00036000 0x4a5bc1f0 7/14/2009 7:23:28 AM
dxgmms1.sys fffff880`107a1000 fffff880`107e7000 0x00046000 0x4ce799c1 11/20/2010 5:49:53 PM
dxgkrnl.sys fffff880`106ad000 fffff880`107a1000 0x000f4000 0x4ce799fa 11/20/2010 5:50:50 PM
Dxapi.sys fffff880`06bbf000 fffff880`06bcb000 0x0000c000 0x4a5bc574 7/14/2009 7:38:28 AM
dump_iaStor.sys fffff880`0467e000 fffff880`047d2000 0x00154000 0x4cd50774 11/6/2010 3:44:52 PM
dump_dumpfve.sys fffff880`06bd9000 fffff880`06bec000 0x00013000 0x4a5bc18f 7/14/2009 7:21:51 AM
drmk.sys fffff880`0648a000 fffff880`064ac000 0x00022000 0x4a5bd8e5 7/14/2009 9:01:25 AM
disk.sys fffff880`01c3a000 fffff880`01c50000 0x00016000 0x4a5bc11d 7/14/2009 7:19:57 AM
discache.sys fffff880`01868000 fffff880`01877000 0x0000f000 0x4a5bc52e 7/14/2009 7:37:18 AM
dfsc.sys fffff880`01bc0000 fffff880`01bde000 0x0001e000 0x4ce79447 11/20/2010 5:26:31 PM
crashdmp.sys fffff880`06bcb000 fffff880`06bd9000 0x0000e000 0x4a5bcabd 7/14/2009 8:01:01 AM
CompositeBus.sys fffff880`055e8000 fffff880`055f8000 0x00010000 0x4ce7a3ed 11/20/2010 6:33:17 PM
compbatt.sys fffff880`00e15000 fffff880`00e1e000 0x00009000 0x4a5bc3b6 7/14/2009 7:31:02 AM
cng.sys fffff880`014d7000 fffff880`01549000 0x00072000 0x4ce79e2d 11/20/2010 6:08:45 PM
CmBatt.sys fffff880`055c4000 fffff880`055c8500 0x00004500 0x4a5bc3b7 7/14/2009 7:31:03 AM
CLFS.SYS fffff880`00cb5000 fffff880`00d13000 0x0005e000 0x4a5bc11d 7/14/2009 7:19:57 AM
CLASSPNP.SYS fffff880`01b6a000 fffff880`01b9a000 0x00030000 0x4ce7929b 11/20/2010 5:19:23 PM
CI.dll fffff880`00d13000 fffff880`00dd3000 0x000c0000 0x4ce7c944 11/20/2010 9:12:36 PM
cdrom.sys fffff880`04600000 fffff880`0462a000 0x0002a000 0x4ce79298 11/20/2010 5:19:20 PM
cdfs.sys fffff880`06655000 fffff880`06672000 0x0001d000 0x4a5bc112 7/14/2009 7:19:46 AM
cdd.dll fffff960`00710000 fffff960`00737000 0x00027000 0x00000000
BTHUSB.sys fffff880`06848000 fffff880`06860000 0x00018000 0x4db8e510 4/28/2011 11:54:56 AM
bthport.sys fffff880`064b2000 fffff880`0653e000 0x0008c000 0x4db8e51b 4/28/2011 11:55:07 AM
bthpan.sys fffff880`0656a000 fffff880`0658a000 0x00020000 0x4a5bcc24 7/14/2009 8:07:00 AM
BthEnum.sys fffff880`068c6000 fffff880`068d6000 0x00010000 0x4a5bcc1c 7/14/2009 8:06:52 AM
btfilter.sys fffff880`06800000 fffff880`06848000 0x00048000 0x4d75c97a 3/8/2011 2:15:22 PM
btath_rcp.sys fffff880`065aa000 fffff880`065cee00 0x00024e00 0x4c22f871 6/24/2010 2:17:21 PM
btath_lwflt.sys fffff880`02baa000 fffff880`02bbd000 0x00013000 0x4c8de04e 9/13/2010 4:26:54 PM
btath_hcrp.sys fffff880`02b38000 fffff880`02b9b000 0x00063000 0x4c29bd43 6/29/2010 5:30:43 PM
btath_flt.sys fffff880`02b9b000 fffff880`02baa000 0x0000f000 0x4c22f882 6/24/2010 2:17:38 PM
btath_bus.sys fffff880`05424000 fffff880`0542f000 0x0000b000 0x4c22f887 6/24/2010 2:17:43 PM
btath_a2dp.sys fffff880`02ad1000 fffff880`02b38000 0x00067000 0x4d59db43 2/15/2011 9:47:47 AM
bowser.sys fffff880`04318000 fffff880`04336000 0x0001e000 0x4d649328 2/23/2011 12:55:04 PM
blbdrive.sys fffff880`01bde000 fffff880`01bef000 0x00011000 0x4a5bc4df 7/14/2009 7:35:59 AM
Beep.SYS fffff880`04d7f000 fffff880`04d86000 0x00007000 0x4a5bca8d 7/14/2009 8:00:13 AM
BATTC.SYS fffff880`00e1e000 fffff880`00e2a000 0x0000c000 0x4a5bc3b5 7/14/2009 7:31:01 AM
atkwmiacpi64.sys fffff880`01bef000 fffff880`01bf8000 0x00009000 0x4e66cc94 9/7/2011 9:44:52 AM
athrx.sys fffff880`0a67c000 fffff880`0a926000 0x002aa000 0x4e8aac79 10/4/2011 2:49:29 PM
ataport.SYS fffff880`0116d000 fffff880`01197000 0x0002a000 0x4ce79293 11/20/2010 5:19:15 PM

kokopuffs
05-29-2012, 03:12 PM
atapi.sys fffff880`01164000 fffff880`0116d000 0x00009000 0x4a5bc113 7/14/2009 7:19:47 AM
ASMMAP64.sys fffff880`03336000 fffff880`0333e000 0x00008000 0x4a4c7a36 7/2/2009 5:13:26 PM
amdxata.sys fffff880`011a2000 fffff880`011ad000 0x0000b000 0x4ba3a3ca 3/20/2010 12:18:18 AM
AgileVpn.sys fffff880`05400000 fffff880`05416000 0x00016000 0x4a5bccf0 7/14/2009 8:10:24 AM
afd.sys fffff880`04c36000 fffff880`04cbf000 0x00089000 0x4db4dd96 4/25/2011 10:33:58 AM
ACPI.sys fffff880`00f53000 fffff880`00faa000 0x00057000 0x4ce79294 11/20/2010 5:19:16 PM
000.fcl fffff880`03231000 fffff880`0325e000 0x0002d000 0x4ce5ca88 11/19/2010 8:53:28 AM

dstrakele
05-29-2012, 04:20 PM
What is the a) Bug Check String, b) Bug Check Code, c) 4 Parameters, and d) filename listed as possible cause for the BSOD?

kokopuffs
05-29-2012, 05:31 PM
What is the a) Bug Check String, b) Bug Check Code, c) 4 Parameters, and d) filename listed as possible cause for the BSOD?

a)DRIVER_POWER_STATE_FAILURE
b)0x0000009f
c)00000000`00000003 fffffa80`09a9e440 fffff800`00b9c3d8 fffffa80`06c329c0
d)NT Kernel & System (?)

dstrakele
05-29-2012, 06:58 PM
What were you doing on the system when this BSOD occurred? Was the system being shut down or entering sleep?

This DRIVER_POWER_STATE_FAILURE BSOD is most likely a software issue. It occurs when a device object has been blocking an IRP (interrupt request packet) for too long a time, typically for 10 minutes. The NT Kernel and System are important Windows 7 files and are most likely victims in this BSOD, rather than the cause. Someone skilled in the use of a debugger could troubleshoot further if you could provide the mini-dump file to them. I've seen this done in the Asus Gaming Notebooks section of Notebook Review Forum.

What 3rd Party Antivirus, AntiMalware, Firewall, Remote Access, or Disk Management software have you installed to your system prior to the BSOD? The drivers in these applications are the ususual suspects in BSOD's and system lockups.

If you have an Atheros WiFi card, be sure its driver is version 9.2.1.432 or later. Earlier versions have high DPC Latency and have caused numerous problems on G74SX systems. See http://rog.asus.com/forum/showthread.php?5126-Any-Kind-of-Lag-and-Atheros-WiFi-Card

cbolin21
05-29-2012, 08:12 PM
Ok I'm not a pro at reading computer code and most of that is just nonsense to me. I do recognize 1 file in all of that. The ntoskrnl.exe file. That was also the main source of my crashes. Here's a way to test your memory and see if that was the cause of the crash. It's called memtest86+ (http://www.memtest.org/#downiso). It takes quite a while to complete the test but it will tell you if there is a fault in your memory. I used the Pre-compiled Bootable ISO (.zip). I can post instructions on how to set-up and run the test if necessary. As for the popping the memory cover off instructions, here's like full disassemble instructions from the guys over at the BTO forum (http://btoforums.com/showthread.php?t=3525). All you really need is the first set of pictures. The removing ODD is past the memory section. Of course this is always good the have at your disposal for a reference.

Hope this helps.

kokopuffs
05-30-2012, 12:35 AM
What were you doing on the system when this BSOD occurred? Was the system being shut down or entering sleep?

This DRIVER_POWER_STATE_FAILURE BSOD is most likely a software issue. It occurs when a device object has been blocking an IRP (interrupt request packet) for too long a time, typically for 10 minutes. The NT Kernel and System are important Windows 7 files and are most likely victims in this BSOD, rather than the cause. Someone skilled in the use of a debugger could troubleshoot further if you could provide the mini-dump file to them. I've seen this done in the Asus Gaming Notebooks section of Notebook Review Forum.

What 3rd Party Antivirus, AntiMalware, Firewall, Remote Access, or Disk Management software have you installed to your system prior to the BSOD? The drivers in these applications are the ususual suspects in BSOD's and system lockups.

If you have an Atheros WiFi card, be sure its driver is version 9.2.1.432 or later. Earlier versions have high DPC Latency and have caused numerous problems on G74SX systems. See http://rog.asus.com/forum/showthread.php?5126-Any-Kind-of-Lag-and-Atheros-WiFi-Card


I just finished updating my kapersky and I was restarting. It was stuck at the "shutting down" screen and suddenly the BSOD appeared.

what should I do now then? Uninstall? I was just also wondering, if I system recover. will it just restore my C drive(OS) back to factory settings or all the partition drives?

kokopuffs
05-30-2012, 12:36 AM
Ok I'm not a pro at reading computer code and most of that is just nonsense to me. I do recognize 1 file in all of that. The ntoskrnl.exe file. That was also the main source of my crashes. Here's a way to test your memory and see if that was the cause of the crash. It's called memtest86+ (http://www.memtest.org/#downiso). It takes quite a while to complete the test but it will tell you if there is a fault in your memory. I used the Pre-compiled Bootable ISO (.zip). I can post instructions on how to set-up and run the test if necessary. As for the popping the memory cover off instructions, here's like full disassemble instructions from the guys over at the BTO forum (http://btoforums.com/showthread.php?t=3525). All you really need is the first set of pictures. The removing ODD is past the memory section. Of course this is always good the have at your disposal for a reference.

Hope this helps.

thanks! I've downloaded the mentioned file, I'll just wait for your instructions now :)

so what you mean is, I'l just pop off the lid, take off my HDDs and put them back in place again?

dstrakele
05-30-2012, 01:52 AM
I don't know what your situation is currently. But if I had just a few days until the retailer's exchange/return period ended, I would perform an ASUS Factory Restore by pressing F9 at the ASUS splash screen and choosing to restore Windows to the 1st partition. Since this completely overwrites the OS partition, be sure to backup any important files you've stored there. It will not touch any other partition.

Then try to reproduce the issues you reported. Disable or Uninstall ASUS Live Update, so it doesn't interfere with your tests. Don't uninstall any other ASUS bloatware.

My G74SX-A1 came with a pre-installed trial of Trend Micro Antivirus already running. If you have the same, uninstall it and REBOOT before you install Kapersky to repro the BSOD on installation.

Install your Black Ops and see if it shuts down correctly.

See if Windows starts up faster.

Do NOT update the video driver and see if you can reproduce any video issues.

If your reproduce any issues and cannot resolve them easily, consider exchanging or returning the laptop.

cbolin21
05-30-2012, 10:23 AM
Ok for the instructions. Since your computer from what I have read on that model has blue-ray you might need to get a blank blue-ray disc. I have no experience with blue-ray what so ever but I'm pretty sure it won't read a DVD style disc. I have a regular ODD in my G74sx so that should be the only difference. If anyone could provide some insight on this it would help. But first when you open the memtest file you downloaded it should open in a disc burning software. Mine opened in Cyberlink Power2go. You need to burn the ISO image to a disc. Once you finish burning the ISO image to a disc you'll need to do a restart. When your computer starts to start up again hit the esc key, (I generally just mash the key once the first Asus screen pops up. The black screen that says Asus Inspiring Innovation Persistent Perfection.)That should pop up with a Boot Device manager. Just select your disc drive as the boot device and it should start the test. I'll include a picture of the boot device manager you should see and the test once it starts. As with any test make sure to have your computer plugged in. (I seem to be having an issue with my image up loader so I'll use links.) Heres the Boot Device Manager (https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-snc7/579253_10150934460194026_544699025_9808665_8488358 70_n.jpg) you should see. Then here is the Memtest (https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-ash3/s720x720/547112_10150934457529026_544699025_9808649_1664421 786_n.jpg) running screen you should see. If those links don't work I will find another way to get those pictures up.

For your Hard Drives you can try to take them out and reseat them. They are simple to remove also your RAM is right there too. I used canned compressed air to blow out the ports of everything.

Wish you the best of luck with the Memory Test.


Ok I checked with a friend of mine who is like an expert of blue-ray and he said a regular DVD disc will work.

brecker
05-30-2012, 03:28 PM
you can always run memstest from a bootable pen drive...

http://www.memtest.org/download/4.20/memtest86+-4.20.usb.installer.zip

TorturedByTech
05-31-2012, 04:00 PM
Another one was when I tried updating my graphic driver, as prompted by the Asus Live Updater. Though I already fixed it, but I guess I should mention it. It restarted my laptop without asking and when it was back on. It was all fat (low resolution) the highest I could go up to was 1280 D: anyway, I uninstalled the entire graphic driver and downloaded it from the asus site.


:(

PLEASE tell me HOW you did this. I got an Asus Update last night/ early morning at 230 am on (5/31/2012). when it finished the screen resolution was, I believe, 800x600. I IMMEDIATELY went to change it back to its original high resolution and the highest it could go was 1280x1024. I can easily tell that this resolution wasn't the one I had the day I left the store with it. I want to say the resolution was much higher like I've seen in others' posts of 1920x1200, I THINK...Whatever the case, the resolution was better than it is now. If you or anyone could assist me with returning it to what it was, and possibly explaining a way to ensure this NEVER happens again. I would be Extremely grateful. This view is so terrible, I can't stand to watch videos, work with Maya or even just use the laptop at all.

btw: I have a Asus G74s: i7-2630QM, 2.0 GHz, 12GB, HDD 500GB + SDD 500GB, nVidia Geforce GTX 560M 3GB

iluvatar
05-31-2012, 04:18 PM
1. Try system restore to a point before the update
2. If that doesn't work download a driver for your card from nvidia and make sure to do a "Clean install"
3. Uninstall asus live update, it does more harm than good and you don't need it

TorturedByTech
05-31-2012, 05:32 PM
THANK YOU SO MUCH!
The system restore worked perfectly in restoring my resolution. It restored to the last critical update which was just a few days ago. Everything is all perfect and pretty and perfect and awesome,...did i mention perfect? Back to the 1920x1080, AND the Screen resolution menu has changed (I'm assuming to its original). It now says Mobile PC Display in the Display Dropdown, instead of the: Standard VG--something-or-other crap. IT also has an Orientaion dropdown that it was missing before. (after the Asus Live Update). All in all it is back to the glorious way i remember it!

NOW, how do I uninstall Asus live Update? I found it in my start menu (Asus Live Update). but I'm afraid to click it, and end up starting it. I right clicked it but it didn't show uninstall on the list. Do i still just click it and it will give me a dialogue box so i can uninstall it, before it tries to update?

Once again THANK YOU

dstrakele
05-31-2012, 06:21 PM
You can uninstall ASUS Live Update from "Start - Control Panel - Uninstall a program".

cbolin21
05-31-2012, 06:37 PM
You can also uninstall the Nvidia update the same way. You should really only update a driver if it will fix a bug that you have.

TorturedByTech
05-31-2012, 07:02 PM
THANK YOU EVERYONE FOR THE ASSISTANCE! When Skynet is active you all are welcome to take refuge in my hidden bunker!

dstrakele
05-31-2012, 10:19 PM
Just watch out... There are reports of G74SX's with 2760 processors and 32 GB's of RAM that have become self-aware...

In fact, it is rumored that @fostert is actually one of these sentient machines!