ga-a55m-ds2 v1.0 BSOD - Blue Screen of Death, help please

[fkerrx]

I just bought 2 of the same barebones kits from newegg.com with the ga-a55m-ds2 & I get BSOD all the time on both computers , even during install of Windows 7.

I've tried installing from multiple genuine win 7 DVDs, downloaded & installed drivers from gigabyte website, installed all of the latest windows updates,  updated BIOS to latest version, tried standard IDE and ahci mode from BIOS, tried fail-safe BIOS defaults, optimized BIOS defaults, RAM voltage is correct @ 1.5v, any suggestions? 

G.SKILL Value Series 4GB 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600)
AMD A8-3850 Llano 2.9GHz Socket FM1 100W
Seagate Barracuda 7200.12 ST3500413AS 500GB 7200 RPM SATA 6.0Gb/s
Thermaltake A4022 92mm CPU Cooler
GIGABYTE GA-A55M-DS2 FM1 AMD A55 (Hudson D2) rev 1.0
520w antec PSU

[autotech]

Power supply is not that great for your system. Also what do you have connected to it when installing windows as in , external usb devices, 2 monitors,DVD drives front usb case connected to mb usb and so on. I have had the same problem and what i did to fix it was this.

Dont use anything you dont have to at first just 1 monitor, keyboard and mouse, 2 gigs ram, cpu, hard drive, dvd drive in last sata port set to sata or ide.. Make sure hard drive is connected to the first sata port, In bios make sure no overclocking yet and ram is set to unganged and the right timings and voltage.

[Arisen]

Wow.

I ordered a similar (lower spec) bundle which includes the same mobo to build an upgrade system for my wife, and I have never seen such a wide array of BSOD's over the two days it's been running and I've been pulling my hair out trying to figure out what's causing the problem.

Here's the bundle I ordered.

I've tried everything you tried, reinstalled windows, used drivers from Gigabyte's website, tried AHCI/IDE, and ran the system with only mouse, keyboard and USB wireless adapter. Nothing stops the bluescreens.

The ram timings look perfectly normal, and I have a fan on the rear exhaust for airflow.

I also found this thread from a guy who got the same mobo and found himself in blue screen hell.

I'm reluctant to ask for a refund because when it runs it's great for the price, but from my perspective this build seems like a horrifically unstable disaster.

If anyone can help, it will be hugely appreciated.

[fkerrx]

I've read that AMD CPUs need the RAM to be in unganged mode, but I'm not sure how to set that on this mobo's BIOS. Suggestions?

[autotech]

M.B. Intelligent Tweaker hit enter and go to,
DRAM Configuration hit enter then go to
DCT's Mode       set to ganged or unganged and yes amd procreeosr run better at unganged with really no visable speed decreases and it allows for higher overclock.

[Dark Mantis]

Hi

Please people list the STOP codes for the BSODs! These are the most helpful parts when they happen and will hopefully point you in the right direction.

[fkerrx]

==================================================
Dump File         : 022712-13665-01.dmp
Crash Time        : 2/27/2012 5:04:22 PM
Bug Check String  : APC_INDEX_MISMATCH
Bug Check Code    : 0x00000001
Parameter 1       : 00000000`76e56e3a
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`0000ffff
Parameter 4       : fffff880`073a2320
Caused By Driver  : win32k.sys
Caused By Address : win32k.sys+18adb9
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\022712-13665-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,480
==================================================

==================================================
Dump File         : 022712-13182-01.dmp
Crash Time        : 2/27/2012 4:54:00 PM
Bug Check String  :
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`0493c4f8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+4b16cc
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\022712-13182-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
==================================================

==================================================
Dump File         : 022512-22604-01.dmp
Crash Time        : 2/25/2012 2:45:22 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff880`0338fb60
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff800`028973ef
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\022512-22604-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,536
==================================================

==================================================
Dump File         : 022412-17706-01.dmp
Crash Time        : 2/24/2012 6:41:29 PM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`02b7be1c
Parameter 3       : fffff880`031a8a18
Parameter 4       : fffff880`031a8270
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+360e1c
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+360e1c
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\022412-17706-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,608
==================================================

==================================================
Dump File         : 022412-20326-01.dmp
Crash Time        : 2/24/2012 6:01:24 PM
Bug Check String  :
Bug Check Code    : 0x00000101
Parameter 1       : 00000000`00000031
Parameter 2       : 00000000`00000000
Parameter 3       : fffff880`02fd3180
Parameter 4       : 00000000`00000003
Caused By Driver  : cdd.dll
Caused By Address : cdd.dll+11f87
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\022412-20326-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,608
==================================================

==================================================
Dump File         : 022412-21512-01.dmp
Crash Time        : 2/24/2012 5:46:43 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\022412-21512-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,608
==================================================

==================================================
Dump File         : 022412-23649-01.dmp
Crash Time        : 2/24/2012 5:36:16 PM
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffff900`4074e968
Parameter 2       : 00000000`00000000
Parameter 3       : fffff960`00154b95
Parameter 4       : 00000000`00000005
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\022412-23649-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,608
==================================================

[fkerrx]

I'm starting to think it's cheap RAM, RAM settings in the BIOS, or not enough watts from the power supply...

[fkerrx]

Just verified it is due to the RAM overheating, loaded some Crucial Balistics and put a fan right on them and I could complete the 'windows experience index' test without BSOD 4 out of 5 times. So I put the g skill RAM back in with a huge cage fan blowing on my open case and I played TF2 for a bout an hour then, BSOD. I'm going to try some of the gigabyte tested RAM and another case fan.

[Arisen]

Update...

I sent the mobo back to Newegg and they sent me a replacement (same model). It's been running perfectly with no BSOD's for two days now. 

[Dark Mantis]

OK, good to hear that you managed to get it sorted out in the end.