Bluescreens on newly built system

[begj]

Hi, i keep getting bluescreens on my newly built computer.
--
Intel core i7 2600k
MSI GTX 560 ti Twin Frozr II
H70
CORSAIR HX 750W ATX12V 2.2 / EPS12V
SAMSUNG SPINPOINT F3 1TB SATA/300 7200RPM 32MB
CORSAIR 8GB DDR3 XMS3 VENGEANCE PC3-12800 1600MHZ CL8 (2X4GB)
OCZ VERTEX 3 2.5" 120GB SSD SATA/600 MLC
Asus P8P67 B3 Pro
some cheap ass cd-rom (says super ritemaster - speed plus, on the front)

Windows 7 Ultimate 64-bit - Full Retail Version.
Age of system: less than 1 month
What is the age of OS installation: Last format was on 27. June.

 

[zigzag3143]

Hi, i keep getting bluescreens on my newly built computer.
--
Intel core i7 2600k
MSI GTX 560 ti Twin Frozr II
H70
CORSAIR HX 750W ATX12V 2.2 / EPS12V
SAMSUNG SPINPOINT F3 1TB SATA/300 7200RPM 32MB
CORSAIR 8GB DDR3 XMS3 VENGEANCE PC3-12800 1600MHZ CL8 (2X4GB)
OCZ VERTEX 3 2.5" 120GB SSD SATA/600 MLC
Asus P8P67 B3 Pro
some cheap ass cd-rom (says super ritemaster - speed plus, on the front)

Windows 7 Ultimate 64-bit - Full Retail Version.
Age of system: less than 1 month
What is the age of OS installation: Last format was on 27. June.

No DMP files uploaded try this method





To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[begj]

Oh, i just unchecked auto restart and changed info header to small memory dump, what now?
i zipped the folder and added to OP

OPS: i just saw i had added the "Windows_NT6_BSOD_v3.03_jcgriff2_" .exe instead of the folder i have updated the zip file in OP.

 

[zigzag3143]

Oh, i just unchecked auto restart and changed info header to small memory dump, what now?
i zipped the folder and added to OP

OPS: i just saw i had added the "Windows_NT6_BSOD_v3.03_jcgriff2_" .exe instead of the folder i have updated the zip file in OP.

Pool Corruption (memory) caused yb an un-named driver. Please run thee two tets


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[begj]

I've done the Memok test, i've even changed the position of the ram, they all work when i have them on A1 and B1, however they didn't pass intel burn thest on high when they were both on A2 and B2.
After i switched to A1 and B1 there have been less crashes, so i doubt it is the ram, can there be something else?