[SOLVED] Asus G51J BSoD thread - part 2

No.

If it messes up your laptop is screwed. It will need to be serviced and possibly the motherboard replaced (out of warranty this is a very expensive thing!)

That's why you don't stuff around when updating BIOS, you do it on a clean boot with nothing plugged in except AC with as many background programs closed. You don't touch your computer until it's done. You reboot immediately.

Chances of something stuffing up are very low, but they are still there if you don't do it properly.

 

^ That's great advice!

Probably doing it during a thunderstorm isn't a super great idea either :lol:

 

Hi, I've been having problems with the bsod for a while now and factory rebooting has been of no use. I've read about this problem and the GenTech bios update and I would like to upgrade my bios but i have some doubts.

1- What files do I need to download? The GenTech 207.T10, the official 208, or both?
2- With the WinFlash program, is it just selecting the update file and waiting for it to load?
3- Would I lose any data from my hard disk?

Thank you

 

Hi guys!

I just wanted to say thank you, because you gave me a solution for the BSoD-problem of my G60J. I will try it immediately when I get home. What I learned is that obviously meanwhile the 208 Bios will work as well - which I would prefer because it is officially released and I don't really would want to lose my guarantee.

But there is one thing which I don't really understand. I was playing e.g. Battlefield 2 for a long time without any BSoD - now i have them. Has anyone an explanation why it came so suddenly?

 

If you are able to play Battlefield 2 without BSOD for a long time and just got BSOD recently then it most likely not BIOS related issues unless more people report with same issue.

 

Well it is the same 124 error as far as I see. The only difference might be, that now I got internet in my apartment and play MP and get BSoD, while earlier it was only SP without BSoD. No idea if this makes the difference.

Oh btw... it was you who managed to solve the problem as GenTechPC, right? Then thanks especially to you (if the Bios-Update works in my case) )

 

Hi, Is there an official BIOS from Gentech to fix BSODS problem in Asus G51jx-x5??

 

Could be Steam issue or faulty memory, you can try remove one stick of RAM to check.

Try BIOS 208:

http://dlcdnet.asus.com/pub/ASUS/nb/G60Jx/G60JXAS208.zip

 

Thanks for quick answer, but I have already instaled ver208 2 days ago and it generates BSODS after few mins playing in anything, (is this the same version BIOS as it is on ASUS official website with drivers?)
Also I tried diffrent versions of nvidia card - with no luck,

Here is some info from the event viewer:

This message generates very often, can only think that is about graphics hardware problem( DEVICE ID 0xd138 is Intel(R) processor PCI Express Root Port 1 - D138 driver) I found it in device manager and could not update the driver which is from 06.2006

1

corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus evice:Function: 0x0:0x3:0x0
Vendor ID evice ID: 0x8086:0xd138
Class Code: 0x30400


2

LMS Service cannot connect to Intel(R) MEI driver


3


KERNEL POWER 41 (63)

The system has rebooted without cleanly shutting down first. This error could be
caused if the system stopped responding, crashed, or lost power unexpectedly.

 

Good Morning (at least here it is)

Well I updated to 208 yesterday and so far it seems to work, I knock on wood. This Steam issue could possibly be a factor, as I had a Steam installation for a previous game. I uninstalled it before updating, because it was of no use anymore. Who knows.

But as very rarely the same BSoD came in GTA IV too, the Bios Update was surely a good idea. Both Games are mentioned in this Wiki.

 

@mopas001

The 0x124 BSOD is usually extremely sporadic, not something you'd get after a couple minutes consistently. It looks like you do have some sort of problem with your graphics drivers, but I'm not sure it's related to 0x124. You might want to try a complete uninstall of NVIDIA, a reboot, maybe a driver sweep, and then try a version you knew was stable.

 

at least its good to see that there are some solutions available, but sad that not in my case... Ihave contacted the RMA to get it fixed as its still on waranty.... hope so, as there was a little problem with the USB socket.... a small piece of plastic fell out of the USB socket and the naked wires were easy to bend where short circuit could occur, Ihave filled in the socket by non con-conducting glue to prevent a damage.... I didnt want to send it to RMA as I needed the notebook to work. Just hope that I will not lose warranty....

I wouldn't recommend this laptop to anyone, as even the company don't know how to fix these problems. For this money its a piece of crap, nothing else...

to ALLurGroceries

