Multiple BSOD

[Ross]

Hi,

I built a new PC on Friday and ever since, I have been plagued with the dreaded BSOD.

The specification is:

Intel Core i7-2600K 3.40GHz
MSI ATI Radeon HD 6870 OC HAWK 1024MB GDDR5
Asus P67 Sabertooth Intel P67 ** B3 REVISION **
OCZ Agility 3 60GB 2.5" SATA-3 Solid State Hard Drive
Corsair TX 750W ATX SLI Compliant Power Supply
Samsung SpinPoint F3 1TB SATA-II 32MB Cache - OEM (HD103SJ) x 3
Corsair XMS3 8GB DDR3 PC3-12800C9 1600MHz

The BSOD frequecy increased when I set the RAM to 1600MHz, so I have dropped it down to 1333MHz and it is still happening, but not as frequently.

The OS is Windows 7 Pro x64.

Thanks in advance.

Regards,

Ross

 

[Ross]

This is still causing an issue at 1333MHz. I'll try running Memtest86+ when I get home to see if this shines any light on the issue.

 

[mgorman87]

Start off by removing AVG. It was the cause of one of your blue screens
AVG - Download tools

Replace it with Microsoft Security Essentials

Your Belink WiFi adapter is also not compatible with Windows 7. This might be causing some issues as well

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
2. Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

If all tests pass then I would like for you to enable driver verifier - http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 17:17:11.060 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:13.950
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
BUGCHECK_STR:  0xC5_2
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID:  X64_0xC5_2_nt!ExAllocatePoolWithTag+53d
BiosReleaseDate = 03/02/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 17:15:15.993 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:39.883
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteScb+108
BiosReleaseDate = 03/02/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 17:09:42.227 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:49.007
Probably caused by : ntkrnlmp.exe ( nt!CcGetVirtualAddressIfMapped+7c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
FAILURE_BUCKET_ID:  X64_0x34_nt!CcGetVirtualAddressIfMapped+7c
BiosReleaseDate = 03/02/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 17:08:11.961 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:02.851
*** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+364d )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  avgnsa.exe
FAILURE_BUCKET_ID:  X64_0xD1_AVGIDSFilter+364d
BiosReleaseDate = 03/02/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 17:00:27.111 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:26.001
Probably caused by : ntkrnlmp.exe ( nt!CcWriteBehind+1d1 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!CcWriteBehind+1d1
BiosReleaseDate = 03/02/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Mon May 23 13:04:33.283 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:17.204
Probably caused by : memory_corruption ( nt!MmUnlockPages+3eb )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WinSAT.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MmUnlockPages+3eb
BiosReleaseDate = 03/02/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Ross]

Thanks for the response.

I have removed AVG and the Belkin adaptor. The Belkin adaptor was only a temporary measure, as my old d-link did not fit in my new motherboard (due to the sheilding on the motherboard) and luckily my new adaptor has turned up today, so I will be replacing it asap.

I am currently running Memtest86+, so I will post back when that has completed.

Thanks for your help

 

[Ross]

Just an update.

I ran memtest86+ twice (10 passes @ 1333MHz & 8 passes @ 1600MHz) and all 4 modules have passed each time but I am still convinced 1 of the ram modules are faulty, as twice now I have removed the same module and the computer has worked perfectly. I ran the single module on its own and I have suffered the BSOD.