BSOD on brand new build, please advise

**Chinaguy** · 08-19-2012

Hello everyone,
I just finished with a brand new custom built computer, and it's BSOD'd on me twice. The first time borked Windows so hard that it messed with the MBR and I had to use gparted to get it all ironed out so that I could reinstall. The second time wasn't so fatal so I have all the relevant information on it. As I am not fluent in C, I was hoping some of the fine folk of this forum could help me iron this problem out.Seven Forums JARROD-PC.zip

**usasma** · 08-19-2012

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

Intel, Marvell and ASMedia (?USB 3.0) storage drivers date from 2011 - they need updating.

You should install drivers for this device (most likely a C-Media Electronics Inc/ASUS Xonar Audio Device):

Multimedia Audio Controller PCI\VEN_13F6&DEV_8788&SUBSYS_835D1043&REV_00\4&3829F950&0&08F0 The drivers for this device are not installed.

Please un-install AICharger as apps of this type have been having BSOD's recently. Feel free to reinstall it (and test it) after the system has been stabilized.

Network drivers (wired) date from 2009, please update them also.

If the above things don't fix it, then try uninstalling Comodo Internet Security. Then turn on the Windows Firewall and install a free antivirus for testing purposes ( Free AntiVirus )

Analysis:

The following is for information purposes only.

Code:

**************************Sun Aug 19 07:33:36.465 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081912-16707-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:0 days 5:57:54.262
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck Code: BugCheck 128, {fffff8000325e1d0, 2, 0, fffff80003426380}
Probably caused by :ntoskrnl.exe ( nt+7f1c0 )
BugCheck Info: WORKER_THREAD_RETURNED_WITH_BAD_IO_PRIORITY (128)
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x128
CPUID:        "Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed:3300
  BIOS Version                  2104
  BIOS Release Date             08/03/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:

The following is for information purposes only. Any drivers in red should be updated.

Code:

**************************Sun Aug 19 07:33:36.465 2012 (UTC - 4:00)**************************
intelppm.sys        Mon Jul 13 19:19:25 2009 (4A5BC0FD)
RTL8187.sys         Wed Dec  9 04:16:39 2009 (4B1F6AF7)
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys          Mon Aug  2 22:47:59 2010 (4C57835F)
ICCWDT.sys          Wed Aug 18 04:27:45 2010 (4C6B9981)
tap0901.sys         Thu Aug 19 18:07:59 2010 (4C6DAB3F)
AsIO.sys            Mon Aug 23 21:53:02 2010 (4C7325FE)
ElbyCDIO.sys        Thu Dec 16 17:58:13 2010 (4D0A9985)
e1c62x64.sys        Wed Jul 20 12:37:53 2011 (4E270461)
HECIx64.sys         Mon Aug 15 13:29:24 2011 (4E495774)
mvxxmm.sys          Mon Sep 19 07:31:37 2011 (4E772819)
mvs91xx.sys         Mon Sep 19 07:31:51 2011 (4E772827)
mv91cons.sys        Mon Sep 19 07:36:08 2011 (4E772928)
ASUSFILTER.sys      Tue Sep 20 11:46:33 2011 (4E78B559)
iaStorF.sys         Wed Oct 12 16:28:40 2011 (4E95F878)
iaStorA.sys         Wed Oct 12 16:29:51 2011 (4E95F8BF)
hiber_iaStorA.sys   Wed Oct 12 16:29:51 2011 (4E95F8BF)
dump_iaStorA.sys    Wed Oct 12 16:29:51 2011 (4E95F8BF)
asmtxhci.sys        Wed Nov  2 23:00:22 2011 (4EB203C6)
asmthub3.sys        Wed Nov  2 23:00:32 2011 (4EB203D0)
inspect.sys         Mon Dec 19 13:48:52 2011 (4EEF8714)
cmderd.sys          Sun Mar 11 16:46:00 2012 (4F5D0F08)
cmdhlp.sys          Sun Mar 11 16:46:18 2012 (4F5D0F1A)
cmdguard.sys        Sun Mar 11 16:47:16 2012 (4F5D0F54)
AiCharger.sys       Thu Mar 22 04:07:51 2012 (4F6ADDD7)
nvhda64v.sys        Wed Apr 18 13:07:54 2012 (4F8EF4EA)
nvlddmkm.sys        Tue May 15 03:35:36 2012 (4FB20748)

**Chinaguy** · 08-20-2012

Ok. I've updated everything that I possibly can. I'll take a look some more at the links you posted to be sure though. Do you know of a way to do a good stress test to see if the system has stabilized with the new drivers?

**usasma** · 08-20-2012

Driver Verifier is a good test to see if the drivers are stable - but running it on all drivers will slow down your system.

I'd suggest just waiting to see if this has fixed the BSOD's. If it hasn't, then we can move on to looking at more things.

**Chinaguy** · 09-20-2012

Sorry for the long delay in repy. Turns out the issue was memory instability. The vendor I built this machine from supplied me with initially 3 kits of ram to populate 8 slots... and the kits didn't match. After much bs from the vendor, he sent me 1 kit of ram, of which one stick is bad. In any case, of the two that are working, I have them installed and the system is solid as a rock. Eventually the vendor will supply me with the 32gb of ram, but I have him running scared because I keep making his tech people look bad. LOL

BSOD on brand new build, please advise

LinkBack

Thread Tools

Search Thread

BSOD on brand new build, please advise

Re: BSOD on brand new build, please advise

Re: BSOD on brand new build, please advise

Re: BSOD on brand new build, please advise

Re: BSOD on brand new build, please advise

Similar Threads

[BSOD] BSOD with STOP 0x0000001A - potential hardware issue - please advise

[BSOD] BSOD on Brand New custom build Compuer

[BSOD] BSoD BRAND NEW SYSTEM BUILD - POSSIBLE HARDWARE FAULT???

BSOD on brand new custom build.

My problems started with BSOD!! Please Advise

Visitors found this page by searching for:

Tags for this Thread

Posting Permissions