New Build, several BSOD's - Hardware & Software

I not long ago built a new gaming computer, the specs are as follows: - ASUS P7H57D-V EVO ATX Motherboard - Intel Core i5 750 - 2x2GB DDR3 1333MHz Crucial Ballistix RAM - HIS ATi Radeon HD 5770 1GB - Samsung F3 1TB SATA HD103SJ - Samsung SH-S233 DVD-RW - Windows 7 Professional 64bit Over the past couple of months I've had this computer, I have had several BSOD's. - During setup, the part where I enter my username etc, it BSOD'd, but restarted too quick for me to catch the message. - One BSOD which I think was BAD_POOL_HEADER but I can't quite remember. - Few days ago got the BSOD "A clock interrupt was not received on a secondary processor" - Today got two BSOD's "SYSTEM_SERVICE_EXCEPTION", both times occurred while watching a video. I have not overclocked anything on this system (Everything is on stock configuration) and AFAIK my drivers are updated. Please help.

Restart pc and while booting press f8 and shut down the auto restart in the bios (so you can read the bsod) Write it down and post it here.

I have the restart on BSOD disabled, I did that when setup finished. This is the report from WhoCrashed: [QUOTE]On Sun 21/03/2010 20:18:07 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D1F6DD, 0xFFFFF88009DE0130, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\032110-10124-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Sun 21/03/2010 20:13:10 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F47B9B, 0xFFFFF88009376080, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\032110-9999-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. On Fri 19/03/2010 08:08:18 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003163180, 0x2) Error: CLOCK_WATCHDOG_TIMEOUT Dump file: C:\Windows\Minidump\031910-13150-01.dmp file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time. [/QUOTE] EDIT: Also, I can't seem to replicate the BSOD's. They happen randomly.

BAD_POOL_HEADER indicates that a pool header is corrupt. SYSTEM_SERVICE_EXCEPTION indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. CLOCK_WATCHDOG_TIMEOUT indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. All 3 could be a RAM or CPU issue.

Would it be a good idea to test the RAM with MemTest86+ and the CPU with Prime95? (Or is there better software?)

Its the RAM. Always is with new builds.

[QUOTE=SteeleCratos;20886184]Always is with new builds.[/QUOTE] Hope it didn't hurt when you pulled that out of your ass.

I entered the RAM timings into the BIOS (Was on Auto before) and also discovered that the RAM was being run at 1.55v instead of 1.65v, so I manually set that. Perhaps that was the cause of the problems?

Don't up the voltage on your RAM unless you actually know what you're doing. I'd try removing 1 stick and test it, then do the other one.

[QUOTE=alphaspida;20894686]Don't up the voltage on your RAM unless you actually know what you're doing. I'd try removing 1 stick and test it, then do the other one.[/QUOTE] Crucial website says the RAM runs at 1.65v