Sign in with
Sign up | Sign in
Your question

Random BSOD

Tags:
  • Motherboards
  • RAM
  • Blue Screen
Last response: in Motherboards
Share
May 31, 2011 6:42:59 PM

Hi guys, i got random BSOD's when i am using my computer. I've already try using one stick of ram and swapping ram slots. Doesn't seems to work. I've tried memtest as well, i get no errors but I still get BSOD consistently.

Here is my specs:
Intel i7 2600k
Asus P8P67 Evo
G.Skill 8GB RipjawX 1600mhz 9-9-9-24
EVGA GTX 570 SC
OCZ Vertex 3 120gb
Corsair AX850

Thanks, in advance.

Louis

PS: Here is the minidump files that I've collected.
http://cid-8493fbf85f1f6f65.office.live.com/embedicon.a...

More about : random bsod

a c 105 V Motherboard
May 31, 2011 10:19:03 PM

Is the CPU overclocked?
m
0
l
May 31, 2011 10:20:04 PM

stock clock
m
0
l
Related resources
a c 105 V Motherboard
May 31, 2011 10:28:53 PM

Check for CPU temps using RealTemp 3.40

If for some reason the heatsink is loose, the CPU will overheat and result in BSODs as well as shutdowns. Monitor the voltages too. Too low a voltage will result in BSOD.
m
0
l
May 31, 2011 10:32:45 PM

well, my temps are normal idle at 2x and load at 7x. voltage are set in bios @ 1.2v. Any ideas what cause that to happen? i had bsod like every 5-10 minutes.
m
0
l
a c 105 V Motherboard
May 31, 2011 10:46:49 PM

I do realize that you are running at stock speeds. Read these regarding voltage:

http://www.tomshardware.com/forum/264113-29-intel-2600k
http://www.overclock.net/intel-cpus/921856-i7-2600k-vol...
http://www.evga.com/forums/tm.aspx?m=929933&mpage=1

Every CPU (even the same make and model) has slight differences and will behave differently at different speeds/voltages. The 1.2 volts may be at the borderline for your particular CPU/heatsink assembly. Try raising it in small increments of 0.050 volts and run the computer. Do not exceed 1.350 volts even though Intel says something like 1.502 volts.
m
0
l
a c 130 V Motherboard
June 1, 2011 12:24:21 AM

check out BlueScreenView.

Lets you get the stop message and post it. This may help us
http://www.nirsoft.net/utils/blue_screen_view.html

EDIT

I ran your mini-dumps

a few of this

CRITICAL_OBJECT_TERMINATION

Technical Information:

*** STOP: 0x000000f4 (0x0000000000000003, 0xfffffa8009abab30, 0xfffffa8009abae10,
0xfffff800033de240)

*** ntoskrnl.exe - Address 0xfffff800030d5f00 base at 0xfffff80003064000 DateStamp

and one

KERNEL_DATA_INPAGE_ERROR

Technical Information:

*** STOP: 0x0000007a (0xfffff6fc4000a980, 0xffffffffc0000056, 0x000000017d4f7860,
0xfffff8800153069c)

*** Ntfs.sys - Address 0xfffff8800153069c base at 0xfffff8800143f000 DateStamp

I would run a hard drive check just in case.
m
0
l
a b V Motherboard
June 1, 2011 12:26:56 AM

If memtest runs fine but you still bsod in windows then drivers are a likely culprit, or maybe you have a hardware failure in sound or video or network, i.e. stuff not running during memtest. I'd update all drivers and also see if that BSOD references anything specific
m
0
l
June 1, 2011 4:04:56 AM

nukemaster: how do i run a hard drive check?

notherdude: i had all the latest driver for all hardware.
m
0
l
a c 130 V Motherboard
June 1, 2011 8:51:45 PM

goto the maker of your hard drives website and get there tool for drive diagnostics. Run short and long test...DO NOT WRITE ZERO's TO DRIVE as that erases it.

The only thing i see is a firmware update, but that has to be applied on a different computer.

http://www.ocztechnology.com/ssd_tools/OCZ_Vertex_3,_Ve...

You can run chkdsk /f . on next boot the computer will check for file system errors.
There is a /r command, but i think the drive should be checking it self in the background anyway.

As a last shot, maybe you need to check the cable.

I will post if i think of anything else you can try
m
0
l
June 3, 2011 4:48:07 AM

I've the latest firmware and I've checked all the cables.. No luck, but if I switched to sata 2 seem to be fine.. Could there be any possibility that it's a faulty sata 3 port?
m
0
l
!