P67pro/2500k freezing issue

shabby

Diamond Member
Oct 9, 1999
5,782
45
91
My new system has been freezing at least once daily since i put it together, it consists of an asus p67pro/2500k and 8gb of corsair vengeance memory, everything is running at stock speeds.
At first the event viewer was hinting at logitech's sideshow plugin so i completely removed all logitech software but the crashing still continued. Next hint i got was an address space error upon bootup with some asus mobilink file, so i remove the ai suite of programs and all seemed well for the last 5 days until it crashed again an hour ago. This was happening with both 1203/1253 bios'.
Im going to reformat tomorrow and see if that solves anything, if its a hardware issue how do i pin point it?
 

shabby

Diamond Member
Oct 9, 1999
5,782
45
91
The screen just freezes, no reboot or bsod, i have to reset the machine. Drivers are all upto date.
 

Mugenx

Senior member
Apr 25, 2010
249
1
81
RAM. look at it's voltage and settings (factory) or one or two or more sticks is dying!
 

BathroomFeeling

Senior member
Apr 26, 2007
210
0
0
Can you list your full specs? How is the memory in BIOS, I mean 1600 with manual timings or 1333 and auto timings? Any LEDs light up on your mobo when it freezes?

Test your system in Safe Mode for a while, see if it crashes there.
 

shabby

Diamond Member
Oct 9, 1999
5,782
45
91
I'll try pulling one of the sticks out and see what happens, im not sure i want to be stuck in safe mode since it took 5 days for it to crash again. Every setting in the bios is stock/default, haven't noticed any led's during the crash since my case is closed.
 

mv2devnull

Golden Member
Apr 13, 2010
1,526
160
106
The screen just freezes, no reboot or bsod, i have to reset the machine. Drivers are all upto date.
So you mean that the OS, programs, and demain remain on? One frozen screenshot?


I've got something almost, but not quite, similar. Freezes after some usage. But, the cursor of the mouse is still moving. Occasionally some keys (Win-key) might work too, but not continuously. And eventually all input freezes. The only way out is to cut off power.

No observed freezes while running IBT or memtest86+.

I did flash to 1253. No help. I did remove Auzentech Forte soundcard. No help.

I did disable all energy saving options of Windows 7 and disabled Windows Defender that was simultaneously on with Avira antivirus tool. Now it took three evenings of usage before a freeze. This last freeze was while playing X3 Reunion. On freeze a (repeating) static sound started. That was yesterday.


Today, first boot froze on loading Windows. That had never happened before. Next boot was my first ever double-boot, no video, and no progress.

The memory led was on. Pressing MemOK inits testing, power cycles once, and reaches rapid blinking, then returns to solid led. Repeatably.

Memory was two sticks of Corsair CMV4GX3M1A1333C9, ie 2x4GB, in slots A2 and B2. Removing A2 and moving B2 to B1 allowed MemOK to succeed after multiple reboots.

I did restore Optimized Defaults, flashed to 1204, restored defaults, pulled out power cord and battery for several minutes (never touched battery of any board). Tried using both modules again, but failed, so am now running
with only one in A2 slot.

Haven't disabled C3/C6 (yet).

The more or less freezing system was in use for about seven evenings before today's solid memory error led.

Asus P8P67 Pro
i7-2600
Nvidia GTX460 1GB
SATA6G_1: 80GB Intel SSDSA2M080G2GC (GPT partitions)
SATA6G_2: 1TB Samsung F3 (RAID1 Array0)
SATA3G_3: 1TB Samsung F3 (RAID1 Array0)
SATA3G_4: 500GB ST3500630AS (RAID1 Array1)
SATA3G_5: 500GB ST3500630AS (RAID1 Array1)
SATA3G_6: LG GH22NS50 DVD
Seasonic X-650W
Marvell, JMicron, Fireware, Serial port, and HyperThreading disabled
Virtualization enabled
Windows 7 Home Premium 64-bit with UEFI boot
No overclocking of any sort


EDIT: The second memory module no longer functions even when put in alone. Conclusion: that particular module was so and so to begin with (did pass couple cycles of Memtest86+ and linpack) but has failed (at least by P8P67 Pro standards).
 
Last edited: