SD (Secure Digital) Causes Blue Screen in Vista x64
 

To whom it may concern:

I have an Acer 5102 WLMi Notebook, which came with an
(ENE CB 712/714/810) “5-in-1” Memory Card Reader. The
important identifying information is provided below:

Acer Aspire 5102WLMi (w/o Bluetooth, Orbicam, or TV Tuner)
Model No: BL51
AS5102WLMI-MCEEN-TL50/15.4
ACB/512M/100G US
S/N: LXABH0J0116380F0B41601

The system came with Windows XP Media Center Edition loaded and I have
upgraded the OS to Vista x64, thereby voiding the warranty. Vista x64
works very well; but when I try to install an SD card, Windows
“Plug & Play” will reach various stages of installing the
driver software before crashing with a Blue Screen, where the video is
also scrambled, so it’s impossible to read the error message. This
looks a lot like a "short-circuit" to me. My card reader was only
designed to support SDA 1.1, which supports SD Cards up to 2GB. I used
the correct card. I used a "SanDisk Extreme III 2GB SD Card," which
I’m reasonably confident is not SDHC, so my unit, which was
manufactured in November 2006, should be able to read it. I’ve
read several online Blogs regarding SD cards causing BSODs in Vista. The
articles point to 1.8v & 3.3v being activated when SD cards only use
3.3v. The symptoms are looking an awful lot to me like one of the
system’s logic voltages is being pulled low, causing the OS Kernel
to stop working. I have the related Hotfix from Microsoft installed; but
I’m still having problems. It’s possible my Card Reader is
bad, or perhaps I purchased a defective SD card. These are also
possibilities. I would like to get this unit functioning properly under
Vista x64, preferably with SDHC support. I have the correct drivers
installed for this OS and Device Manager states “the device is
working properly.” If I cannot get the device working properly, I
would like to upgrade the internal Memory Card reader with one that is
known to be compatible with Vista x64. I realize this will probably
involve making changes to the motherboard; but I'm sure there is a
vendor out there somewhere knowledgeable enough and willing to do this.


Thanks, John


--
coljohnhannibalsmith

SD (Secure Digital) Causes Blue Screen in Vista x64
 

not sure this will help, but see
ftp://ftp.support.acer-euro.com/notebook/vista_64bit/

On Fri, 12 Oct 2007 13:41:49 -0500, coljohnhannibalsmith
wrote:


To whom it may concern:

I have an Acer 5102 WLMi Notebook, which came with an
(ENE CB 712/714/810) “5-in-1” Memory Card Reader. The
important identifying information is provided below:

Acer Aspire 5102WLMi (w/o Bluetooth, Orbicam, or TV Tuner)
Model No: BL51
AS5102WLMI-MCEEN-TL50/15.4
ACB/512M/100G US
S/N: LXABH0J0116380F0B41601

The system came with Windows XP Media Center Edition loaded and I have
upgraded the OS to Vista x64, thereby voiding the warranty. Vista x64
works very well; but when I try to install an SD card, Windows
“Plug & Play” will reach various stages of installing the
driver software before crashing with a Blue Screen, where the video is
also scrambled, so it’s impossible to read the error message. This
looks a lot like a "short-circuit" to me. My card reader was only
designed to support SDA 1.1, which supports SD Cards up to 2GB. I used
the correct card. I used a "SanDisk Extreme III 2GB SD Card," which
I’m reasonably confident is not SDHC, so my unit, which was
manufactured in November 2006, should be able to read it. I’ve
read several online Blogs regarding SD cards causing BSODs in Vista. The
articles point to 1.8v & 3.3v being activated when SD cards only use
3.3v. The symptoms are looking an awful lot to me like one of the
system’s logic voltages is being pulled low, causing the OS Kernel
to stop working. I have the related Hotfix from Microsoft installed; but
I’m still having problems. It’s possible my Card Reader is
bad, or perhaps I purchased a defective SD card. These are also
possibilities. I would like to get this unit functioning properly under
Vista x64, preferably with SDHC support. I have the correct drivers
installed for this OS and Device Manager states “the device is
working properly.” If I cannot get the device working properly, I
would like to upgrade the internal Memory Card reader with one that is
known to be compatible with Vista x64. I realize this will probably
involve making changes to the motherboard; but I'm sure there is a
vendor out there somewhere knowledgeable enough and willing to do this.


Thanks, John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Barb,


Thanks, for the reply. I checked out the ftp site. None of the
folders listed my system and most were empty; however, undetered I
checked each folder's contents individually and found the following file
"CardReader_ENE_v3.00.04.zip," in one of the folders near the very
bottom. This is the same Card Reader I use on my machine and looks like
the same file that's on the "AcerPanAm" site, listed under the Aspire
5100 drivers folder simply as "Vista," not Vista x64; however I have
verified that the extracted files from the AcerPamAm site do have x64
folders.

But the installer doesn't work in Vista x64. I had to drill down
alternatively to either the "x64 Cardbus," or "x64 Card Reader" folders
and install the drivers from Device Manager. When I did this they
installed correctly and Device Manager reports all the various
components of the device as working properly; but it still doesn't work.
It may not be a problem with the drivers, it could be with Vista
itself.

I am going to copy the extracted files to my flash drive and compare
them to what I have at home. If the drivers are different, I'll try
installing them and let you know what happened.

Nice detective work!


Thanks, John


--
coljohnhannibalsmith

SD (Secure Digital) Causes Blue Screen in Vista x64
 

thanks for the update.

On Fri, 12 Oct 2007 15:43:13 -0500, coljohnhannibalsmith
wrote:


Barb,


Thanks, for the reply. I checked out the ftp site. None of the
folders listed my system and most were empty; however, undetered I
checked each folder's contents individually and found the following file
"CardReader_ENE_v3.00.04.zip," in one of the folders near the very
bottom. This is the same Card Reader I use on my machine and looks like
the same file that's on the "AcerPanAm" site, listed under the Aspire
5100 drivers folder simply as "Vista," not Vista x64; however I have
verified that the extracted files from the AcerPamAm site do have x64
folders.

But the installer doesn't work in Vista x64. I had to drill down
alternatively to either the "x64 Cardbus," or "x64 Card Reader" folders
and install the drivers from Device Manager. When I did this they
installed correctly and Device Manager reports all the various
components of the device as working properly; but it still doesn't work.
It may not be a problem with the drivers, it could be with Vista
itself.

I am going to copy the extracted files to my flash drive and compare
them to what I have at home. If the drivers are different, I'll try
installing them and let you know what happened.

Nice detective work!


Thanks, John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Barb,

