Dell e1505 Intel core duo T2500 Power BSOD

[Jeff]

Hi,
Getting a power BSOD on Dell e1505 w/Intel core duo T2500 whenever I
unplug from ac power.
Upon exhaustive research; it now appears that someone MISSED this very
important function; in the rc1 tree;altogether!!
Starting with the rc1 branch build 5536;and subsequent builds;including
RC1;a MAJOR ACPI power BSOD whenever this laptop is unplugged from ac
power.

To research this; I uninstalled/reformatted and installed various o.s.'s. No
problems.
this includes XP; Linux; and PRE-RC1 tree;builds. Build 5384/Beta 2 ; build
5472; do not exhibit this behavior; they in fact;work great.

I'm no coder;by any stretch of the imagination;however; one would assume
that the people involved;would have at least caught this before a public RC1
release.
Poor Dell; first the battery recall;now this!!!
Anyone else getting this?
Or am I the lucky Dell e1505 dual core?
Jeff

 

[Guest]

I have the same PC with the same problem, however I've found a partial
work-around. Go into the BIOS and take your pick at turning off either Dual
Core Function, Or Speedstep. I would STRONGLY suggest leaving dual core and
and turning speedstep off however if you REALLY need that battery life and
don't care about speed turn off dual core. Either will make it work. I sure
hope Microsoft fixes this issue in the next build, I've submitted an error
report

have fun!

 

[Jeff]

Thanks,
Leaving them alone; but thanks for the heads up.
Shouldn't have to do this;in the 1st place!!! I mean; Really;RC1????
:
Worked fine before; Oh I reported it also;through feedback;and through
WER(Windows Error Reporting)
Hopefully; it'll be a Windows update patch;like YESTERDAY!!!!

Amazed however;that it's gone through multiple builds in the RC1
branch(most internal;but 1 other one-5536;public;and it wasn't
either'\;caught;or if it was;addressed)
Jeff
P.S. Thanks Again for the workaround.

 

[Lang Murphy]

I'm writing this on a Dell Latitude D620 with a T2400 Duo Core CPU. I have
not experienced this problem at all and I plug/unplug this seat a number of
times every day. Could be a BIOS issue... could be a Vista issue... time'll
tell.

Lang

 

[Jeff]

No Lang;

That's where you are mistaken. It is NOT a bios issue; and it most
DEFINITELY is a Vista coding issue.
If you had taken the time to read my post; you would clearly see;that
although there are variables involved; one is constant;i.e the hardware; no
where did I state that the bios had changed.
And in fact; the only variable that did change; was the o.s.build.
Furthermore; I stated a Specific Dell model; and no where did I hint;or
infer that this was a general laptop issue.
And upon further reading; you would have noticed;that this issue was
absent in builds prior to the rc1 branch.
So; No Lang; time will not tell. It's definitely a Vista build issue.

Jeff

 

[Guest]

Yes I totally agree it is a vista issue this should not be happening this
late in the Vista scene. Although I am running vista primary, it is making me
think it'd be a great FREE os like linux but there is no way I'm paying for
this. It should be a $20 upgrade to xp thats all it really is, a little
faster and a really neat GUI.

I'd say within a month it will be fixed because with RC1 they get TONS of
feedback and this will be common.

 

[Lang Murphy]

Chill out, dude. I did read your post. Don't know why you're flaming me for
trying to help you. Go jump off a bridge.

Lang

 

[Jeff]

Nah Lang, No thanks;
Maybe ya need to chill urself.
Sorry to be a tad testy; just that MSFT screwed up bad; and ppl in here
just assume that its never msft.
Dont\'t take offense;
And if ya did; oh well
Jeff

 

[Lang Murphy]

OK, back to civility...

SuperGeek replied to you that he/she had the same laptop with the same
problem. I responded that I had a different laptop without the problem.
SuperGeek said he/she found a work around by making changes in the BIOS.

Hmmm... see a thread here? I'm just trying to address the problem. I'm not
an MS cheerleader.

Surely BIOS's have problems, otherwise, all Dell BIOS's would stay at A01.
It may just be that the BIOS for the E1505 needs to be updated to work with
Vista RC1. If it were a problem soley with Vista, then every laptop would
exhibit the problem, methinks. The OS works in conjunction with the BIOS to
allow certain stuff to work. I don't know that either one of us can say
beyond doubt that it's one or the other, but it seems to me that they're out
of sync on the E1505. Take that feedback as you will.

Lang

 

[Jeff]

Lang,
O.k.
The BIOS did not change is all I'm saying.
And that being said; what did change; is the o.s.
Seeing as older builds code worked fine with the current e1505 BIOS, I'm
going with the o.s.
You are correct;they need to be in sync to work correctly;that's what the
ACPI guidelines are all about. Power BSOD's are way crucial;or a standard
would not have been put in place to begin with.
And although Supergeek found a workaround; he shouldn't have to.
..
And; just the fact that; it was quite functional before the rc1
builds;leads me to be strongly suspicious;that someone left out .inf
coding;that was in preRC1 builds;but through;either; unintentional
omission;or a plain just not proofing the code before release; it's no
longer there.
As further follow up;on my part has shown; WER immediately saw this as
an issue. In fact; not more than an hour went by before my machine reported
back;that this situation was being investigated.

Which is heartening to know;that at least MSFT is now investigating it.
And I stand by my first assumption;that it is an o.s. issue.
As to cheerleading;
Never said ya were; just allot of people in these ng's truly think MSFT is
correct;and it's the OEM's and 3rd party vendors who are the root of
problems.
Sometimes; as I suspect this issue is; it's a MSFT issue.
Then again; things don't function standalone;they work in conjunction with
one another. Either way; I'm sticking with my first suspicion; this one lies
in the o.s.
That's all.

Jeff

 

[Guest]

OK, first forget everything about people offending each other, we are trying
to help each other.

I agree it is partially the OS's fault because it did work with previous
builds + XP however I also believe a BIOS update could make it WORK with this
version of vista. It's kinda like they are both just 'incompatible' and a fix
to either one could solve the problem. I'm confident msft can fix this one
(and i'm not a microsoft cheerleader infact i wish they'd just stick to xp)
however if they can't Dell will.

 

[Jeff]

Super;
We're over it.
True; both need to work together. But strange how that bios did work with
older builds.
Jeff

 

[Guest]

Yep, I got it too.

Just a brand spanking new Dell T5500 (1.66GHz Core 2 Duo). For whatever
reason, it just gives me the BSOD. I'm not adjusting the bios on this one
simply because I need both the battery longevity and the power of the core 2
duo. (Got to give the indexing service one of the sides of the CPU )

Has anyone seen a post from a MS guy about this? Work arounds besides
shutting off the new features that I bought this laptop for?