correct. you won't loose any information.
-
just flashed to the 204 bios (using the asus utility) released on 11/9(i think?), I'll see how the games fare later on tonight/the weekend. good luck to everyone else!
-
they fixed the mem mapping problem, so it should work. ill give it a go eventually.
-
ASUS Customer Care Company Representative
To everyone who has update the BIOS, please post your feedback if it resolved the issue or not. So I can't pass the word along. Thank you.
-
is this a problem only for asus G51 J with windows 7 or does it affect all G51 series laptops?
-
currently playing Dragon Age: Origins, no problem as of yet. will try CA/CoD later tonight.
-
well I just clocked in a few hours with Fallout3 with no bsod yet, I haven't tried turning on the Power4Gear clocking but i guess I'll try later...
-
So nobody had a BSOD after installing the new bios??
Then can somebody link me a tutorial on how to update it??? I have absolutely no idea. -
0) extract bios to C:\
1) f2 at start
2) EZflash
3) using the arrow keys, navigate to the BIOS.rom
4) flash
there isn't much room for error.
played 2 rounds of CA / about two hours on broadcast/crossfire/crash without a problem. will do more over the weekend. -
I currently am waiting for my g51j to come back from RMA in Indiana. It has been there a week on this issue and I have been unable to get any information on its status other than status repairing (which it has been since shortly after recieved on 11/6.) And rate of progress 0.0. When I have called I've been told repeatedly it will be escalated, but then I get told there is nothing on the rma to show it had been. I'm getting kind of frustrated over what should be an easy fix from what I'm hearing.
-
After BIOS update:
BSOD @ Borderlands. I now have a short freeze before the BSOD
MW2 is fine
Fallout 3 is fine
L4D is fine -
-
-
anyone gets BSOD might want to check to see if thermal paste is applied properly on GPU.
-
MW2 is not fine. BSOD, same 124 problem -
-
2009-11-14 03:22:35 , 500.0 , 799.0 , 87.0
2009-11-14 03:22:36 , 500.0 , 799.0 , 87.0
2009-11-14 03:22:37 , 500.0 , 799.0 , 87.0
2009-11-14 03:22:38 , 500.0 , 799.0 , 87.0
2009-11-14 03:22:39 , 500.0 , 799.0 , 87.0
2009-11-14 03:22:41 , 500.0 , 799.0 , 87.0
2009-11-14 03:22:42 , 500.0 , 799.0 , 87.0
2009-11-14 03:22:43 , 500.0 , 799.0 , 87.0
then CRASH. 87.0 should not be fatally high. -
Seems like it works for some people and not others?
Even when I didn't update Bios i didnt get any errors from any games such as L4D and COH.. etc. Only COD4. Will try after updating bios on weekends. -
I just purchased the G51J after months of wait and having the notebook BSOD with an old game like Battlefield 2 just makes it that much more awesome.
The blue screen of death happens for me with the 204 update. -
ASUS Customer Care Company Representative
For those affected by the BSOD, would it be possible to obtain:
DXDIAG LOG
FORCEWARE INFO
or even better maybe a log of system info from Everest.
Thanks. -
-
dxdiag, forceware 191.56, demsg, kern.log, syslog;
the bug is still NOT fixed ->
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
when an engine is set to allocate low memory (anti-cheat, persistent), it will use the above and potentially stop with an uncorrectable fault if the BIOS overwrites anything to cause the checksums to fail.
suggestion for win7 users:
just to confirm there are no other changes in the bios (DSDT tables maybe),
delete this key from registry (regedit) and restart:
[HKEY_LOCAL_MACHINE\HARDWARE\ACPI\DSDT\PEGA\PEGANB\00000001] -> 00000000
if (for whatever reason) it fails to start after doing this (it shouldn't, really) then F8 on start and choose "Last Known Good Config". this will restore the registry to the state it was last shutdown.
that said without actually trying to play for extended periodsswamped with work this weekend but ill see what i can do.
# stuttering still there (3 sec interval, 60 seconds) -> hopefully punkbuster
# i tried taking a screenshot of flying polygons after the chopper crashed, unfortunately i hit F12 too slow -> first time, maybe just chance. by flying polygons, they were sort of like artifacts, but with textures (of the closest surface).
# leaving it on spec (broadcast from roof overlooking outside) while i finish up some programming assignments...
# round to 4k dm on crossfire and no problem.
# 2 rounds on Snow Valley in Combat Arms, no problem.Attached Files:
-
-
Attached Files:
-
-
something i noticed:
- running prime95 (short ffts). all good, temps should reach between 75 and 85.
- HWmonitor Powers should show 55W, check.
- TMonitor shows clocks at 1.7 (?)
- running furmark (1440x900 windowed, 4xAA, xtreme burn, stress)
^ CPU drops to 933MHz and 15W when furmark starts rendering. temps for the CPU start to drop to 60-ish. pause rendering, shoots back to 55W/1.6G.
if theres something else i can use to monitor, im all ears, but it seems the laptop just doesnt have enough juice. could potentially be a reason for the BSOD. if only i had a watt meter handy...
running a quick oc to 550/950/1375,
- Dragon Age actually gets worse due the CPU going down. luckily this doesnt happen on stock. still, it shouldn't happen at all.
had more than my usual daily dose of CoD4, no bsod. could've just been luck, but the fact that CA also went smooth convinces me otherwise.
imo, customers shouldn't be beta testers, but ill try and help with anything i can (given Asus CC doesn't ignore my posts for not being a US customer (Canada IS close enough))
attached DxDiag/forceware for winXP (the last post was win7)Attached Files:
-
-
Update:
Crysis ran fine on high settings without BSOD while Battlefield 2 continues to give BSOD. -
Combat Arms BSOD'd at the end of the day, 2 minutes in.
-
My dxdiag.txt here:
Attached Files:
-
-
I update to 204 about played MW2 for about 30min, then my computer froze. It was not BSOD, but the game not responding. might be another problem due to new bio. I don't know.
-
freezing would also be related; drivers crashing would not
-
hmm so what is it that would make the G51 J get BSOD while the VX variants dont? is there something software wise causing this or is it the G51J's hardware components?
-
Is it only certain games that are getting BSOD? I'm a little worried since I should be getting mine soon and I really need it for school.
-
-
.
-
I just thought of something...might be relevant and might not, but it's worth mentioning I suppose.
How many of you guys are using the mouse that came with the laptop? (Copperhead is the model name I think)
Reason I ask is because i have the same mouse and I started using it on my G2S-2B after I bought a Sidewinder X8 for my desktop. Well...my laptop would start locking up and giving me BSOD just about every time I played a game and used the mouse. But the only game that I play is WoW...so maybe it would have been worse with more demanding games...dunno. So anyway, I ordered another Sidewinder X8 for my laptop since I love how it performs.....stopped using the Copperhead and removed all drivers for it and haven't had a single problem since I got it. -
copperhead drivers give a BSOD on xp and 7. difference being is that was an e0 driver stop, this is a 124 hardware. i tried with nothing plugged in and CA bluescreens regardless.
LAN and wireless are different as well.
xp is not affected either. -
I'm thinking this has something to do with the new Core i7 and Turbo Boost control of how many cores to use depeneding on the task.
-
I had the microsoft sidewinder mouse when i played my games on this laptop before... but i soon changed to the copper head mouse that came with the laptop but still gets the BSOD.
-
This is the first time I'm hearing about problems with the mouse.
Anyway, I just saw this:
http://www.razersupport.com/windows7/razer-windows-7/
Seems like the copperhead won't have windows 7 support until around Thursday. It also says you should be able to use the mouse without their drivers. -
don't think it's razor, I'm using razor and I haven't gotten any BSOD.
Today I played, MW2 and borderland. No problem at all. -
A game like Crysis runs fine for I and another member of NBR without a BSOD while a list of other games give BSOD's. So this only suggests that the problem is not cause of hardware strain (lack of power or overheating) since Crysis is as demanding as it gets, but maybe an issue with perhaps the turbo boost feature of the new Core i7 being incompatible with some games. At this point in my opinion, the signs point towards the CPU and not the GPU since the G51vx also has the same GPU and doesn't suffer from the same issue.
-
Soviet Sunrise Notebook Prophet
I will test this theory once I get my notebook up and running.
-
-
Hers a quote from another G51J-A1 owner:
-
In Borderland, I set everything to high and use native 1920x1080 resolution. No AA -
afaik, XP and 7 handle single-threaded applications more or less the same way... there's only one thread. i can play borderlands, cod4, mw2/sp and all the other games without issues on XP.
i'm 90% certain that the crashing on 7 is because of bad mem assignments from the BIOS (which is still there in 204).
if someone can, try the below.
-
wow...the bios is causing this many problems?!?
i sure feel happy that i DIDNT wait to buy a notebook, i got my G51Vx-A1 for 1252USD as wellim happy with ma C2Q @ 2.4GHz, if the i7 notebook is causing this much problems, why would i ever want it?
-
I'm sure if it's just a BIOS issue that asus will get it figured out rather quickly and fix it for us. Quite positive they're not going to let this go for too much longer. At least that's what I'm hoping....lol
-
-
I tried Borderlands (BSOD), MW2 (BSOD), L4D (okay), Fallout3 (okay).
I am using Mamba, not the copperhead, though. -
G51j Blue screen of death problems
Discussion in 'ASUS Gaming Notebook Forum' started by Dragokld, Oct 31, 2009.