G51j Blue screen of death problems

[sama98b]

OK There.........

Dude I've yet to see a constructive post from you, and please stop with the " :P " , you use it so much I'm starting to think its being substituted for punctuation.

I didn't see from you either
Guess not going to go over 10000-s of useless pages to find 1 useful.
I read whatever I want and write whatever I feel like, this is the internet not usa :P

Just watching over the topic if I ever run in to bsod know what is the problem.
No bsod til now.

There was 0 clue pointing to nvidia til someone try to blame it on them ...
And lol Sefam .. none of my comments were about you

ps.: already wrote a comment that there should be a different topic with only raw data where ppl get bsod/crash without discussion, and keep this a bla bla.

ps.: 2h ingame and bsod then .. look to parts that don't run hot from the start but getting heated up with time but they usually run cold ..

ps.3.:just lost 10 years of mp3 collection thanks to seagate .. 2 hdd craping out and 3 on the way to there, so guess how #% I am.

ps.4: I had asus a2k notebook with x64 compatible cpu .. asus never releases bios that would have supported x64 win .. finally the display broke down due material failure .. still wasn't that pisses to asus as a few ppl here because random bsod :P

[Sefam]

Sorry then.

And as I said, my G51J already had the 204 BIOS on it, so I suppose my laptop is not from the first batch. Yet it occasionally get the same BSOD than you guys.

[ALLurGroceries]

This has always seemed to be a low level problem, so here is some stuff for anyone else who wants to dig.

There are a number of potential problems in the DSDT:

