New BSOD

[stumpedplshelp]

So over the passed week I have replaced my DFI Lanparty MB with an Asus MB. I stressed tested the ram and CPU again and both passed every thing I threw at them. My rig has bee running rock solid for about 4 days now and then BAM a BSOD. As far as I know all of my drivers and windows have been updated completely. Bios is up to date and all hardware has been trested. Can anyone tell wtf caused this BSOD?

 

[ttran]

I couldn't see much from the minidump file that you uploaded
Please enable Driver verifier:
http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.031\062810-17300-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Mon Jun 28 22:09:10.536 2010 (UTC + 7:00)
System Uptime: 0 days 1:06:05.800
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, b8, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )

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