A crash while updating the BIOS is usually fatal! You're lucky to be able to boot into Windows at this point!
I'm concerned about your inability to run the memory test. Please run this free memory diagnostic and see what happens:
Link Removed - Invalid URL
You can also try Prime95 (it stresses the memory) - and it works inside of Windows. There's a link to it here:
Link Removed Try running all 3 tests in Prime95 (Blend, Small FFT's and Large FFT's) How fast each one gets errors (or doesn't) will give us some clues as to where the problem may lie (CPU, Memory controller, or RAM in most cases).
Memory settings one each stick of RAM is different (in some reports). Please go into the BIOS and reset it to default values - then post another set of the Seven Forums.zip reports.
If there isn't any hardware damage, then the following stuff may help:
You have a Linksys AE2500 wireless USB device. Win7 doesn't like these devices. Here's my rant on the subject:
I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
Your drivers are more recent, but we've still seen problems with these devices in Win7. Please test without the device to see if that helps to isolate the problem.
You have a problem device that appears leftover from AMD Overdrive. Please do the following:
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.
Please un install all AMD/ATI video stuff from Control Panel...Programs...Un install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed - Invalid URL (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed
If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.
If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.
The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
- Further info on BSOD error messages available at:
Link Removed
- Info on how to troubleshoot BSOD's (DRAFT):
Link Removed
- How I do it:
Link Removed
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
Code:
[FONT=lucida console]
AE2500w764.sys Mon Mar 28 20:22:08 2011 (4D912630)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
WmBEnum.sys Tue Jan 13 21:56:45 2009 (496D546D)
WmXlCore.sys Tue Jan 13 21:56:37 2009 (496D5465)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B)
nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C)
[/FONT]
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
BSOD BUGCHECK SUMMARY
Code:
[FONT=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081212-15834-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Aug 12 16:29:02.484 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:24.577
BugCheck DE, {2, fffff8a00ba9e2e8, fffff8a00ba9f2e9, 1a5b778c0}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xDE
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xDE_nt!PoIdle+52a
Bugcheck code 000000dE
Arguments 00000000`00000002 fffff8a0`0ba9e2e8 fffff8a0`0ba9f2e9 00000001`a5b778c0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\081212-34382-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Aug 12 16:23:53.353 2012 (UTC - 4:00)
System Uptime: 0 days 0:29:40.228
BugCheck 3B, {c0000005, fffff80001ebc617, fffff88008d0d140, 0}
Probably caused by : ntkrnlmp.exe ( nt!NtFreeVirtualMemory+287 )
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: firefox.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!NtFreeVirtualMemory+287
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`01ebc617 fffff880`08d0d140 00000000`00000000
BiosVersion = F4
BiosReleaseDate = 08/26/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]