now when I updatedo to 208 ver. It doesnt show taht its a 0x124 BSOD, it shows blue screen and nothing much more... even when its set to do not reset after BSOD. To be honest I think it is some of the chipset driver the WHEA LOGGER 0x138d but here my computer knowladge ends....

 

@mopas001, hard to give you any advice if you don't have a stop code for the new BSOD you are getting, but if you suspect a chipset issue, you can get the latest from intel and then force install it.

http://forum.notebookreview.com/asu...how-install-latest-intel-chipset-drivers.html

 

Today I am sending laptop to RMA, will se what they will do about it. Thanks for all good advices but even the intel chipset drivers are not solving the problem. It goes from IE to UK... hope that I wont have to wait too long.

 

i was thinking maybe it will work if I downgrade BIOS from 208 to 206, most users recomend to use 206 as the BSOD stopped, RMA didn't fix the problem

 

mopas001, the 208 bios or the beta 207 BIOS are the ones that solved the BSOD. Anything earlier than that will be prone to 0x124 BSODs. If the RMA didn't fix your problem, you might want to rule out a software issue. Maybe a clean install is worth the effort...

 

Well to give a little feedback - no BSoD so far, so solved for me too! THX.

 

Got the lappy back from RMA, didnt fixed as they didn't see a problem, maybe is about to update the chipset driver, but to be honest, I can't understand anything from
http://forum.notebookreview.com/asus-gaming-notebook-forum/asus...t-drivers.html . I've done a clean instal and in event viewer I got plenty messages WHEA-LOGGER 17 a corrected hardware error has occured

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus evice:Function: 0x0:0x3:0x0
Vendor ID evice ID: 0x8086:0xd138
Class Code: 0x30400

as far as I can see it is about the graphics problem, I uninstalled old version of nvidia soft and got 266.58 + 6.06 nvidia system tools, will treat it by 3Dmark06 and post the results later on. Will try the 258.96 nvidia drivers as some peolpe reporting that it was stable

 

Hi everyone, seems im abit late with my bsod problems but I started Battlefield bad company 2 yesterday on my ASUS G51j and went looking how to solve the problem. Everywhere I surf I read that the gentech 207.t10 will fix the problem. But how to get it, seems its not downloadable anymore.

Please help, thanks !!

Max

 

The official 208 bios is listed in the first post on page 1. That is the BIOS you want. It can also be found here: ASUSTeK Computer Inc. -Support- Drivers and Download G51J

The GenTech 207.t10 was a beta bios.

If you have never updated the BIOS before please make sure to read http://forum.notebookreview.com/asus/174395-bios-update-guide-asus-notebooks.html

 

I'm still having BSOD occasionally. It never happened while gaming, it happens sometimes while awaking from hibernation, simply browsing or watching a video. I can't reproduce it. I have the original Razer mouse connected at all times. Model is G51J-A1. What I did:

-> updated BIOS to 208 and 207.T10;
-> a clean install of Windows 7;
-> memory check and disk check, both are normal.

Here are the latest crash dumps. Any ideas?


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 24/08/2011 02:56:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082411-32541-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8003762730, 0xFFFFFA80037632A0, 0xCB7B548)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 24/08/2011 02:56:42 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8003762730, 0xFFFFFA80037632A0, 0xCB7B548)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/08/2011 00:50:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081111-28704-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA20A2)
Bugcheck code: 0x24 (0x70F95, 0x10, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 07/08/2011 18:52:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080711-28454-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800C91A8D8, 0xFFFFF8800C91A130, 0xFFFFF8800129E027)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 04/08/2011 01:46:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080311-21450-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80068A5F40, 0xFFFFFA80068A6CC0, 0x5D83728)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 03/08/2011 20:10:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080311-24663-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800CA0D8D8, 0xFFFFF8800CA0D130, 0xFFFFF880014F1027)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 01/08/2011 00:39:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073111-32073-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E346EA, 0xFFFFF880065B7040, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 22/07/2011 02:39:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-23774-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80068F9DF0, 0xFFFFFA80068FA630, 0xC84E218)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 21/07/2011 22:13:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-23743-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880035468D8, 0xFFFFF88003546130, 0xFFFFF880012CE027)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 19/07/2011 12:54:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071911-27580-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80068BEEC0, 0xFFFFFA80068BFB50, 0x5C92778)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 06/07/2011 03:44:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070611-24507-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x14F50)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80067F6DF0, 0xFFFFFA80067F7D40, 0x5F5F1B8)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.