Hardware Runs 32-bit fine but BSODs with 64?

cgroux202 · Jul 25, 2010

Hey guys,
I have a Toshiba Satelite A205-S6810 laptop, and I had been having a lot of random boot crashes and BSODs at startup when I was trying to run the X64 version of Windows 7. For the fun of it, my friend told me I could try his 32-bit disc for a while to see if it worked better, and lo and behold I had zero crahses on the X86 version for over 2 months. A little while later someone else had told me that they had a 64-bit disc that was working error free for them, so I thought I would give it a shot. Now that I'm back on 64 the exact same type errors have plagued my boot experience. Anyone have any good ideas as to why my laptop refuses to run X64 as well as it should, and is there any way that I might be able to get X64 working on my hradware?

If you want to take a peek at some of the types of BSODs I've been getting, check out one of my older threads:
http://www.sevenforums.com/crashes-debugging/70790-several-different-bsods-mostly-boot.html

Thanks in advance!

Petey7 · Jul 25, 2010

Open event viewer (type Even Viewer into the start menu search bar to find it). Look under Windows logs>Application. See if you can find any events with a red circle and a white X. Ignore any others, including warnings. See if you can find one and tell us what it says. Note, if you have Windows Live Essentials installed you may see entries caused by WLMM. Microsoft says those can be ignored, and won't cause a problem.

cgroux202 · Jul 25, 2010

Sorry, I don't see any events with the red X. They are basically all the i with the blue circle with the exception of a couple warnings. Anything else that might help?

Petey7 · Jul 25, 2010

I'd wait until someone that can accurately read dump files responds. If I see someone is online I'll send them your way. It sounds like a driver, so the Driver Verifier will likely need to be used, but I can't read dump files well, so you'll need on of them to help.

Jonathan_King · Jul 25, 2010

Hello,

Petey7 has asked me to look at your dump files. Could you please follow these directions?

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Awaiting results,
~JK

ttran · Jul 26, 2010

I don't see any minidump file in the one you just post. Please go to C:Window and make sure that the minidump folder is there with .dmp file in it. You might want to check if you have set system to create minidump file.

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Are you using any program such as CCleaner..? Are you sure it is BSODs?

zigzag3143 · Jul 26, 2010

cgroux202 said:
Hey guys,
I have a Toshiba Satelite A205-S6810 laptop, and I had been having a lot of random boot crashes and BSODs at startup when I was trying to run the X64 version of Windows 7. For the fun of it, my friend told me I could try his 32-bit disc for a while to see if it worked better, and lo and behold I had zero crahses on the X86 version for over 2 months. A little while later someone else had told me that they had a 64-bit disc that was working error free for them, so I thought I would give it a shot. Now that I'm back on 64 the exact same type errors have plagued my boot experience. Anyone have any good ideas as to why my laptop refuses to run X64 as well as it should, and is there any way that I might be able to get X64 working on my hradware?

If you want to take a peek at some of the types of BSODs I've been getting, check out one of my older threads:
http://www.sevenforums.com/crashes-debugging/70790-several-different-bsods-mostly-boot.html

Thanks in advance!

You sure your computer can run 64 bit? some of the "core duo's" like mine cant.

Petey7 · Jul 26, 2010

I looked it up for you. The T5450 has full 64-bit support. If you ever want to find more info on your processor, its all right here: Intel® Core 2 Duo Processor T5450 (2M Cache, 1.66 GHz, 667 MHz FSB) with SPEC Code(s) SLA4F

zigzag3143 · Jul 26, 2010

Petey7 said:
I looked it up for you. The T5450 has full 64-bit support. If you ever want to find more info on your processor, its all right here: Intel® Core 2 Duo Processor T5450 (2M Cache, 1.66 GHz, 667 MHz FSB) with SPEC Code(s) SLA4F

Nice link Petey (hence the rep) but the cpu could be 64 bit, and mobo not. BTW there is an easy freeware app from gibson research that will tell you what instruction set and more. here GRC | SecurAble: Determine Processor Security Features |

Ken

cgroux202 · Jul 26, 2010

I downloaded this app and the processor does indeed check out. How would I be able to check the motherboard cpmpadability? It says "NO" for Hradware Visualization by the way, if that means anything to ya'll.

Petey7 · Jul 26, 2010

Virtualization mainly has to do with if you wanted to use XP Mode (or other virtual hardware), which is available for 7 Professional and Ultimate. They have actually made a patch that will let you use XP Mode anyways, but I've heard it doesn't always do so well.

zigzag3143 · Jul 26, 2010

It is somewhat less than perfect and runs substantially slower.

cgroux202 · Jul 26, 2010