I located the driver file in the "Travelmate 6292" folder. It was also
located in one or two others. The drivers loaded successfully, then I
was prompted to restart the computer, which I did. I installed the SD
card and was prompted to format it. The screen went blank and came back
on. I then got a window stating that Windows had shut down; but I was
able to close that window and press "OK" to start the format. The
format proceeded for about a minute, then I got a Blue Screen again,
with scrambled video, just like before. I removed the SD card and
performed a cold boot to reload Windows. When Windows reloaded I got
the following error message:

Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000003452
BCP2: 00000000001E0000
BCP3: FFFFF70000081508
BCP4: 0000000000000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini101207-02.dmp
C:\Users\John\AppData\Local\Temp\WER-41890-0.sysdata.xml
C:\Users\John\AppData\Local\Temp\WERDBD9.tmp.versi on.txt

Read our privacy statement:
'Microsoft Online Crash Analysis'
(http://go.microsoft.com/fwlink/?link...3&clcid=0x0409)


I tried one more time with similar results.


BTW, I finally read the release notes for the previous drivers I was
using and for the new drivers. It appears the drivers I was using
before were for XP x64. Oddly enough, I was able to install these
through Device Manager. At least this set was intended for Vista x64.
I also learned from reading the release notes, that this set of drivers
is intended to provide SDHC support. My card reader's still not
working; but at least I know that my card reader can be updated for SDHC
support, by drivers alone. Perhaps a Hotfix or a driver tweak will
allow me to get the reader working. Fortunately, I don't think I'm
going to need to modify the mother board anymore.

I have an active "Paid" trouble ticket open with Microsoft for this
issue. If they provide me with a resolution, I will share it with all
of you.

I'm really at a loss for what to try next. I'm pretty sure the drivers
are correct. This is looking more and more like a Vista issue. I'm
wondering if I should try a different brand of SD card, or just wait to
hear back from MS. I'm also wondering how to "tweak" a driver. Device
Manager states these drivers were built with "WinDDK." I guess I'll
have to Google this to find out what this means. Can anyone describe
what the rudimentary procedures are for tweaking a driver?


Thanks, John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I Finally received an email from MS. They said to try it in Safe Mode
and it worked. The device was completely stable; however, I was only
able to perform a quick format using the default settings, which were
FAT file system & 32KB allocation unit size. Is this normal?


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

no, not normal. but it may help them diagnose the issue. please
continue to keep us posted here. there are quite a few people having
issues with these devices.

On Sat, 13 Oct 2007 02:55:48 -0500, coljohnhannibalsmith
wrote:


I Finally received an email from MS. They said to try it in Safe Mode
and it worked. The device was completely stable; however, I was only
able to perform a quick format using the default settings, which were
FAT file system & 32KB allocation unit size. Is this normal?
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

did MS support ask for the crash data? if not, when you email them
again, tell them you have this info.


On Sat, 13 Oct 2007 01:24:53 -0500, coljohnhannibalsmith
wrote:


Barb,

I located the driver file in the "Travelmate 6292" folder. It was also
located in one or two others. The drivers loaded successfully, then I
was prompted to restart the computer, which I did. I installed the SD
card and was prompted to format it. The screen went blank and came back
on. I then got a window stating that Windows had shut down; but I was
able to close that window and press "OK" to start the format. The
format proceeded for about a minute, then I got a Blue Screen again,
with scrambled video, just like before. I removed the SD card and
performed a cold boot to reload Windows. When Windows reloaded I got
the following error message:

Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000003452
BCP2: 00000000001E0000
BCP3: FFFFF70000081508
BCP4: 0000000000000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini101207-02.dmp
C:\Users\John\AppData\Local\Temp\WER-41890-0.sysdata.xml
C:\Users\John\AppData\Local\Temp\WERDBD9.tmp.vers ion.txt

Read our privacy statement:
'Microsoft Online Crash Analysis'
(http://go.microsoft.com/fwlink/?link...3&clcid=0x0409)


I tried one more time with similar results.


BTW, I finally read the release notes for the previous drivers I was
using and for the new drivers. It appears the drivers I was using
before were for XP x64. Oddly enough, I was able to install these
through Device Manager. At least this set was intended for Vista x64.
I also learned from reading the release notes, that this set of drivers
is intended to provide SDHC support. My card reader's still not
working; but at least I know that my card reader can be updated for SDHC
support, by drivers alone. Perhaps a Hotfix or a driver tweak will
allow me to get the reader working. Fortunately, I don't think I'm
going to need to modify the mother board anymore.

I have an active "Paid" trouble ticket open with Microsoft for this
issue. If they provide me with a resolution, I will share it with all
of you.

I'm really at a loss for what to try next. I'm pretty sure the drivers
are correct. This is looking more and more like a Vista issue. I'm
wondering if I should try a different brand of SD card, or just wait to
hear back from MS. I'm also wondering how to "tweak" a driver. Device
Manager states these drivers were built with "WinDDK." I guess I'll
have to Google this to find out what this means. Can anyone describe
what the rudimentary procedures are for tweaking a driver?


Thanks, John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I received another email from "Vivian" at MS last night. She said she
analyzed the Minidump files I sent her as an attachment and stated that
"ntoskernel.exe" was the affected OS file. Also, in her reply, she
instructed me to restart the system in "Clean Boot" mode. This involves
running "msconfig" and checking "Hide All" on the Services Tab, then
pressing "Disable ALL;" then pressing "Disable ALL" on the Startup Tab,
then pressing Apply, OK and restarting the system, also checking "Don't
Show This Message Again," when I get the msconfig NAG window when
Windows restarts. I then inserted the SD card and Windows did not detect
it at all. I then checked Device Manager and found a yellow "Conflict"
icon next to:"Storage Controllers\ENE PCI Secure Digital / MMC Card
Reader Controller."
I then pressed "Scan For Hardware Changes" in DM and the Conflict icon
remained. Then I opened the Properties window for this device and read
the following message in the "Device Status" window: "Windows cannot
load the driver for this hardware. The driver may be corrupt or
missing." I then attempted to reinstall the driver from the "DM
Properties" window; but the Wizard reported that the device was
up-to-date, almost immediately, leading me to believe that nothing was
actually installed, since reinstalling the driver should have taken at
least a couple of seconds. I then removed the SD Card and pressed "Scan
For Hardware Changes" again and the Conflict icon remained. I then
restarted the system in Normal mode and the Conflict icon remained. I
then instructed DM to uninstall the driver and delete the driver
software by checking the appropriate box in the confirmation window.
Windows' "Plug & Play" started immediately and could not find the driver
software, so I had to manually guide P&P to the correct folder, DM
installed the driver successfully and the yellow conflict incon
disappeared. I did not retest the SD card in Normal or Clean Boot mode,
because I was composing a response email to Vivian at MS and a Blue
Screen would have caused me to have to log back into Hotmail again.
Besides, it was after 11:00 pm and I had had enough for one day.

BTW, Vivian also instructed me to run the "Memory Diagnostic Tool" and
this would not work from either the Startup Search Window or the install
disk. In both cases I received the message: "Info for the selected entry
could not be loaded because the application is missing or corrupt,"
"boot\memtest.exe," Status: 0xc000000e. I drilled down to the
appropriate folder and located the application "memtest.exe," Version:
6.0.6000.16386, Date Modified: 11/2/06 2:51 am, 377 KB. I checked the
Permissions and System, Administrators, and Users all have Read &
Execute permissions. These appear to be correct.

Vivian also had me run "MSINFO32" and save the file to the Desktop as a
compressed file to email to her as an attachment, which I did.

**Please stay tuned for the next exciting installment of: "What the
$#@!^& happened to my Memory Card Reader."

-John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

thanks for the update. can't wait for the next exciting "chapter"
;-)

On Tue, 16 Oct 2007 10:17:44 -0500, coljohnhannibalsmith
wrote:


I received another email from "Vivian" at MS last night. She said she
analyzed the Minidump files I sent her as an attachment and stated that
"ntoskernel.exe" was the affected OS file. Also, in her reply, she
instructed me to restart the system in "Clean Boot" mode. This involves
running "msconfig" and checking "Hide All" on the Services Tab, then
pressing "Disable ALL;" then pressing "Disable ALL" on the Startup Tab,
then pressing Apply, OK and restarting the system, also checking "Don't
Show This Message Again," when I get the msconfig NAG window when
Windows restarts. I then inserted the SD card and Windows did not detect
it at all. I then checked Device Manager and found a yellow "Conflict"
icon next to:"Storage Controllers\ENE PCI Secure Digital / MMC Card
Reader Controller."
I then pressed "Scan For Hardware Changes" in DM and the Conflict icon
remained. Then I opened the Properties window for this device and read
the following message in the "Device Status" window: "Windows cannot
load the driver for this hardware. The driver may be corrupt or
missing." I then attempted to reinstall the driver from the "DM
Properties" window; but the Wizard reported that the device was
up-to-date, almost immediately, leading me to believe that nothing was
actually installed, since reinstalling the driver should have taken at
least a couple of seconds. I then removed the SD Card and pressed "Scan
For Hardware Changes" again and the Conflict icon remained. I then
restarted the system in Normal mode and the Conflict icon remained. I
then instructed DM to uninstall the driver and delete the driver
software by checking the appropriate box in the confirmation window.
Windows' "Plug & Play" started immediately and could not find the driver
software, so I had to manually guide P&P to the correct folder, DM
installed the driver successfully and the yellow conflict incon
disappeared. I did not retest the SD card in Normal or Clean Boot mode,
because I was composing a response email to Vivian at MS and a Blue
Screen would have caused me to have to log back into Hotmail again.
Besides, it was after 11:00 pm and I had had enough for one day.

BTW, Vivian also instructed me to run the "Memory Diagnostic Tool" and
this would not work from either the Startup Search Window or the install
disk. In both cases I received the message: "Info for the selected entry
could not be loaded because the application is missing or corrupt,"
"boot\memtest.exe," Status: 0xc000000e. I drilled down to the
appropriate folder and located the application "memtest.exe," Version:
6.0.6000.16386, Date Modified: 11/2/06 2:51 am, 377 KB. I checked the
Permissions and System, Administrators, and Users all have Read &
Execute permissions. These appear to be correct.

Vivian also had me run "MSINFO32" and save the file to the Desktop as a
compressed file to email to her as an attachment, which I did.

**Please stay tuned for the next exciting installment of: "What the
$#@!^& happened to my Memory Card Reader."

-John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Vivian at MS next had me attempt to use the SD card in "Device" Clean
Boot mode. This involves opening Device Manager and disabling all
non-essential devices, which I did, inluding the other two components of
the 5-in-1 card reader, which were not being used. When I inserted the
SD card, the system Blue Sceened almost inmediately. So, it appears the
problem is either with the driver or with Vista itself. I can't wait to
hear the response from MS! BTW, Vivian said that if necessary she will
open a separate Trouble Ticket for the "memtest.exe" problem, free of
charge. This one definitely sounds like an MS isssue, so at least
they're taking responsibility for it. I don't know if I'll ultimately
get a resolution; but so far their service has been pretty good.

Anyway, I've learned a little bit about device driver troubleshooting.
It apears the process is to test the device in Safe Mode and if stable,
test again in Clean Boot mode. If stable, reenable applications and
services until the device fails and you've found the culprit. If
unstable in Clean Boot mode, test the device in Device Clean Boot mode.
If stable, reenable devices until the device under consideration fails
and again you've found you're culprit. If unstable, then the issue is
either with the driver itself or the OS. Very interesting! This is where
I am now.

If MS places the blame on the driver my next step will be to post the
text of the .INF files here, for the drivers that aren't working and
perhaps the original XP x32 drivers, which I've never tested; but assume
must have worked when the unit shipped. Then with luck a knowledgeable
person might be able to examine them and point out any differences that
could potentially be the source of the problem. This set of drivers
actually contains 4 components. The CardBus driver, the SD/MMC Card
Reader, the MS/MS Pro Card Reader and the xD Card Reader. I intend to
post the .INF files for all 4 devices for the failing driver set and a
known good driver set, albeit for XP x32. I believe I have all the tools
I need to edit drivers now. I've got the .CAB SDK, the Vista WDK, WINPE2
and the Express version of MS Visual Studio 2005 and all the relevant
components. At this point all I'll need is a couple of hints to point me
in the right direction. Wow, I never thought I'd get this deep into this
mud hole, yikes!


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Wow, that's a lot of work for you to do. I do hope that this leads
to a successful resolution. Please continue to keep us posted.

On Fri, 19 Oct 2007 12:52:13 -0500, coljohnhannibalsmith
wrote:


Vivian at MS next had me attempt to use the SD card in "Device" Clean
Boot mode. This involves opening Device Manager and disabling all
non-essential devices, which I did, inluding the other two components of
the 5-in-1 card reader, which were not being used. When I inserted the
SD card, the system Blue Sceened almost inmediately. So, it appears the
problem is either with the driver or with Vista itself. I can't wait to
hear the response from MS! BTW, Vivian said that if necessary she will
open a separate Trouble Ticket for the "memtest.exe" problem, free of
charge. This one definitely sounds like an MS isssue, so at least
they're taking responsibility for it. I don't know if I'll ultimately
get a resolution; but so far their service has been pretty good.

Anyway, I've learned a little bit about device driver troubleshooting.
It apears the process is to test the device in Safe Mode and if stable,
test again in Clean Boot mode. If stable, reenable applications and
services until the device fails and you've found the culprit. If
unstable in Clean Boot mode, test the device in Device Clean Boot mode.
If stable, reenable devices until the device under consideration fails
and again you've found you're culprit. If unstable, then the issue is
either with the driver itself or the OS. Very interesting! This is where
I am now.

If MS places the blame on the driver my next step will be to post the
text of the .INF files here, for the drivers that aren't working and
perhaps the original XP x32 drivers, which I've never tested; but assume
must have worked when the unit shipped. Then with luck a knowledgeable
person might be able to examine them and point out any differences that
could potentially be the source of the problem. This set of drivers
actually contains 4 components. The CardBus driver, the SD/MMC Card
Reader, the MS/MS Pro Card Reader and the xD Card Reader. I intend to
post the .INF files for all 4 devices for the failing driver set and a
known good driver set, albeit for XP x32. I believe I have all the tools
I need to edit drivers now. I've got the .CAB SDK, the Vista WDK, WINPE2
and the Express version of MS Visual Studio 2005 and all the relevant
components. At this point all I'll need is a couple of hints to point me
in the right direction. Wow, I never thought I'd get this deep into this
mud hole, yikes!
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Well I just received another email from MS and they state that in
addition to "ntoskernel.exe," "ntfs.sys" is also affected; so Vivian at
MS had me run "chkdsk /f /r." I assume the '/r' part is an instruction
to repair the file system if any errors are found. chkdsk took about 1
1/2 hours to run and found no errors. Vivian; however did find a problem
in my BCD file. She said that "memtest.exe" was set to the wrong
partition; so she had me run:
"BCDEDIT /SET {memdiag} partion=c:" This completed successfully. I then
ran the Memory Diagnostic Tool and restarted the system. The Memory
Diagnostic Tool ran as expected and found no errors. Well at least I've
gotten this problem out of the way. I'm not entirely surprised by this
error, since I upgraded the hard drive on my Notebook to 160GB within
days of upgrading the Vista x64. I did this by using a commercially
available USB, Universal cloning kit; however instead of using the
cloning software supplied by the manufacturer, I used the Acronis
cloning software I downloaded from Seagate, who manufactured the drive.
I incorrecctly performed the last step of the cloning process, which was
to restart the Notebook with the cloned drive still attached. Instead I
removed the drive before restarting. When I did, the original drive
would not restart and I had to use the install disk to repair the drive,
after which Vista x64 started normally. The same thing also occurred on
the cloned drive when I replaced the original drive with it. Here's the
reason this happened. The instructions for the cloning software supplied
by the cloning kit manufacturer warned profusely about NOT leaving the
cloned drive connected durring restart; so I removed the cloned drive
prior to restart. Much to my chagrin, the Seagate Acronis cloning
software instructed leaving the cloned drive connected durring restart.
I didn't bother to read that far until I had the restart problem. I
assumed the cloning process would be universal, so I assumed I would
follow the same steps for the other application. I guess I learned "my
lesson!"

Unfortunatey the SD Card issue still persists. Somehow Vivian at MS was
able to determine that I had not disabled the ATI Display Driver durring
Device Clean Boot Mode. I didn't disable this, because I thought the
display would stop working. She asked me to make sure that the device
uninstalled completely before testing the SD Card in this mode and if it
didn't to make sure I installed the latest driver. She provided me with
a link to an ATI driver on Acer's website, unfortunately it was for
Vista NOT Vista x64. I had already encountered this problem when I
originally started searching for x64 drivers and located the most
up-to-date driver on ATI's website. BTW, it's running beautifully. I was
able to get the Display Driver, The South Bridge Drivers and the
Catalyst Control Panel for the "ATI Radeon 1100 card." Those of us with
Aspire 5100 Notebooks have been waiting with baited breath for these to
be released. Anyway they're there and they're working perfectly. I do
recommend installing these in order though; starting with the Display
Driver, then the South Bridge Drivers, then the Catalyst Control Panel.

Anyway, this time I disabled the ATI Display Driver along with
everything else that could be disabled, without shutting down the
system. The display continued to work in VGA mode. Then I inserted the
SD Card again. It Blue Screened immediately, so now I have to wait for
MS's next email to troubleshoot further.


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

ouch. you've certainly been having quite a time with this. I do hope
that the MS folks come up with a resolution.

On Tue, 23 Oct 2007 14:48:09 -0500, coljohnhannibalsmith
wrote:

Then I inserted the
SD Card again. It Blue Screened immediately, so now I have to wait for
MS's next email to troubleshoot further.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I have started a parallel thread he

http://www.vistax64.com/drivers/1016...k-drivers.html



I think my last post there may be of much interest, to those with that
inclination.


-John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Well here goes,


Since the last time I wrote I've had two more TS sessions with MS.
Here's how they went:

Prior to the previous TS session, Vivian escalated my ticket to an
Escalation Engineer named Emma. Emma had me perform a complete format
of the C:\ drive and then a Complete PC Restore without checking the
select box to "Repartition and Reformat to Match the Backup," suspecting
that "chkdsk" may have missed something. The system Blue Screed as
before when I inserted the SD Card; so during the last TS session, she
had me perform an "inplace-upgrade." This involves having Windows
reinstall the system files from the install disk. This is supposed to
leave your files and settings alone; but rewrites the Registry and
deletes all the Windows Updates. It also forced me to reactivate, which
I could not do online, since I have a wireless Internet connection
through T-Mobile, which could not be launched from the Activation
window. "God is this a buggy piece of @#$!%?" They're using me as an
Alpha Tester and have made me pay $189.00 plus the $59.00 support fee
for the privilege. They should be paying me as an SW Tester. I've got
half a mind to file charges with the Department of Labor Standards
Enforcement for unpaid wages! Then again, maybe I only have half a
mind, which is far more likely.

Oh, BTW I also got a nasty message in the lower right corner of the
Desktop that read: "This copy of Windows is not Genuine." This remained
even after re-activation. Fortunately this went away after a couple of
restarts.

Then I inserted the SD Card and held my breath. "Plug and Play"
started immediately and placed a balloon on my Desktop stating:
"Installing Software." This never happened before! Shortly thereafter,
that went away and P&P placed another balloon on my Desktop stating:

"Secure Digital_MMC_Drive.
Device Driver Software Installed Successfully."

This took at least a minute and nothing. No Blue Screen, no Dialog
Boxes stating that some critical Windows component, like "Windows
Explorer" had stopped working; so I opened the SD Card in "Computer" and
was able to store files in it. I was also able to successfully perform
Quick & Full Formats in FAT, FAT32 & NTFS and store files on the card in
each of these formats. By this time I'm wiping the sweat off of my brow
and daring to think that I've finally achieved success; but this was
short lived. During all of this I was still connected to the Internet
and one of my applications installed an update. I was persuaded to
restart, which I did, with the SD Card still inserted. When Windows
tried to launch the Desktop the system Blue Screened. I then removed
the SD Card and Cold Booted. I started Windows normally, then
reinserted the SD Card after Windows had completely loaded the Desktop.
A dialog Box popped up stating that my HD Soft Conn Modem had stopped
working; but I closed it and persevered. I was prompted to format the
SD card and when I clicked "OK" another Blue Screen.

Anyway, I got a little farther along this time. Apparently, when
Windows is first installed the Memory Card Reader Driver and Vista x64
are compatible; but this relationship doesn't last long. For some
reason this relationship deteriorates relatively quickly in human time;
however more slowly in processor time.

Emma says she thinks her manger will let her ship me a Retail Version
of Vista x64; but I'm not sure what this is supposed to accomplish. At
this point it appears MS is trying "Hail Mary" passes instead of trying
to fix the problem. At this point I don't care. I just want to use my
damn computer for something other than a paperweight.



-John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

do you know what the update was? did you try going into device
manager and doing a driver rollback? (and or a system restore?)

this is extremely painful to read and has to be much worse for you,
and I admire you patience.

On Sat, 3 Nov 2007 19:26:32 -0500, coljohnhannibalsmith
wrote:

During all of this I was still connected to the Internet
and one of my applications installed an update. I was persuaded to
restart, which I did, with the SD Card still inserted. When Windows
tried to launch the Desktop the system Blue Screened. I then removed
the SD Card and Cold Booted. I started Windows normally, then
reinserted the SD Card after Windows had completely loaded the Desktop.
A dialog Box popped up stating that my HD Soft Conn Modem had stopped
working; but I closed it and persevered. I was prompted to format the
SD card and when I clicked "OK" another Blue Screen.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Barb Bowman;503159 Wrote:
do you know what the update was? did you try going into device
manager and doing a driver rollback? (and or a system restore?)

this is extremely painful to read and has to be much worse for you,
and I admire you patience.

On Sat, 3 Nov 2007 19:26:32 -0500, coljohnhannibalsmith
wrote:

--

Barb Bowman
MS Windows-MVP
'Previous Columns by Barb Bowman'
(http://www.microsoft.com/windowsxp/e...ts/bowman.mspx)
'Barb's Connected World' (http://blogs.digitalmediaphile.com/barb/)


Hum...

The system only works temporarily with no updates loaded. I forget
which application downloaded and installed an upgrade, but it wasn't a
Windows Update and it wasn't driver related. I think it was one of my
Firefox add-ons. Why one of these would require a restart I can't
explain; but I was prompted for a system restart afterward and did so.
That's when my system Blue Screened. I don't believe the application
upgrade is responsible, since the problem persists in clean boot mode.

A driver rollback is a non-starter. I'm using the only Vista x64
drivers available and I've done many system restores. Something else
appears to be going on. My theory at this point is that there is some
instability in "ntfs.sys" that my driver somehow manages to trigger and
this in turn causes a cascade effect, that eventually causes
"ntoskernel.exe" to fail.

The only good thing I think that can come out of receiving a free
Retail version, as the MS engineer suggested is that there may be some
system file differences between the retail and the OEM versions. If
this is so, performing an inplace-upgrade with the retail version may
solve the problem, then again maybe not.

I suspect in the end MS will just need to add or modify a couple lines
of code in ntfs.sys to solve the problem.

-John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I can't imagine that the core files would be different. What are the
file properties of ntfs.sys on your system? what is the status of
the digital certificate?

On Sun, 4 Nov 2007 08:47:45 -0600, coljohnhannibalsmith
wrote:


The only good thing I think that can come out of receiving a free
Retail version, as the MS engineer suggested is that there may be some
system file differences between the retail and the OEM versions. If
this is so, performing an inplace-upgrade with the retail version may
solve the problem, then again maybe not.

I suspect in the end MS will just need to add or modify a couple lines
of code in ntfs.sys to solve the problem.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I'll post the core file info shortly,

I'm away from my Laptop right now. By digital certificate, I assume
you mean for the driver set? These appear to be correctly signed. I
received no warning message when installing and I've checked Device
Manager and the driver manufacturer "ENE Technologies" is displayed.

Yesterday, I read the tutorial section regarding System Files, which
covered some of the TS steps I've been performing with MS at the
following link:

http://www.vistax64.com/tutorials/88...all-vista.html

It states the following if an "inplace-upgrade" fails to resolve the
your issue:

"NOTE: If Vista is still not working properly afterwards, then a Clean
Install would be recommended."

Since I already had my configuration backed up on an external HDD, I
decided to give this a try and not only did the issue persist, but I got
a BSOD when Windows tried to load for the first time and had to restart
the install from the beginning and I got another BSOD after the first
restart after the Windows Desktop completely loaded, even before
inserting the SD Card. I briefly scanned the crash details and they
appeared very similar to those caused by the SD Card.

This is very strange. I didn't get BSODs when cloning the 160GB drive
from my original 100GB drive; but I got BSODs both times when performing
a clean install to the 160GB drive. It's also strange that it appears
to only affect one device. I think what I'll have to do next is
reinstall my 100GB drive, perform a clean install and wait to see if I
get BSODs durring the install or if not and when inserting the SD Card.
This may expose an incompatibility in my new HDD; but then again, the OS
and drivers are already mounted in RAM. The memory Diagnostic Tool
reports no errors after several passes.

I received another email from Emma, after having done the clean install
and she suggested uninstalling Firefox and collecting the Dump files
again. I nearly lost it! Apparently it seems she's forgotten that we
TS'd the system in Clean Boot mode. She must now think that Firefox's
downloading and installation of an update is causing the problem. It
seems to me that would be pretty difficult for an unrelated & unmounted
application to do and I expressed as much to her. I also informed her
that the problem persisted and displayed additional symptoms after a
clean install.

I'm losing my faith in this engineer. She keeps asking me to do things
over again, that don't appear to make sense with respect to the steps
we've already taken together. Also, her English is barely better than
pigeon. She appears to be located in mainland China. I've probably got
enough energy left to check for the same problems with another drive,
then if I still can't get a resolution I'm going to contact a Laptop
repair company and let them give it a try.

Barb,

Do you know of any reputable companies that can handle Latop repair of
this complexity?


Thanks, John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

So here's the latest,


I performed a Clean Install of Vista x64 on my old 100GB drive. I got
BSODs after install and BSODs after inserting the SD Card, just like on
my new drive. I did not load any other programs other than Windows and
the Card Reader Drivers. So, at least I know my new HDD is not at
fault. Then I loaded Vista x32 from the Acer upgrade disk. I had no
BSOD problems during or after install and I restarted repeatedly to
stress test the install, still no problems. I then inserted the SD Card
and it worked flawlessly. I was able to perform quick and full formats
in all three file systems, FAT, FAT 32 & NTFS. I intentionally left the
SD Card inserted and restarted repeatedly. No further problems. It
certainly appears that Vista x64 is just a buggy, unstable "bowl of
sugar."

Thank You Microsoft!

Now all I have to do is do battle with their incompetent engineer. I'm
very close to asking MS to replace her. I have very little patience
left.


-John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Although I don't normally recommend flashing the BIOS unless there
is a real problem, it "appears" there is a new BIOS for your system
from 11/1 at
ftp://ftp.support.acer-euro.com/note...ire_5100/bios/

(and you do need to understand that there is some risk in flashing a
BIOS, altho I've done it many times myself on various systems.)

Some of us were/are having media reader issues on Acer's Ferrari
4000 (and 5000).

I resolved most of my issues with a BIOS update for the 4000 (see
http://blogs.digitalmediaphile.com/b...ew+BIOS.a spx
for my tale of woe).

Your chronology of interaction with the MS engineer is depressing.
I'm going to send it around to a few PSS and other folks I know at
MS. While I doubt they will comment, I will make them aware of your
bad experience.

On Wed, 7 Nov 2007 03:33:26 -0600, coljohnhannibalsmith
wrote:


So here's the latest,


I performed a Clean Install of Vista x64 on my old 100GB drive. I got
BSODs after install and BSODs after inserting the SD Card, just like on
my new drive. I did not load any other programs other than Windows and
the Card Reader Drivers. So, at least I know my new HDD is not at
fault. Then I loaded Vista x32 from the Acer upgrade disk. I had no
BSOD problems during or after install and I restarted repeatedly to
stress test the install, still no problems. I then inserted the SD Card
and it worked flawlessly. I was able to perform quick and full formats
in all three file systems, FAT, FAT 32 & NTFS. I intentionally left the
SD Card inserted and restarted repeatedly. No further problems. It
certainly appears that Vista x64 is just a buggy, unstable "bowl of
sugar."

Thank You Microsoft!

Now all I have to do is do battle with their incompetent engineer. I'm
very close to asking MS to replace her. I have very little patience
left.


-John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Thank you for your assistance,

I've flashed many BIOs myself and am aware of the dangers. Thanks for
the caveat. The greatest danger is from power interruption during a
flash; however corrupted and incorrect files can also be a danger. I am
currently using v3.05 from the AcerPanAm.com site; so this will be the
2nd flash for me. I've noticed this is the second time you've referred
me to a European site. Do they generally release more quickly there
than here in the US? Anyway, the model #5100 looks correct and the
latest version appears to be v3.10, which is consistent with the
previous verion numbers. I will try it after reading your blog and the
"release notes," if there are any.

It appears the next step for me is to perform a Clean Install again on
my new drive and collect the crash data and dump files from the install
BSOD, then save the crash data and dump files from the SD Card BSOD and
forward them to MS with the reminder that these were obatined with no
other software than the OS itself loaded from the first crash & the OS
plus Card Reader Drivers from the second crash. It is my current theory
that the causes are the same. If the files are text files, which I
believe some of them are and they are small enough, I will also post
them here with appropriate labeling, so that all may inspect them and
that my scientific method of discovery may be well documented. When I'm
further along toward a resoltion I will post the actual MS case number,
so that all may inspect.

I'm really convinced the problem is with NTFS.SYS. I've been playing
with the idea of substituting the NTFS.SYS file from XP x64. I don't
know if this is even possible, because it may call different subroutines
or differently named subroutines than the Vista x64 version; but it
would be quite a coup if it worked; however I'll try flashing the BIOS
first.

As an aside, Vista x32 will only see 2GB of my 4GB ram even though it's
supposed to be capable of addressing 128GB Ram. Any thoughts on this?


-John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

1. I don't even both with the US Acer site when looking for drivers
and updates. I think they point everyone to the European ftp site on
one of the links anyway.

2. The clean install and info gathering sounds like a good triage
step.

3. I think you will be prevented from substituting a system file
from XP x64

4. wondering about
http://support.microsoft.com/default.aspx/kb/930261

5. see BIOS settings and see if there is a memory re-mapping
setting.

On Wed, 7 Nov 2007 14:43:00 -0600, coljohnhannibalsmith
wrote:


Thank you for your assistance,

I've flashed many BIOs myself and am aware of the dangers. Thanks for
the caveat. The greatest danger is from power interruption during a
flash; however corrupted and incorrect files can also be a danger. I am
currently using v3.05 from the AcerPanAm.com site; so this will be the
2nd flash for me. I've noticed this is the second time you've referred
me to a European site. Do they generally release more quickly there
than here in the US? Anyway, the model #5100 looks correct and the
latest version appears to be v3.10, which is consistent with the
previous verion numbers. I will try it after reading your blog and the
"release notes," if there are any.

It appears the next step for me is to perform a Clean Install again on
my new drive and collect the crash data and dump files from the install
BSOD, then save the crash data and dump files from the SD Card BSOD and
forward them to MS with the reminder that these were obatined with no
other software than the OS itself loaded from the first crash & the OS
plus Card Reader Drivers from the second crash. It is my current theory
that the causes are the same. If the files are text files, which I
believe some of them are and they are small enough, I will also post
them here with appropriate labeling, so that all may inspect them and
that my scientific method of discovery may be well documented. When I'm
further along toward a resoltion I will post the actual MS case number,
so that all may inspect.

I'm really convinced the problem is with NTFS.SYS. I've been playing
with the idea of substituting the NTFS.SYS file from XP x64. I don't
know if this is even possible, because it may call different subroutines
or differently named subroutines than the Vista x64 version; but it
would be quite a coup if it worked; however I'll try flashing the BIOS
first.

As an aside, Vista x32 will only see 2GB of my 4GB ram even though it's
supposed to be capable of addressing 128GB Ram. Any thoughts on this?


-John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I already have KB929777 installed, and I have an ATI Graphics Card not
an NVIDIA; but it does appear the error is ram related. It took me a
while, but I finally figured out why you're leaning in this direction.
The Card Reader was stable with Vista x32 only seeing 2GB ram. So,
after recollecting the crash data I yanked the second memory stick and
guess what. The Card Reader works rock solid in Vista x64. It's
looking now like the Card Reader and the upper 2GB of ram are trying to
share the same address space. I would have thought Device Manager would
catch the conflict, but I guess not. I'm fairly certain my BIOS doesn't
have a memory remapping feature; but this can be done in Device Manager
can't it?

BTW, I haven't flashed the BIOS chip with the new version yet; but I'll
check for this feature as soon as I do.


-John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

You would have to remap in BIOS. Acer is pretty much ignoring any
requests for fixes for x64 compatibility fixes, but if you find
after flashing the new BIOS there is no support, you should still
contact them and add another voice/complaint.

On Thu, 8 Nov 2007 03:21:44 -0600, coljohnhannibalsmith
wrote:


I already have KB929777 installed, and I have an ATI Graphics Card not
an NVIDIA; but it does appear the error is ram related. It took me a
while, but I finally figured out why you're leaning in this direction.
The Card Reader was stable with Vista x32 only seeing 2GB ram. So,
after recollecting the crash data I yanked the second memory stick and
guess what. The Card Reader works rock solid in Vista x64. It's
looking now like the Card Reader and the upper 2GB of ram are trying to
share the same address space. I would have thought Device Manager would
catch the conflict, but I guess not. I'm fairly certain my BIOS doesn't
have a memory remapping feature; but this can be done in Device Manager
can't it?

BTW, I haven't flashed the BIOS chip with the new version yet; but I'll
check for this feature as soon as I do.


-John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Barb Bowman;507241 Wrote:
You would have to remap in BIOS. Acer is pretty much ignoring any
requests for fixes for x64 compatibility fixes, but if you find
after flashing the new BIOS there is no support, you should still
contact them and add another voice/complaint.

On Thu, 8 Nov 2007 03:21:44 -0600, coljohnhannibalsmith
wrote:

--

Barb Bowman
MS Windows-MVP
'Previous Columns by Barb Bowman'
(http://www.microsoft.com/windowsxp/e...ts/bowman.mspx)
'Barb's Connected World' (http://blogs.digitalmediaphile.com/barb/)


Ah yes the BIOS,

The BIOS has two versions a DOS version and a Windows version. The
README file states that you can launch each version in its appropriate
environment. When I tried to launch the Windows version, I got an "Error
1275" stating:

"The Driver could not be loaded."

The text of the error message said to "check administrator privileges."
Well I'm the administrator and I have User Account Control turned off
and Data Execution Prevention in the default setting, which is to
monitor Windows Services only NOT Programs; so this certainly isn't the
cause.

I then launched a DOS window and attempted to run both the Windows and
the DOS versions of the installer. I received error messages both times.
I believe when I tried to run the DOS version, I simply got a gereric
error message stating an incompatibility issue. If my memory serves me
correctly, when I tried to run the Windows version from the DOS window,
I got an error message stating that the application is not compatible
with 64 bit OSs. This makes sense, since Acer is trying their best, NOT
to offer any x64 support. What I'm going to try next is to reinstall my
old 100GB drive with Vista x32 on it and attempt to load the new BIOS
from there. My last BIOS flash was done from XP x32.

BTW, I checked Device Manager and it appears there's an option to
modify resources; but it's greyed-out and it also appears greyed-out for
other unrelated components in DM as well. I wonder what bedeviled MS to
disable this feature and if there's any way to turn it back on? What
knuckleheads! When you deliver an unfinished product to the public, you
"DON'T" disable TS features.

Oh, and Emma from MS wrote back again, she said she wanted me to send
her the crash data and data from MSIFNO32, from after I performed the
Clean Install, which makes sense; but then, she said we would "update
the drivers one by one." This begs the questions: "Why would we need to
update any drivers at all, especially more than one, since I'm getting
BSODs immediately after install, before loading the SD Card Drivers;
which means the only drivers being loaded are those supplied by the OS
itself and when I get the SD Card BSODs, the only drivers loaded are
those for the Memory Card Reader Plus the OS and I have the latest
Memory Card Reader Drivers and she already knows that.

I haven't told her I've TS'd the problem to the upper 2GB of ram yet;
but I'm wondering if she'd even understand if I did.



Weeeee...........:party:


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Finally had time to read:

I resolved most of my issues with a BIOS update for the 4000 (see
'Barb's Connected World - Updating Acer Ferrari x64 Ultimate with new
BIOS'
(http://blogs.digitalmediaphile.com/b...ew+BIOS.a spx)
for my tale of woe).

I see you had the same problem and found a work around for it.


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

so you're good with my workaround?

On Thu, 8 Nov 2007 11:46:00 -0600, coljohnhannibalsmith
wrote:


Barb Bowman;507241 Wrote:
You would have to remap in BIOS. Acer is pretty much ignoring any
requests for fixes for x64 compatibility fixes, but if you find
after flashing the new BIOS there is no support, you should still
contact them and add another voice/complaint.

On Thu, 8 Nov 2007 03:21:44 -0600, coljohnhannibalsmith
wrote:

--

Barb Bowman
MS Windows-MVP
'Previous Columns by Barb Bowman'
(http://www.microsoft.com/windowsxp/e...ts/bowman.mspx)
'Barb's Connected World' (http://blogs.digitalmediaphile.com/barb/)


Ah yes the BIOS,

The BIOS has two versions a DOS version and a Windows version. The
README file states that you can launch each version in its appropriate
environment. When I tried to launch the Windows version, I got an "Error
1275" stating:

"The Driver could not be loaded."

The text of the error message said to "check administrator privileges."
Well I'm the administrator and I have User Account Control turned off
and Data Execution Prevention in the default setting, which is to
monitor Windows Services only NOT Programs; so this certainly isn't the
cause.

I then launched a DOS window and attempted to run both the Windows and
the DOS versions of the installer. I received error messages both times.
I believe when I tried to run the DOS version, I simply got a gereric
error message stating an incompatibility issue. If my memory serves me
correctly, when I tried to run the Windows version from the DOS window,
I got an error message stating that the application is not compatible
with 64 bit OSs. This makes sense, since Acer is trying their best, NOT
to offer any x64 support. What I'm going to try next is to reinstall my
old 100GB drive with Vista x32 on it and attempt to load the new BIOS
from there. My last BIOS flash was done from XP x32.

BTW, I checked Device Manager and it appears there's an option to
modify resources; but it's greyed-out and it also appears greyed-out for
other unrelated components in DM as well. I wonder what bedeviled MS to
disable this feature and if there's any way to turn it back on? What
knuckleheads! When you deliver an unfinished product to the public, you
"DON'T" disable TS features.

Oh, and Emma from MS wrote back again, she said she wanted me to send
her the crash data and data from MSIFNO32, from after I performed the
Clean Install, which makes sense; but then, she said we would "update
the drivers one by one." This begs the questions: "Why would we need to
update any drivers at all, especially more than one, since I'm getting
BSODs immediately after install, before loading the SD Card Drivers;
which means the only drivers being loaded are those supplied by the OS
itself and when I get the SD Card BSODs, the only drivers loaded are
those for the Memory Card Reader Plus the OS and I have the latest
Memory Card Reader Drivers and she already knows that.

I haven't told her I've TS'd the problem to the upper 2GB of ram yet;
but I'm wondering if she'd even understand if I did.



Weeeee...........:party:
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I flashed the BIOS. The system still Blue Screens after I insert the SD
Card and there is still no support for memory remapping.


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

yuck. I can't think of anything else to suggest other than hounding
Acer for better x64 support.

On Fri, 9 Nov 2007 08:19:09 -0600, coljohnhannibalsmith
wrote:


I flashed the BIOS. The system still Blue Screens after I insert the SD
Card and there is still no support for memory remapping.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I've just sent Acer a request for email support. I've phrased it in such
a way that it shouldn't violate their support policies. I haven't told
them that I can't even get the unit to see the upper 2GB ram in Vista;
but they don't need to know that. The email follows below:

Subject: Use of ENE Memory Card Reader causes BSODs with 4GB ram
installed.

Acer Aspire 5102WLMi w/o Bluetooth, Orbicam, or TV Tuner
Model No: BL51
AS5102WLMI-MCEEN-TL50/15.4
ACB/512M/100G US
S/N: LXABH0J0116380F0B41601
O/S: Vista Home Premium.
Date of Purchase: 2/29/2007

I recently upgraded to the Vista Home Premium version supplied to me by
Acer through the Vista Upgrade Program, that my unit qualified for.

I can only use the internal ENE Memory Card Reader with 2GB ram
installed. When I install the upper 2GB ram, my system Blue Screens when
I attempt to use the Card Reader.

The crash data follows below:

Problem signatu
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000003452
BCP2: 00000000001E0000
BCP3: FFFFF70000081508
BCP4: 0000000000000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini101207-02.dmp
C:\Users\John\AppData\Local\Temp\WER-41890-0.sysdata.xml
C:\Users\John\AppData\Local\Temp\WERDBD9.tmp.versi on.txt

It is my opinion that this device shares memory mapping with the upper
2GB ram. I also suspect this will require a BIOS rewrite to remap the
device or a BIOS rewrite to add memory remapping ability to the BIOS
itself. Both highly desireable!


This is a "Hail Mary" play. Hopefully "meine kleine weisse Lüge" will
generate a productive result.


-John


PS., I called Acer this morning and the phone tech said to download the
"chipset drivers" to get the unit to see the upper 2GB ram in Vista x32.
I've downloaded and installed the most recent set from "amd.ati.com;"
but they did not slove the problem. I haven't tried downloading and
installing the set from the AcerPanAm.com site yet.


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Opps:

I think I'm screwed, when they see this:

OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

I suppose I can always tell them I'm having the same problem on a
similar unit, or on a different drive with the x64 OS installed and
provided them with the wrong crash data set and promise to supply them
with correct data set.


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

they may not even notice. more likely they will ask you if the RAM
is genuine Acer brand RAM and then tell you, sorry, you need
official Acer RAM.

On Fri, 9 Nov 2007 13:34:26 -0600, coljohnhannibalsmith
wrote:


Opps:

I think I'm screwed, when they see this:

OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

I suppose I can always tell them I'm having the same problem on a
similar unit, or on a different drive with the x64 OS installed and
provided them with the wrong crash data set and promise to supply them
with correct data set.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

That's fine. I'll just tell them it's Acer ram. If the push me, I'll
go out and buy some.


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Good luck. I DO hope you are successful.

On Fri, 9 Nov 2007 14:48:40 -0600, coljohnhannibalsmith
wrote:


That's fine. I'll just tell them it's Acer ram. If the push me, I'll
go out and buy some.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

Third Party BIOS upgrade:

I've come across an interesting website while searching on Google:

'eSupport.com - scan.esupport.com -'
(http://scan.esupport.com/?CFID=378388&CFTOKEN=25298523)

It appears to offer 3rd party BIOS upgrades, which may offer a solution
to my problem. I suspect however; that most of their business is from
people who have older machines. They do some some interesting claims:

**eSupport is the world's oldest and largest provider of BIOS Upgrades
with nearly 20 years of unparalleled excellence in the industry.

**Option To Assign IRQ's.

If these folks don't have a BIOS upgrade for my system, I suspect they
might be able to write one or direct me to someone who can.


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I'd personally stay away from non manufacturer's BIOS. You can't
lose anything by making an inquiry, but rather than toast a machine,
I'd buy an external card reader.

On Wed, 14 Nov 2007 18:19:07 -0600, coljohnhannibalsmith
wrote:


Third Party BIOS upgrade:

I've come across an interesting website while searching on Google:

'eSupport.com - scan.esupport.com -'
(http://scan.esupport.com/?CFID=378388&CFTOKEN=25298523)

It appears to offer 3rd party BIOS upgrades, which may offer a solution
to my problem. I suspect however; that most of their business is from
people who have older machines. They do some some interesting claims:

**eSupport is the world's oldest and largest provider of BIOS Upgrades
with nearly 20 years of unparalleled excellence in the industry.

**Option To Assign IRQ's.

If these folks don't have a BIOS upgrade for my system, I suspect they
might be able to write one or direct me to someone who can.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I have been communicating with a Dan at Ircona a distributor of the
Phoenix BIOS and he states that it would cost about $1000.00/day for the
development effort involved in a BIOS rewrite. He suggested another
strategy. He suggested modifying the E820 table after BIOS completes but
before the OS loads. He states that this can be done by modifying the
boot sector to intercept the Windows load and modify the E820 table
before allowing Windows to finish loading.

This sounds like very technical stuff! Does anyone know what an E820
table is and how I would go about writing a program to do what Dan
suggested above or is anyone out there qualified to do this?



Thanks, John


--
coljohnhannibalsmith

I love it when a plan comes together.
It keeps me "on the jazz!"

SD (Secure Digital) Causes Blue Screen in Vista x64
 

I'll wish you the best of luck with this one..

On Mon, 19 Nov 2007 15:24:10 -0600, coljohnhannibalsmith
wrote:


I have been communicating with a Dan at Ircona a distributor of the
Phoenix BIOS and he states that it would cost about $1000.00/day for the
development effort involved in a BIOS rewrite. He suggested another
strategy. He suggested modifying the E820 table after BIOS completes but
before the OS loads. He states that this can be done by modifying the
boot sector to intercept the Windows load and modify the E820 table
before allowing Windows to finish loading.

This sounds like very technical stuff! Does anyone know what an E820
table is and how I would go about writing a program to do what Dan
suggested above or is anyone out there qualified to do this?



Thanks, John
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/e...ts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/