BSODs Unaffiliated with any task

[Griswel]

Windows 7 64 bit installed on system when I bought it around July 2011. Rare BSODs became uncommon a few weeks ago, now I do nearly anything and I BSOD, sometimes right back into a BSOD on reboot. I updated drivers, uninstalled MovieMaker which seemed to be related in the event log. Still BSODs left and right, especially when doing anything more intense than web browsing. Never reinstalled windows on this system.

I ran the tools and zipped up the resulting files. I think I have done this correctly.

Any help would be appreciated.

 

[JaidynM]

Test your RAM using Memtest86+. Let it run until 6-8 passes have completed or errors have been found.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Enable Driver Verifier. Enabling this should hopefully crash your system and then point to the faulty driver that is causing problems. However before you do, it is advised that you create a system restore point and backup first.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[mgorman87]

Do as suggested by JaidynM and report back the results

nusb3hub.sys Fri Nov 20 05:15:57 2009 (4B066C5D)

Your NEC Usb 3.0 drivers also cause about four of the crashes. See if you can find a newer driver from your motherboard manuf. site

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Apr  9 18:07:14.776 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:52.962
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6061 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_411_nt!_??_::FNODOBFM::_string_+6061
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Apr  8 19:40:11.839 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:18.539
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Apr  8 22:24:25.489 2012 (UTC - 4:00)
System Uptime: 0 days 2:43:10.675
Probably caused by : memory_corruption ( nt!MiPerformFixups+80 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiPerformFixups+80
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Thu Apr  5 23:24:25.526 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:46.352
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )
BUGCHECK_STR:  0x4E_2
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Fri Apr  6 08:00:47.796 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:27.982
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35698 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  XSrvSetup.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35698
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Thu Apr  5 21:07:24.074 2012 (UTC - 4:00)
System Uptime: 5 days 1:24:11.893
*** ERROR: Module load completed but symbols could not be loaded for fileinfo.sys
Probably caused by : fileinfo.sys ( fileinfo+2961 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_fileinfo+2961
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Thu Apr  5 21:18:27.634 2012 (UTC - 4:00)
System Uptime: 0 days 0:04:32.804
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Thu Apr  5 22:13:48.435 2012 (UTC - 4:00)
System Uptime: 0 days 0:42:01.246
Probably caused by : win32k.sys ( win32k+65f7c )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mcagent.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k+65f7c
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Mar 31 18:57:07.156 2012 (UTC - 4:00)
System Uptime: 7 days 4:18:36.814
*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys
Probably caused by : nusb3hub.sys ( nusb3hub+10ce0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nusb3hub+10ce0
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Mar 24 12:16:25.917 2012 (UTC - 4:00)
System Uptime: 9 days 14:18:53.218
*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys
Probably caused by : nusb3hub.sys ( nusb3hub+10ce0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nusb3hub+10ce0
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 25 20:44:40.946 2012 (UTC - 4:00)
System Uptime: 6 days 23:59:34.153
*** WARNING: Unable to verify timestamp for nusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3hub.sys
Probably caused by : nusb3hub.sys ( nusb3hub+10ce0 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nusb3hub+10ce0
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 15 20:43:11.299 2012 (UTC - 4:00)
System Uptime: 2 days 2:09:28.691
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  swtor.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c96
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Apr  9 19:01:26.513 2012 (UTC - 4:00)
System Uptime: 0 days 0:10:34.684
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+384a0 )
BUGCHECK_STR:  0x1a_888a
PROCESS_NAME:  mcagent.exe
FAILURE_BUCKET_ID:  X64_0x1a_888a_nt!_??_::FNODOBFM::_string_+384a0
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Apr  9 18:44:03.666 2012 (UTC - 4:00)
System Uptime: 0 days 0:16:42.837
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+c4 )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  McSvHost.exe
FAILURE_BUCKET_ID:  X64_0x19_20_nt!ObpCloseHandleTableEntry+c4
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Apr  9 18:16:01.521 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:51.707
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Apr  8 23:22:04.825 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:58.636
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  steam.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4
BiosReleaseDate = 03/09/2011
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-870A-UD3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[Griswel]

Well, this feels foolish, but even though I tried a couple DVDs and a CD-Rom I can't get the system to boot to the Memtest. I checked the CMOS, and it was already set to go to CD first, though I switched to non-2.2tb HDs just in case. With the CD I saw the drive light go on, but it still boots to the HD and Windows. I'll see if I can't find an empty memory stick or empty one, but I do not see what I'm doing wrong I right-clicked the iso, opened with Disk Image Burner, burned the disk, and no luck.

The CD has the readme.txt file and a Boot directory. The boot directory has boot.cat and memtest.img.

I feel like I'm tripping over the starting line.

 

[JaidynM]

If you go into your BIOS settings, there is an option to change the boot order. Change it so that the CD will boot first and the other drives will not boot at all.

You might also want to try reburning the CD.

 

[Griswel]

If you go into your BIOS settings, there is an option to change the boot order. Change it so that the CD will boot first and the other drives will not boot at all.

You might also want to try reburning the CD.

I tried a DVD as well, no go.

Oddly, I now have boot from CD first and the second and third options "disabled" and yet I boot from the HD. There is a setting above these three which is something like "HD Boot Priority" and all it lets me do is move "other bootable device" or my HD up or down from first to second position. There is no "off".

I can also use the "Boot Menu" by hitting F12 instead of Del for the CMOS menu. Three times I did this, I chose first boot device "CD-ROM" and three times I booted instead from the HDD. I could pop the case open and disconnect the HDD but I'm not quite there yet

Far fewer BSODs in the meantime, hours of surfing and then more hours of SWTOR last night and only having the thing sitting overnight cause a BSOD.

I'll work on drivers for the MB from Gigabyte for now and see how much of my problem I can solve that way. Just wanted to say I'm not ignoring the advice you've offered, which I appreciate, but I'm not making much progress on it either.

EDIT - Finally thought to check the MB box and used the Gigabyte disk to upgrade those drivers, also PSI key was not working, whatever that is, so I clicked on the Windows OS message and followed that instruction. Still working on memory, I guess, and seeing how many BSODs I still have.

 

[JaidynM]

In that case, you might want to give the USB Memtest a shot.

Can you upload the new dump file?

 

[Griswel]

In that case, you might want to give the USB Memtest a shot.

Can you upload the new dump file?

Here's the new dump file. Hope I wasn't supposed to clear the old stuff...

 

[JaidynM]

Okay, we'll try getting Memtest to run before we address the new dump. Try putting it on a USB and see if you can boot it then.

 

[Griswel]

Okay, we'll try getting Memtest to run before we address the new dump. Try putting it on a USB and see if you can boot it then.

Ordered a new flashdrive to install the system on, but ran the Windows memory check in the meantime because heck, it takes 8 minutes, why not? Well, the third time I ran it the report came back that there were errors. So I ordered new memory. The Windows report was non-specific, but at this point it's worth it to just replace the memory and hope that solves the problem. I should have it later this week.

Assuming that the new memory solves the memory-related BSODs, is there anything else I ought to do? I think all my drivers are up to date now.

 

[JaidynM]

Assuming it does solve all your BSODs, you still have a couple of drivers to update.

The following drivers need to be updated:

AtiPcie.sys  Wed May 06 01:00:22 2009
gdrv.sys     Fri Mar 13 14:22:29 2009

These drivers can be found by searching them in Google and then finding the associated software or driver. Finally, find the latest version of this driver or software and download and install it. Some of the drivers may also be found here (if the driver says 'Windows Update' simply make sure all Windows Updates are installed).

You should also update any other drivers you can think of including graphics, audio, chipset, SSD etc.

You should also make sure all Windows updates are installed.