New
#1
Frequent BSOD on new build W7 PC
Okay, hopefully someone can shed some light on a number of bsod I've been having with a new build PC.
Specs below:
OS
Windows 7 Home Premium 64 Bit
CPU
AMD Phenom II X6 Six Core 1055T 2.8ghz
Motherboard
Gigabyte GA-880GM-UD2H AMD 880G DDR3
Memory
OCZ Gold 2GB DDR3 PC3-106666C9 1333MHZ x4
Graphics Card(s)
MSI ATI Radeon HD 5850
Hard Drives
WD Caviar Black 1TB Sata
PSU
550W Coolermaster GX550
Case
OCUK EZCool NA 705 Case
Cooling
Arctic Cooling Freezer 7 Pro v2.1 (CPU)
In the space of 2-3 hours tonight, I've had no less than 7 BSODs, all roughly within 20-30 minutes of one another. They've happened when the system has been idle, or when trying to play blu ray via arcsoft TotalMedia Theatre 5. The system was built yesterday, we put all W7 updates on it, updated drivers etc. etc with no problems, although I'm not sure how long the system was on before we were restarting for updates etc. We did have a lot of problems initially even trying to install Windows 7 though - it kept complaining about missing files (tried 2 windows disks both legit) - eventually we switched the memory setting in the bios from ganged to unganged and that let us install windows, clonedvd and microsoft office without any issues.
Tonight I installed Total Media Theatre which also installed Total Media Server. I have the exact same program running on my other PC (no bsod) with W7 although admittedly my other PC is older. Also stuck on 3d Mark 06.
Began to run memory test, receiving crazy error totals (40,000+ errors) although memory is brand new? We will probably have to start taking out sticks of memory to test if there's a bad one, but in the meantime I thought it'd be worthwhile having someone check the dmp files. I've quickly looked at them in BlueScreenView and they all point to ntoskrnl.exe with the exception of the latest dump, which cites win32k.sys - did a bit of googling but there seems to be no real info on ntoskrnl although I'm led to believe it's really just a generic error if windows doesn't understand what's causing the problem.
Oldest driver in the dmps seems to be secdrv.sys (2006) but this is present on my other PC so I doubt that's causing the problem.
It looks to me like there's probably an issue with the memory, so I'll look at that next, but if there's any info to be gained from the .dmp files I'd be really grateful to hear it!
Many thanks.
Quote