Intermittent BSOD on new 'white box'

Welcome Aboard. Let us check your crash dumps.

► Symantec Network Security Intermediate Filter Driver

Code:

fffff800`00b9bbb8  fffff880`03f626c4Unable to load image \SystemRoot\system32\DRIVERS\SymIMv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SymIMv.sys
*** ERROR: Module load completed but symbols could not be loaded for SymIMv.sys
 SymIMv+0x36c4
fffff800`00b9bbc0  fffffa80`08733d50
fffff800`00b9bbc8  fffff880`03f67110 SymIMv+0x8110

It is the root cause of your issues, Norton internet security. It is hampering your internet performance a lot, too.
Uninstall it, use Microsoft Security Essentials - Free Antivirus for Windows

► ATI Display Driver:
[cdode]fffff800`00b9c238 fffff880`04a7b723Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
atikmdag+0x4f723[/code]
The installed one is very old.

Code:

lmvm atikmpag
start             end                 module name
fffff880`04400000 fffff880`04451000   atikmpag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed May 25 07:55:42 2011 (4DDC68A6)
    CheckSum:         00058CA5
    ImageSize:        00051000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get the updates from AMD Graphics Drivers & Software.

► Intel(R) 82579V Gigabit Network Connection driver

Code:

lmvm e1c62x64
start             end                 module name
fffff880`056e5000 fffff880`05740000   e1c62x64 T (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:        Thu Dec 01 04:39:31 2011 (4ED6B7AB)
    CheckSum:         0006396D
    ImageSize:        0005B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from http://downloadcenter.intel.com/.

► Intel(R) USB 3.0 eXtensible Host Controller Driver

Code:

lmvm iusb3xhc
start             end                 module name
fffff880`0560e000 fffff880`056d2000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Mon Dec 05 15:39:06 2011 (4EDC9842)
    CheckSum:         000C70D4
    ImageSize:        000C4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get update from http://downloadcenter.intel.com/
After making those changes, let us know the results.

pmshah said:

I have similar problems on the same motherboard. I got the latest drivers for USB 3 extensible host controller driver and the system stabilized for a while. However lately it has has gone totally berserk. It throws up bsod for a wide variety of files, you name it. I have 2 x 4gb corsair vengeance ram modules. I have ested both of them very thoroughly on the motherboard as well as on other systems. No faults at all. Recently I had upgraded my AV to Nod32 V 7.xxx. I even uninstalled it without any benefit.

BTW Intel's motherboard design or USB 2.0 AND USB 3 implementation sucks big time. Even with a single USB powered external drive connected to USB 2 or 3 port connectivity is not guaranteed. If I connect a second one then it is bound to crash the system. No problem with externally powered USB HDDs. I have another 7 year old Via CN700 mini-itx system which takes everything in its stride. I can connect 4 USB powered drives simultaneously and all connections are solidly stable.

I really do wonder if I make a blunder in buying an Intel motherboard in stead of an ASUS or AsRock one with nVidia chip set!

BSODs are similar to look at ... the blue screen with the white writings on it. Otherwise it is all different. Even if the bugcheck code is the same, the cause may/might/must be different. So one set of instructions will never be essentially applicable for you .... despite of hardware and other similarities.

If you want to get your issue debugged, start a new thread following the Blue Screen of Death (BSOD) Posting Instructions.