System BSOD at Shutdown

Hi,

i've a strang Problem with System crashes out of nowhere - System worked in this configuration for over a year.
Since a few days the system crashes after logoff right before turning itself off with different BSODs.
There's no clear pattern for the BSOD and driver type it crashes at.

OK so i thought might be the CPU which has degraded or something like that ... primed ... 20 minutes ... nothing.
Next step Memtestx86+ ... nothing again.
Then some tests for the crash again ... start - logon - shutdown -> bsod ... this is absolutely repeatable.

Then some problems with SSL connection started , https pages not loading for example.
Lowered CPU clock by 100 Mhz ... everything works again for a evening.
But problems came back after a while.
So it doesn't seem the CPU after all.

I suspect motherboard or PSU. A quick look at the mobo revealed no exploded capacitors.
The crashes never occur on load, e.g. while gaming. But basically always while Shutting down.

The PSU is quite old, around 6+ years i think. (Tagan 530W, not the best overclock PSU but not really bad either, 2 12V Rails and plenty of Amps).
Voltage reports seem good though, but maybe there is a short dive suddenly which crashes the system?

Does anyone know if PSUs exhibit this kind of degradation where they suddenly can get problems providing clear power for the system?
Did someone else experience the same and has a hint of whats wrong?

I also dont believe in file corruption. Files seem to be ok. And it does BSOD from IRQL_NOT_LESS_OR EQUAL to various drivers.


TIA

Every time I had a BSOD on shut down the memory was stable

Have you installed any new software recently? I don't think you have a hardware problem. You could, but more cases than not (especially if you have run prime95 and memtest and game frequently), it's probably either a piece of software that's causing the crash, or maybe the hard drive going bad in the area where something is to be run during shutdown and it's esploding the os on shutdown. It would be helpful to get the dumpfile and maybe some info from the bsod screen, if you are able to post these. I would assume you are talking about the computer in your sig, so it is win 7 x64, right? Get us a little more info and we can probably help you out more :)

http://www.nirsoft.net/utils/blue_screen_view.html

Please download that, run it and take a screenshot of the most recent BSOD

Mad-Marty: I've had strange things like that happen when pushing my OC pretty hard.

It doesn't sound like thats your situation, but when it happens a "System Restore" to the point where the
system was stable fixes it.... Might be worth a try. :up:

Thanks for all your answers.

I'll analyze a dump as soon as i get back to the system.
(Will be on monday, as i'm currently not near the system.)

Yes, its the System from the sig, W7 U x64 on Phenom II x6 @ 4 Ghz on GA-MA790GP-UD4H.

I actually installed new software. Which was the Catalyst 11.8 preview.
So yes, i thought its that and reverted. Didn't help though so probably a bad coincidence.
(The SSL problem was apparent a few days before).

Also it *might* be the videocards, run single card, no problem on games.
When the GPU crashes it would be not at shutdown i think, should be under load.

The Win partition is on a intel postville 80 gb ssd.
Checked intel SSD suite, wearout still has not moved a single percentage.
Also no read problems were to be found.

Also by lowering OC it did work again for a few tries as described in 1st post.
But then again even on my standard oc no testsuites exhibit those problems.
The shutdown bsod was very quickly reproducible though.

What do you guys think?

Mobo?
PSU?
CPU?

Sounds like a software issue to me. Try a fresh win install.

Hi all,

I dont believe in Software issue, this Win7 install is only 3 Weeks old now.
Re-install was not done because of problems.

Attachment 118518

Here is the BSOD screenshots.
Hmm since i did the reinstall not so long ago ...
I wonder if those microcode update dll was present the last time?
Maybe that thing shoots up CPU AGESA on high clocks somehow?

As you can see, creash reasons are in a number of different system dlls mostly.

Any ideas?

Thanks so far :)

EDIT:
Ok so i tried what happens if i overclock statically through bios, not altering p states with k10 stat
and what if i use low values for k10 stat

- system does shutdown without bsod if static bios oc (no CnQ)
- system does shutdown without bsod if low k10 stat oc (so its not the k10 stat driver shooting things up)

So ... i think this points to some power problem, maybe doing p-state changes while unloading and not getting enough power?
(Oh btw, the in between p-states are not modified)

What do you guys think?


Thanks.

I remember the IRQ not equal BSOD from Win XP. I think If I remember correctly it was RAM related, PSU is a posiblity, but the RAM much more likely.

PAGE_FAULT and IRQL_NOT_LESS_OR_EQUAL are ram related. System service exception can also be ram related...as well as the DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Well,

but that doesnt make much sense, right?
Memtest86+ ... OK
Lower CPU clocks ... OK
no CnQ ... ok

If the bsods were because of bad ram, those 3 things would not work out to be ok i guess.

Memtest86+ is in no way a sign of stability. I can run ram 30 Mhz higher in Memtest86 than what is stable in windows. Same rule applies to CPUNB.

Show 4 hour Prime95 Blend and then I personally would rule out memory problems.

Yeah but reproducible crash after 10 seconds of starting windows and shutting down vs 20 mins of memtest, prime, etc which dont fail?

OK but anyway i found the reason. Forgot that i had Cat 10.6 before i tried 10.8 preview.
Its Catalyst 10.7 and 10.8 preview. Both seem to :banana::banana::banana::banana: up at shutdown with the 4 Ghz clock.
Down to 10.6 and no BSODs on shutdown anymore.

Now that is really strange i think.
I can game for hours, benchmark everything etc and the damn Catalyst crashes on shutdown only ...

I'll try to set a clockdown trigger on shutdown sequence and see what happens.
Now thats interesting, i want to find out why it only produces errors on shutdown.
Maybe a timing issue when cpu jumps between 4 Ghz and 800 Mhz while unloading catalyst (as written earlier without CnQ and a static 4 Ghz its fine too).


Thanks again guys.