Windows 7: Getting constant BSODs

MilesEdgeworth · 17 Jun 2011

Started getting them like a month ago, and am getting them about 1-2 times a day, and every once in a while on startup. It's almost always during gaming, especially while downloading updates.

Tried the recovery options, System Restored to a point before the BSODs were happening, and even re-installed Windows, all to no avail.

Specs are:
- Windows 7 Ultimate x64 (Retail version, only OS ever on the system)
- AMD Phenom II x4 965 CPU
- Gigabyte GA-770T-USB3 Board
- Nvidia GeForce GTX 465 GPU
- 2x 2GB DDR

jcgriff2 · 17 Jun 2011

Hi -

The most recent BSOD shows OS corruption -

Code:

0: kd> lmnt
start             end                 module name
fffff800`00bb0000 fffff800`00bba000   ____fffff80000bb0000 ġ⒐          Sat Feb 05 07:21:45 2011 (4D4D40D9)
fffff800`02c1e000 fffff800`031fa000   nt       ġ⒐          Sat Apr 09 00:14:44 2011 (4D9FDD34)
fffff800`031fa000 fffff800`03243000   ___      ġ⒐          Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00cc0000   ____fffff88000c00000 ġ⒐          unavailable (00000000)
fffff880`00cc0000 fffff880`00cd0000   ____fffff88000cc0000 ġ⒐          unavailable (00000000)
fffff880`00cd0000 fffff880`00cea000   ____fffff88000cd0000 ġ⒐          unavailable (00000000)

It should look like this - with driver names -

Code:

2: kd> lmnt
start             end                 module name
fffff800`00bc1000 fffff800`00bcb000   kdcom    kdcom.dll    Sat Feb 05 07:21:45 2011 (4D4D40D9)
fffff800`02c15000 fffff800`031f1000   nt       ntkrnlmp.exe Sat Apr 09 00:14:44 2011 (4D9FDD34)
fffff800`031f1000 fffff800`0323a000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00c2a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00c2a000 fffff880`00c35000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00c35000 fffff880`00c6f000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)

Run memtest86+ - http://www.techsupportforum.com/foru....php?p=2863029

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061611-32463-01.dmp]
*** WARNING: Unable to verify timestamp for g?
*** ERROR: Module load completed but symbols could not be loaded for g?
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri Jun 17 00:26:25.065 2011 (GMT-4)
System Uptime: 0 days 0:02:55.797
*** WARNING: Unable to verify timestamp for g?
*** ERROR: Module load completed but symbols could not be loaded for g?
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : g?_ ( nt+70700 )
BUGCHECK_STR:  0xc2_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000C2
Arguments 00000000`00000007 00000000`00001097 00000000`00000000 fffff8a0`023b6948
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061611-35209-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri Jun 17 00:14:44.182 2011 (GMT-4)
System Uptime: 0 days 0:00:33.914
Probably caused by : Wdf01000.sys ( Wdf01000!imp_WdfSpinLockRelease+f6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_Wdf01000!imp_WdfSpinLockRelease+f6
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02c8c9cd 00000000`00000000 ffffffff`ffffffff
BiosVersion = F3
BiosReleaseDate = 05/14/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061611-38672-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu Jun 16 04:06:07.693 2011 (GMT-4)
System Uptime: 0 days 18:10:15.441
Probably caused by : ndis.sys ( ndis! ?? ::FNODOBFM::`string'+636e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_ndis!_??_::FNODOBFM::_string_+636e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 05/14/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061511-34133-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Wed Jun 15 01:58:32.642 2011 (GMT-4)
System Uptime: 0 days 0:06:35.000
Probably caused by : ataport.SYS ( ataport!PortListRemoveRequest+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0x1E_ataport!PortListRemoveRequest+22
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 05/14/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
by jcgriff2     
 
       J. C. Griffith, Microsoft MVP 
 
 https://mvp.support.microsoft.com/profile/Griffith 
 
 www.sysnative.com
 
 www.jcgriff2.com 
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

MilesEdgeworth · 17 Jun 2011

Downloaded, and burned the iso to a CD. Ran the test, and it comes back as "Pass complete, no errors"

MilesEdgeworth · 18 Jun 2011

Update, no blue screen today, but it did restart on it's own twice, both times were during gaming again. Should I run the app again, or give any other information?

zigzag3143 · 18 Jun 2011

Quote: Originally Posted by MilesEdgeworth

Downloaded, and burned the iso to a CD. Ran the test, and it comes back as "Pass complete, no errors"

Memtest needs to be run for an extended amount of time (usually 6-8 passes) before you can truly eliminate memory.

MilesEdgeworth · 18 Jun 2011

Quote: Originally Posted by zigzag3143

Memtest needs to be run for an extended amount of time (usually 6-8 passes) before you can truly eliminate memory.

Oh okay, my fault. I only let it run for two passes, I will let it run a bunch more, thanks.

MilesEdgeworth · 18 Jun 2011

Ran Memtest again before I left the house. Just got back, and it's found over 20 million errors so far over 5 hours, and it's still going. Should I just let it continue?

zigzag3143 · 18 Jun 2011

Quote: Originally Posted by MilesEdgeworth

Ran Memtest again before I left the house. Just got back, and it's found over 20 million errors so far over 5 hours, and it's still going. Should I just let it continue?

Kill it, its either the memory or mobo. test one stick at a time till you find a good one then test each mobo slot.

MilesEdgeworth · 19 Jun 2011

Stick 1 in Slot 1 - 8 passes, No errors
Stick 2 in Slot 1 - 8 passes, No errors
Stick 1 in Slot 2 - 0 passes before errors started
Stick 2 in Slot 2 - 5 passes before errors started

So, I assume the problem is with my second ram slot?

zigzag3143 · 19 Jun 2011

Quote: Originally Posted by MilesEdgeworth

Stick 1 in Slot 1 - 8 passes, No errors
Stick 2 in Slot 1 - 8 passes, No errors
Stick 1 in Slot 2 - 0 passes before errors started
Stick 2 in Slot 2 - 5 passes before errors started

So, I assume the problem is with my second ram slot?

Looks like it

Windows 7: Getting constant BSODs

Getting constant BSODs problems?