This BSOD puzzles me!

[Valis]

I have been getting these BSOD's for some weeks now, and only in Win 7 64 bits. D: Win XP 32 works without a hitch.

http://www.lern2play.se/~chiefen/pics/w7.bsod.jpg

When I google or search for the cause explained in the BSOD, I don't get any coherent solutions/causes etc. AMD gives the most cliché and dumbest solution of them all.

http://support.amd.com/us/kbarticles/Pages/CPU-3-Systemexperiencesablue.aspx

Since I've updated win 7, tested with different RAM, PSU, all new drivers, etc. All I have left is CPU and mobo, since I don't think it is the Radeon causing this. :hmm:

Have you guys seen anything, or have any ideas? The BSOD's comes now and then, randomly, after hours of use or more, even.

I'd appreciate it.

 

[Veliko]

If you have already spent all that time updating drivers and trying different hardware, it is probably easier just to format W7 and start afresh.

 

[Valis]

I was running W7 RC long before and W7 Ultimate (x64) another version that had problem too, but I can't remember if it was the same. Ohh well, it was fun while it lasted. :\

 

[Snapster]

If you start up in safe mode you'll get a list of drivers as they load. The should be able to point you at least the starting driver (or dependant) that is causing the issue.

I'm still surprised (read: disappointed) at how easy Windows can still fubar due to one driver going awol, and not get any sort of intelligent message as to what the problem is (even on Server 2008). Might as well forget any recovery and just revert to an image.

 

[w7pro]

Doing a clean install at this point might be your best bet. It can be time consuming, but at the very least, you can maybe get rid of what's causing your machine's problems.

-- Ryan
Windows Outreach Team

 

[Valis]

Doing a clean install at this point might be your best bet. It can be time consuming, but at the very least, you can maybe get rid of what's causing your machine's problems.

-- Ryan
Windows Outreach Team

I thought that too, so I did a while back, but it still doing the same.

 

[corkyg]

The AMD message points to something you have not switched or mentioned . . . the power supply.

 

[theevilsharpie]

If you're getting CPU timing-related BSODs in Windows 7, but not in Windows XP, your motherboard may have an issue with it's HPET timer. Your BIOS may have an option to disable it, and failing that, Windows 7 should have an force the use of the APIC timer.

 

[Valis]

The AMD message points to something you have not switched or mentioned . . . the power supply.

About a week ago, prior to writing this thread, I switched out the older Chieftec PSU to a 550Watt newer Corsair. Just to be on the safe side with the power supply.

If you're getting CPU timing-related BSODs in Windows 7, but not in Windows XP, your motherboard may have an issue with it's HPET timer. Your BIOS may have an option to disable it, and failing that, Windows 7 should have an force the use of the APIC timer.

Ok, I shall try this. The mobo I have is a Giga GA-MA770-DS3 BIOS FDe dated 09/13/2010
Thanks for the tip!

 

[airdata]

What do you have for a display?

 

[Valis]

What do you have for a display?

A monitor? :sneaky: Ok, seriously, I have an ASUS Rad HD4850 connected to a Sam Syncmaster 245B @ 1920x1200 Res.


On another note, I have now disabled the HPET timer in the Power Management Setup section in the AWARD BIOS. Let's see what happens. :whiste: :hmm:

 

[Valis]

Well, disabling the HPET in the BIOS didn't help much.... :\

 

[bankster55]

look in event viewer