• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

BSOD Card/Driver/Something else

Doco

Doco

Doco

Associate
Joined
16 Aug 2011
Posts
1,569
Location
Ireland
Hey all, thought I'd check in here and get advice on a BSOD issue that's been occurring last little while, now my card was* overlocked but i decided to restore it to default settings to see if it was a dodgy O.C. but gaming today and Diablo 3 crashed with about 30 mins of play and then about 10 mins ago I got a blue screen when playing a MP game with a friend, never had an issue with temps even when O.C - temp was 54-6 degrees when my system blue screened)

When I check BlueScreenView all my last crashed have 3 filenames highlighted red in common

atikmpag.sys
dxgkrnl.sys
dxgmms1.sys


whats your rough first opinions - borked card/software conflict or something else


Bit more data - I am using a 2 screen setup and occasionally the 2nd screen will go up the left (all fuzzy etc) a restart will fix it.

Any help welcome

Doco.
 
Blue screen viewer shows it starting around feb. it just seems to have gotten bad recently - no changes in hardware from November and no driver updates I can recall.
 
Well this has gone from bad to worse lol aye my cpu is overclocked, has been from I got it, didnt think it was it because ati etc thought it may have been card related, I'l restore my cpu to stock then and see if it re-occurs over the next few days
 
edit sorry my bad wrong information. 116 is from overclocking GPU not CPU the CPU code is 124

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

So ignore, above are you overclocking the GPU??

And just for testing I would still run the CPU stock or lower down the OC for little while.
 
I did have the card O.C. but restored to default settings (non-O.C.) and got a x116 BSOD today
 
Doco said:
Hada look in my bios and PCH voltage is 1.058v and "auto"
Click to expand...

Seeing has 116 means its low I would expect you have to higher this. But am in no way asking you to higher to something I don't fully understand whats classed as safe.. I see post on Google saying 1.1 etc
 
You must log in or register to reply here.
Back
Top Bottom