ttran said:
I don't see any minidump file in the one you just post. Please go to C:Window and make sure that the minidump folder is there with .dmp file in it. You might want to check if you have set system to create minidump file.

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Click to expand...

Are you using any program such as CCleaner..? Are you sure it is BSODs?

OS Version: Winows 7 Professional X64
Original OS: Winows Vista Home Premium X86
Full Retail
Hardware Age: Approximately 27 Months
OS Age: 1 day

Sorry here's an updated one with dmp files included. I haven't gotten full BSODs but these are my older ones included in the dump. The same type boot errors and BSODs have actually been occuring but they flash so quickly that I can never actually read them. I'm nearly positive the problems occurring now are the same ones that have plagued my previous installations of this OS, so these older dumps should be just as conclusive. Hope this helps!

ttran · Jul 26, 2010

All of the crash dump pointed to memory corruption or giving signal that related to memory corruption. I would download third party called memtestx86 to test the ram.
Memory Diagnostics

AVG was blamed. Third party antivirus are known for causing BSODs. I would recommend to uninstall it for testing purposes. If you need a AV program to protect your computer, you can use microsoft security essential, it is known for BSOD free.
http://www.microsoft.com/security_essentials

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff800028a1b74, fffff880009a9968, fffff880009a91c0}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff800028b535f, fffff88007d08160, 0}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff800028dcb74, fffff880009a8478, fffff880009a7cd0}

Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
Probably caused by : avgldx64.sys ( avgldx64+40976 )

Followup: MachineOwner
---------
BugCheck 1E, {ffffffffc0000005, fffff800028eb35f, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )

Followup: MachineOwner
---------

You also have very out of date driver:

Code:

fffff880`0149b000 fffff880`0149fe80   TVALZ_O  TVALZ_O.SYS  Fri Nov 09 10:08:41 2007 (4733CF39) [COLOR=Blue]TOSHIBA ACPI-Based Value Added Logical and General Purpose Device Driver[/COLOR]
fffff880`04800000 fffff880`04852000   tifm21   tifm21.sys   Thu Jan 25 03:35:19 2007 (45B7C307) [URL="http://www.google.com/search?q=%22Texas%20Instruments%20PCIxx21/PCIxx12%20Integrated%20FlashMedia%20Controller%22"][B]Texas Instruments PCIxx21/PCIxx12 Integrated FlashMedia Controller[/B][/URL]
fffff880`068c4000 fffff880`069e6000   agrsm64  agrsm64.sys  Mon Nov 10 22:01:35 2008 (49184CCF) [COLOR=Blue]Agere Systems Soft Modem[/COLOR]

cgroux202 · Jul 26, 2010

In regards to the memory curruption, I do have one 2GB third-party memory stick in this computer (with one 2GB factory stick.) Do you think that could be the porblem? I'd find it odd that that particular stick would have a porblem on X64 but not X86 though. I'll definately run the memory tests in the morning, and post my results. Thanks for all the help and quick responses everyone. I'm generally pretty good with computers, but this problem has me dumbfounded.

Petey7 · Jul 26, 2010

I had a problem with AVG seeming like it wasn't running right on my x64 machine, which is why I switched to Microsoft Security Essentials in the first place. Also, x86 would only use ~3bg of ram. I know everyone says that other 1giig gets used for other stuff, but if it is a memory problem, I'd bet that has something to do with it.

cgroux202 · Jul 27, 2010

I ran memtest for 21 hours yesterday and it still was not done. It did find like 7 or 8 failed addresses and 700 or so errors so should I assume that one of my memory sticks is faulty? I apologize for not having a full report, but I assumed after I hit esc to reboot that it would ask me if I wanted to save a log, and of course it did not. My laptop just got so hot even with a cooling fan that I thought it was going to explode so i had to shut it down haha.

Jonathan_King · Jul 27, 2010

Heat could be the issue. Take a can of compressed air and blow out the air vents.

Petey7 · Jul 27, 2010

Sounds like the RAM might be faulty, but the heat can be just as much a source of problems.

cgroux202 · Jul 28, 2010

So do ya'll think buying a new RAM stick is my best move? Or should I just go back to 32 where I was experiencing no crashes performing my everyday tasks. I don't game because my GPU is awful, so the RAM never really gets overloaded on X86 while browsing or instant messaging.

Edit: Assuming the compressed air doesn't work.

Hardware Runs 32-bit fine but BSODs with 64?

New member

My Computer My Computer

At a glance

Devil Hunter

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Devil Hunter

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Computational Biologist

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Devil Hunter

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Devil Hunter

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Computational Biologist

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Devil Hunter

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Devil Hunter

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer