BSOD system_service_exception 0x3b

[dk70]

Good, I think they work with 2.1v
Modules are really 1.8v 5-5-5 but thanks to Corsairs "handpicking" they raise specs and sell it as 2.1v 4-4-4. Why SPD/auto dont work. You need something like EPP A Quick Look at Enhanced Performance Profiles (EPP) Memory Should only be important with timings, voltage. Rest of the settings are just fine-tuning, chipset/Gigabyte defaults.

Dont overclock when stress testing? You should stress test a lot when overclocking but not now with memtest86+ since trying to find out if ram is working under default conditions. Any change will in theory require you to start all over - why oc´ing is fun Prime95/Orthos blend is stress testing memory, memtest86 is just checking.

 

[danielr0y]

thats what i mean...
i'm not overclocking while stressing now that there is a problem.

Just passed memory diagnostics tool with 2.1v
running again at 1.8v- hoping for fail.

 

[dk70]

Ok with quick-test now but if you could let run some hours that would be the best. Same as with Orthos. Do a marathon test when things have settled down - makes you feel better

When back in Windows, and you will be soon i think, do run sfc /scannow and chkdsk. Making sure old bsods are really gone and dont have leftovers like corrupted system files or file system.

 

[danielr0y]

damn... passed the voltage test. passed with both 2.1 and 1.8. not the same as last night.

ill run the scans now then continue mem tests. still trying to get memtest86 to start but id preferr to go through all the tests quick. then do some long ones.

 

[dk70]

Annoying.

So may be you could try to boot Windows with 2.1v? Not like you are afraid of bsod so what to lose? Then we could see if Orthos/P95 blend test fail.

Chipset should not be compared but as said I had same problem with memtesting being ok and yet ram failed in P95 - which it should, i had the bsods to prove it was right. As have you, hard to tell.

 

[danielr0y]

running run sfc /scannow now.

windows booted with RAM voltage at 2.1 no worries. but wasn't running for long. just enough to open memory diag tool which forces restart. Its not in my F8 menu annoyingly. any suggestions how i get it in there?

 

[dk70]

Dont really know - there are several ways to start it from boot http://www.vistax64.com/tutorials/65361-memory-diagnostics-tool.html?ltr=M

I have rarely used it because of memtest86. When i did overclocking using test 5 and 8 to get quick confirmation registry files would not corrupt was nice. Cpu oc/tweaking not so risky, memory can be.

 

[acdcfan]

and this whilst or after vista memory diagnosis tool (i walked out... came back to see it)

Driver irql not less or equal

BCCode: d1
BCP1: 0000000000000037
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFFA6002571CEC

nvlddmkm.sys- address FFFFFA6002571CEC

File causing this error is athrx.sys... Do you have Atheros card?

 

[acdcfan]

and this whilst or after vista memory diagnosis tool (i walked out... came back to see it)

Driver irql not less or equal

BCCode: d1
BCP1: 0000000000000037
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFFA6002571CEC

nvlddmkm.sys- address FFFFFA6002571CEC

This one is caused by bad Nvidia graphics driver. Try updating the drivers, but first try to roll back the driver to previous one and see if it causes the error

 

[dk70]

I think the athrx.sys is from some dlink stuff - not without concern perhaps... Working Vista 64 bit drivers anytime soon? May be it should be disabled as a test.

Problem is his ram setup might not be all that solid - and could be causing all the bsods. Then error msg. is more random than precise - will never say "you have wrong setting for your ram in bios". Think he is testing ram now.

 

[acdcfan]

system_service_exception_recent.dmp
BCCode: 3b
BCP1: 00000000C0000047
BCP2: FFFFF80001EC1B48
BCP3: FFFFFA60090E9210
BCP4: 0000000000000000

system_service_exception_1.dmp
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF960000BECD6
BCP3: FFFFFA600479EB80
BCP4: 0000000000000000

This one adn one above are cause by Firefox (unless you sent the same file).... Something to do with win32k.sys file.

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


PROCESS_NAME: firefox.exe

page_fault_in_non_paged_area.dmp

BCCode: 50
BCP1: FFFFF800015386A8
BCP2: 0000000000000001
BCP3: FFFFF80002111E7B
BCP4: 0000000000000000

Thanks

and above one is to do with your Vista Some register values may be zeroed or incorrect. ntkrnlmp.exe
PROCESS_NAME: System

 

[acdcfan]

I think the athrx.sys is from some dlink stuff - not without concern perhaps... Working Vista 64 bit drivers anytime soon? May be it should be disabled as a test.

Problem is his ram setup might not be all that solid - and could be causing all the bsods. Then error msg. is more random than precise - will never say "you have wrong setting for your ram in bios". Think he is testing ram now.

He has Firefox problem too, for some reason and certain issue with is registry...
Last dump file I looked at was to do with the system and incorrect registry values.

 

[dk70]

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-tools/183498-windows-update-reset-repair-tools.html if that is not also victim of something else.

 

[danielr0y]

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...?

Thanks

 

[acdcfan]

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.

Thanks

One thing at the time

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.....

Second
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....

 

[dk70]

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.

 

[danielr0y]

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.

 

[dk70]

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

 

[danielr0y]

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?

 

[dk70]

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.