just had something weird.

[LoadsaMoney]

Well this was odd, right i ran the latest version of CPU-Z, and it was reporting my CPU as running at 1600mhz 6x, instead of 2400mhz x9 (or whatever it is), so i thought wonder if its now reporting correct as ive got that EIST on in the BIOS, and the version i had of CPU-Z before said the proper 2400mhz x9.

Anyway i went into the BIOS turnd that EIST off, and CPU-Z was still saying 1600mhz 6x, but every now and again it would flash 2400, so i thought must be just miss-reporting or something, so i went back into BIOS and put the EIST back on, then decided to run a couple of games to see if it was at 1600mhz (as i would notice), banged CoD2 on and ran about for about 10 secs, seemed fine, banged stalker on, ran the buidlings timedemo, seemed fine again, so then i decided to run into the gun battle to see if it would slowdown if my CPU had somehow underclocked or something, but it didnt, ran fine, i just ran about for a minute or so then quit back to desktop, then about 5 secs (not even that) later my PC just switched off, came back on, then went off again, came on again and booted fine, so i thought hmm somethings up here now then, so i decided to run through 06 thinking, if ive got a PSU prob or owt, then running this will shut it down straight away, but it ran through fine, and its still on now, so im stumped.

Any possible ideas.

Thanks.

 

[Teaf]

Have you got automatic restarts turned on? If you have and it's automatically rebooting chances are you're missing the information that it's going to give on the blue screen. I'd suggest turning it off if you do have it on. Then I would download the Debugging Tools for Windows. When you download and install that you can follow the next steps:

1. Open the program and click File menu, then "Symbols path"
2. Type in "SRV*c:\symbols*http://msdl.microsoft.com/download/symbols" without the quotes
3. Then click File -> Open Crash Dump and browse to C:\Windows\Minidump and open the latest crash dump
4. When you open it, it'll take a while to load in but when it does you'll be connected to the debugger
5. When you are connected type in "!anaylze -v" without the quotes to get info on why the computer rebooted.

 

[LoadsaMoney]

yeah thats on, but i didnt get any BSOD, it just switched off, came straight back on, then just switched straight off again, didnt even boot or anything, as it only came back on for a bout 1-2 secs, then it booted up fine, ive just gone into my event viewer and noticed a werid ps6ah4nb error in the system bit which is around the time it went off, and it says it was a Protection Synchronization driver detected an internal error, contact the customer support service.

Well this is interesting, found by putting the error into google.

http://community.codemasters.com/forum/showthread.php?t=204208&page=2

Ive got Dirt on, been on since release and never had a prob.

 

[Teaf]

yeah thats on, but i didnt get any BSOD, it just switched off, came straight back on, then just switched straight off again, didnt even boot or anything, as it only came back on for a bout 1-2 secs, then it booted up fine, ive just gone into my event viewer and noticed a werid ps6ah4nb error in the system bit which is around the time it went off, and it says it was a Protection Synchronization driver detected an internal error, contact the customer support service.

That's something to do with Starforce game protection. I would maybe try to run some kinda Starforce cleaner on your system.

 

[LoadsaMoney]

Yeah very strange, never had any issues with starforce before, and its been on my system for months (could be years ), ill give it a go, thanks.