$ iasl -tc dsdt.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20090521 [Jun 14 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a

dsdt.dsl 13831:         Method (KPTS, 1, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (KPTS)

dsdt.dsl 13847:         Method (KWAK, 1, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (KWAK)

dsdt.dsl 13880:         Method (_Q0C, 0, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (_Q0C)

dsdt.dsl 13909:         Method (_Q0D, 0, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (_Q0D)

dsdt.dsl 16623:         Method (MF42, 4, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (MF42)

dsdt.dsl 17637:                     And (CTRL, 0x1E)
Warning  1105 -                             ^ Result is not used, operator has no effect

dsdt.dsl 18059:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18073:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18088:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18103:             Acquire (MUTE, 0x0FFF)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18117:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18132:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18147:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

ASL Input:  dsdt.dsl - 18619 lines, 524548 bytes, 7511 keywords
AML Output: dsdt.aml - 63003 bytes, 1897 named objects, 5614 executable opcodes

Compilation complete. 0 Errors, 13 Warnings, 0 Remarks, 2603 Optimizations

dmidecode says the x16 slot is out of spec, not sure if this is true:

Handle 0x0019, DMI type 9, 17 bytes
System Slot Information
	Designation: J5C1
	Type: x16 <OUT OF SPEC>
	Current Usage: In Use
	Length: Long
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported

Does anyone know the EC chip used in the G51J? I don't know of an existing teardown or disassembly and I'm reluctant to rip it apart myself to read the chip.

A problem somewhere between the EC and the BIOS would seem to at least be possible.

[thalanix]

This has always seemed to be a low level problem, so here is some stuff for anyone else who wants to dig.

There are a number of potential problems in the DSDT:

$ iasl -tc dsdt.dsl

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20090521 [Jun 14 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a

dsdt.dsl 13831:         Method (KPTS, 1, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (KPTS)

dsdt.dsl 13847:         Method (KWAK, 1, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (KWAK)

dsdt.dsl 13880:         Method (_Q0C, 0, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (_Q0C)

dsdt.dsl 13909:         Method (_Q0D, 0, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (_Q0D)

dsdt.dsl 16623:         Method (MF42, 4, NotSerialized)
Warning  1087 -                    ^ Not all control paths return a value (MF42)

dsdt.dsl 17637:                     And (CTRL, 0x1E)
Warning  1105 -                             ^ Result is not used, operator has no effect

dsdt.dsl 18059:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18073:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18088:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18103:             Acquire (MUTE, 0x0FFF)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18117:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18132:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

dsdt.dsl 18147:             Acquire (MUTE, 0x03E8)
Warning  1104 -                                 ^ Possible operator timeout is ignored

ASL Input:  dsdt.dsl - 18619 lines, 524548 bytes, 7511 keywords
AML Output: dsdt.aml - 63003 bytes, 1897 named objects, 5614 executable opcodes

Compilation complete. 0 Errors, 13 Warnings, 0 Remarks, 2603 Optimizations

dmidecode says the x16 slot is out of spec, not sure if this is true:

Handle 0x0019, DMI type 9, 17 bytes
System Slot Information
	Designation: J5C1
	Type: x16 <OUT OF SPEC>
	Current Usage: In Use
	Length: Long
	Characteristics:
		3.3 V is provided
		Opening is shared
		PME signal is supported

Does anyone know the EC chip used in the G51J? I don't know of an existing teardown or disassembly and I'm reluctant to rip it apart myself to read the chip.

A problem somewhere between the EC and the BIOS would seem to at least be possible.

compress and attach the disassembled DSDT, i need something to do in my spare time (being down a laptop). as for the EC error, xp shows the same as reported on page 2/post 12, which would make sense with all those MUTEs.

[ALLurGroceries]

compress and attach the disassembled DSDT, i need something to do in my spare time (being down a laptop). as for the EC error, xp shows the same as reported on page 2/post 12, which would make sense with all those MUTEs.

k, here 'tis:

http://allurgroceries.com/g51ja1dsdt.zip

Edit: HPET write failures?!

Dec 15 19:50:25 g51j kernel: [    1.776712] rtc0: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
Dec 15 19:50:25 g51j kernel: [    3.029128] WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x4f/0x72()
Dec 15 19:50:25 g51j kernel: [    3.032352]  [] ? hpet_next_event+0x4f/0x72

[thalanix]

thanks.
"You must spread some Reputation around before giving it to ALLurGroceries again."
i tried.

Edit: HPET write failures?!

Dec 15 19:50:25 g51j kernel: [    1.776712] rtc0: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
Dec 15 19:50:25 g51j kernel: [    3.029128] WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x4f/0x72()
Dec 15 19:50:25 g51j kernel: [    3.032352]  [] ? hpet_next_event+0x4f/0x72

kmsg from the default ubuntu 9.10 kernel > http://forum.notebookreview.com/show...01#post5517801
no event timer errors there.


edit: the stuttering in CoD4 on joining a MP map seems to be related to the BSoD issue. i copied over the setup 1:1 (Steam and punkbuster) to my temporary crapsicle desktop and there is NO stuttering.

[ALLurGroceries]

Yeh it's the first time I've seen it, I'm on 2.6.32.1 right now, just about to build .33-rc1, you were on .31-something it looks like. I did find this:
http://groups.google.com/group/linux...fb39d?lnk=raot

Looks like it's related to turbo mode, so I know that isn't directly relevant to the BSoD (since ppl get it without turbo on).

Oh yes I get that stutter too, sometimes just in the menu. Although it seems to be directly related to HDD activity. Once that clears up it doesn't stutter at all for me.

[thalanix]

never happened on our old G50s, and those were 5400 drives. it clears up after a minute or two, and sometimes comes back in the middle of a round (in which case i find a corner to sit in and get a drink).

ive tried on both win7 and xp on the desktop, nothing.

i take it you compiled cpufreqd into the kernel instead of a module? that could explain why.

[ALLurGroceries]

Neh, it's a module. But it's in the initramfs. As far as I know it's not a real problem after reading that thread I linked to above. I'm looking at everything I can though, since this is starting to get aggravating having to read this thread every day.

Edit: Also, has anyone had problems with an external USB keyboard in CODMW2? Sometimes it will die on me and I have to hold ESC for a massively long time... and the one time I got the BSOD it happened about 10 seconds after that happened.

[thalanix]

installing XP with only SATA/LAN/Video/CoD/whatever's required on its own 30GB partition will take quicker than reading through this thread alone. it'll even run a solid 5-10% quicker

that was the only way i found CoD to be stable, with the exception of more frequent crashes (one every 5-10 hours, no more than 1 per day).