Blue Screen - can't find a reason...

[latzko]

I've recently bought a decent PC and I keep getting blue screen like once a day.
Set up is next:
I5 2500k 3.3GHz
Gigabyte Z68X-UD3H-B3
2x 4GB 1600GHz (working on 1333GHz) Kingstone
120GB Patriot Pyro
2TB WD Green
775 Thermaltake Toughpower
MSI GTX560-ti Hawk

It doesnt happen in any particual time, happened to me while playing and also while away from PC. I did some googling, found out that SSD might be causing problems when coming out of sleep/hibernate. Turned all sleep/hibernate and power saving options and it's still happening. I've seen also that it might be a turbo boost from my proc causing the problem... Anyone has any thoughts?
Thanks for reading... :]

[DeltrusDisc]

Please post either a picture of the BSOD or the code from it.

If you have neither of those, go to your event viewer and look up your most recent critical event, as that would likely be the BSOD.

[latzko]

Uploaded with ImageShack.us

Which one should I be looking at? Or doing what... I'm new to errors and W7...

[DeltrusDisc]

Hey, you're close, don't worry. Go up to the "custom views" folder and that should likely only have 1 option under it "administrative events."

Find one that is critical level and then post the information from general and details, and under details open up the '+system' spot and some more information should appear, copy and paste that here and that should help us figure out what the issue is.

[latzko]

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2011-11-07T11:17:33.206413500Z

EventRecordID 6524

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Vlatkovic

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

Thanks for assissting btw... much appreciated... :]

[DeltrusDisc]

Looks very similar to my old BSOD codes...

Do you do much overclocking/voltage tweaking? And if so, what kind of CPU do you have?

In fact, I should have asked for this information in the first place, please post all of the information you know about your computer, most importantly:

CPU
Mobo
GPU
PSU
RAM
HDD/SSDs
OS installed

[latzko]

I've posted in the first main thread, but ok.
Intel I5 2500k 3.3GHz
Gigabyte Z68-UD3H-B3
MSI GTX560-TI Hawk
ThermalTake Tough Power XT 775W
WD 2TB Green HDD / Patriot Pyro 120GB Sata3 SSD
2x 4GB Kingstone 1600MHz (working on 1333MHz)
Windows 7 professional

As you can see by the RAM, nothing is overclocked. Everything is as bought. 2weeks old now...

[DeltrusDisc]

I've posted in the first main thread, but ok.
Intel I5 2500k 3.3GHz
Gigabyte Z68-UD3H-B3
MSI GTX560-TI Hawk
ThermalTake Tough Power XT 775W
WD 2TB Green HDD / Patriot Pyro 120GB Sata3 SSD
2x 4GB Kingstone 1600MHz (working on 1333MHz)
Windows 7 professional

As you can see by the RAM, nothing is overclocked. Everything is as bought. 2weeks old now...

Sorry, just realized that. >_<

I think I've been in too many threads this morning. ;p *needs to drink more coffee*

I'm really wondering why you're having these issues now, especially considering you have not done any voltage tweaking/OCing, though you did mention the turbo boost as a possibility in the first post, which is indeed true. Hmm, seeing as how I'm not the best person on these forums for these problems I'm going to try and drag some other posters in here, wonder what they're afraid of. :P

I get the feeling it may be a turbo/voltage issue, though. If it happens again, take a picture with a camera of the BSOD where you can read the text in the picture and put it up here. (use a thumbnail of a large version)

[latzko]

Ok, I'll try go get a pic next time it happens but it might be tomorrow... Thanks for trying to help, I'd really like to get this problem fixed... <3

[Asera]

Is your memory Kingston HyperX modules rated for 1.65v?

If so you either need to put them down to 1.525v @ 1333mhz, or keep them at 1.65v and pump your VCCIO to 1.15v, which is dangerous I think.

If your BIOS is pulling stock voltage settings from the SPD and setting them to 1.65v while your VCCIO is at stock 1.05v, that's .6v difference when SB only like .5v difference.

(I have 1.65v HyperX sticks in my office tower, the 2500K doesn't exactly like them too much, so I had to set them to 1333mhz @ 1.525v.)

[latzko]

I checked into BIOS and memory is running on 1.5v @1333MHz. I've disabled turbo boost for processor to see if that might fix the thing...

[OhpUldum]

Download BlueScreenView and run it. Report the information you find.

BlueScreenView doesn't require any installation process or additional dll files. In order to start using it, simply run the executable file - BlueScreenView.exe
After running BlueScreenView, it automatically scans your MiniDump folder and display all crash details in the upper pane.

Source

[Dezi]

I had a similair problem like this.
It's really easy, contact the store that you bought it from. Explain your situation include all the minidump files and they will solve it for you. If they can't it could be a hardware problem (which is what i had with my 2 weeks old pc)

[Asera]

1.5v might be too low for HyperX sticks rated at 1.65. Mine weren't stable at 1.5v.

It would really help if you knew the BSOD code... lol.

---------- Post added 2011-11-07 at 11:38 AM ----------

Download BlueScreenView and run it. Report the information you find.



Source

Holy crap, this!

Such a simple solution.. :3

[latzko]

I run the program and it reports nothing, I've tried searching for minidump folder through the windows folder with no luck. Any suggestion where those logs could be? As I wrote, using w7 pro... Thanks

[pacapaca]

The Patriot Pyro SSD line has BSOD problems related to sleep mode... The drive dismounts itself causing a blue screen. Firmware 3.3.0 is meant to fix everything but I'm not sure if its out yet but try updating it if you haven't done so already.

[OhpUldum]

Well it should be C:\Windows\minidump

[latzko]

The Patriot Pyro SSD line has BSOD problems related to sleep mode... The drive dismounts itself causing a blue screen. Firmware 3.3.0 is meant to fix everything but I'm not sure if its out yet.

I've disabled all sleep and hibernate related functions, also powersaving options in BIOS... Still happenining

@Culadin, I just found out that debugging info was written as kernel memory dump and i've set it up to be written as small memory dump (aka the log that can be used in that tool). I'm guessing all I can do is wait for new BSOD so the log can be made...