Yeah, well i have had the very same bsods. They are typical for ram not working well. The Dlink athrx.sys one looks a bit hmmm perhaps but rest I would not take literally.
Something is causing them and making Nvidia, Dlink, Firefox, whatever appear evil/broken. Firefox dont cause bsod and notepad should never stop responding. I put all money on hardware but if not then perhaps athrx.sys thingy is to blaim. Wont be 5 things, only 1. Once fixed all other problems are also fixed.
May be risk of snowball effect if some system drivers are corrupt, get more and more bsods pointing left and right.
Easier to attack Vista when hardware is declared stable, to avoid running around in a circle.
Not sure about windowswcpotherfailure3 error - might have to run through this http://www.vistax64.com/software-too...air-tools.html if that is not also victim of something else.
OK, now im really confused and a little frustrated.
I've just run an extensive test with 4 passes and i don't think there was any errors. the first pass had taken 2 hours, then i fell asleep. this morning there is no message from mem diag saying there was troubles.
I haven't really changed anything... sure i fixed the voltages but when i put them back as they were before they still passed. I've not had a blue screen for a while now either.
Some would say that's good. But the problem cant be fixed, as i said, nothing has really been done.
Yes i do have a dlink card, running Atheros driver recommended by win update.
and yes i've got a new nvidia driver but i've used both these drivers before without trouble.
I agree that these aren't all to blame. One hardware fault is just causing instability and everything crashes.
Perhaps someone could analyse the bin file left from the mem diag...?
My suggestion is that if you do have original installation disk that came with Dlink card and Atheros drivers, please install drivers that came with it and completely ignore Vistas update.....
Try to roll back Nvidia driver to an older version and see how that goes. If you do have an installation disc, re-install drivers of that disc and see if that helps.
Personally, I can not see why FF would be culprit and causing BSOD but that maybe linked to above 2.
I don't know who can analyse binary files but I will keep looking for you....
1.8v vs 2.1v is not the same so that is a change. What about P95/Orthos blend test? Try with both. If it can run hours with 1.8v then 1.8v is ok, 1.4v is also ok it it works If you can run tuned 4x1gb at 4-4-4 requiring 2.1v with 1.8v it is a miracle or motherboard is overvolting big time. I will not be that surprised memtest approves with 1.8 or 1.88 in readouts, P95 is something else and "Blend" torture the real test.
What about Windows update? Does it work? Device manager look neat with no question marks?
About the Dlink I would go to their forum, search model and get an overview. Perhaps they have beta-driver more stable than official - or a certain version is prefered. Actually I would go more by Windows Update than cd from Dlink if it had to be one or the other - but find out what the deal is. They got 64bit driver problem or not? Other people will have same problem. Use whatever works. In general go to site of manufacturer and get the latest - or if you truly want the latest go to chipset maker, like Realtek.
I assume you dont run 4 Windows Tweakers or any other unnecessary stuff after a clean boot? And of course no virus/spyware as well.
What about install cd from Gigabyte, did you go all the way with Ultra TPM, EasyTune?
About Nvidia driver I would just use latest, 181.22. One of those you should not get from Windows update, only from Nvidia site.
Did sfc /scannow find any corruption? and did you remember chkdsk?
Dont really remember details from those dump files but there were nothing surprising in there considering how Vista behaves when memory is faulty. Same old really. If ram has never caused any problem an equally evil part must be able to make same snowball effect of bsods. Think you can forget about dump files - unless new one comes along! All I can think of is weak power supply or bad overclocking/tweaking - but all you changed was motherboard, all parts worked together before so dont know.
Things do break, may be motherboard has a permanent problem but since you just few hours ago started using correct voltage for ram may a bit too soon to point fingers
You do have latest bios and except for memory stuff there should not be need for tinkering. No auto-oc/tweaking/tuning of any kind. Loading "optimized defaults" + ram setup should be enough. You did say cpu oc was limited by ram - and yet use wrong voltage for ram, excuse me for being sceptical and suggesting you run through bios once again, heh. I rarely trust myself when doing this so dont feel offended...
You know best but if any doubt use cpu-z to check settings in Vista.
Last edited by dk70; 26 Jan 2009 at 06:30 AM.
Well i've had no problems since the 25th. Its been running the entire time, with reboots but no down time... and no blue screens or crashes.
I've not changed anything with the drivers. not video or dlink card.
I dont run any tweakers or anything of the sort.
I've ran an extensive Mem diag tool test. took about 8 hours, no crashes.
and an orthos blend test for about 7 hours. no crashes.
i figure its from raising the RAM voltages to 2.1. But when i lowered it again to 1.8 it didn't crash.
How exactly would the sfc /scannow and chkdsk have stopped the problems? if it did.
Im getting really curious if you can run P95 blend test with 1.8v - should not work for long if logic still counts. Another thing is only you know speed of ram. If it is running lower than 800 then more chance less than 2.1v will work. Can be very tricky this. When I had similar problem I could run quite a while without BSOD - I just did not think memory at all, ram was only doing 750, was not tweaking/oc´ing and memtest approved. Almost perfect but only almost. That is where P95 comes in handy Situaton was about the same as when someone pushes oc-limits a bit too far without testing properly - but can play favorite game for hours.
I should have done more research - for example at Corsair forum where they are clear about 4x1gb giving problems on some chipsets and highly suggest to lower speed.
After SFC is done it will state if any problems found. Also will make report in windows/logs/cbs
Chkdsk should also state if anything is found.
You had massive attact of bsods - if gone something must have helped
cpu frequency is @ 8x 399 (3.19ghz) with mem @ 798mhz
why is it i cant raise it one more count to 400 which would have my ram @ 800mhz?
I would not like to say much about overclocking an Intel cpu on Intel chipset.
However, what does System Memory Multiplier do? While on "SPD" does it lock memory to max 800 speed? or 799? May be you need to manually force some value to unlock higher numbers? Like you do with "Cpu host clock control". Would not make much sense you lock ram speed in one setting then overrides it in another.
Think you should go ask in oc-forum. And dont uninstall Prime95 just yet.
|Thread||Thread Starter||Forum||Replies||Last Post|
|BSOD - System_Service_Exception (3B)||Whilom||Crashes and Debugging||36||11 Dec 2010|
|System_service_exception||brandonman||General Discussion||1||01 Jul 2009|
|System_Service_Exception||brandonman||Vista General||2||01 Jul 2009|
|Vista Crash after installing SP1 BSOD SYSTEM_SERVICE_EXCEPTION||ethic||Vista General||4||05 Oct 2008|
|System_service_exception||Shadowfly||General Discussion||6||19 Sep 2008|