Driver, Ram or GPU issue.

Kronos

Kronos

Kronos

Soldato
Joined
11 Nov 2009
Posts
4,784
Location
Edinburgh
Just had a Blue screen whilst playing Far Cry Primal and using Nirsofts BlueScreenView the problem seems to related to Nvidia as the cause is related to Nvlddmkm.sys and dxgmms1.sys.

First blue screen I have had with Windows 7 and this is after my 1080 upgrade.

I did not have the latest driver, I thought I did, and did a clean install and so far so good.

Unfortunately this morning I got another blue screen and I was away from my PC at the time and nothing much was open.

Anyone make any sense of this from Nirsofts BlueScreenView?

Dump file.073116-7831-01.dmp
Crash Time31/07/2016 10:47:40
Bug Check string SYSTEM_SERVICE_EXCEPTION
0x0000003b
00000000`
c0000005
fffff800`0313b437
fffff880`08ce1f10
00000000`00000000 ntoskrnl.exe
ntoskrnl.exe+6f400
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7601.23418 (win7sp1_ldr.160408-2045) x64
ntoskrnl.exe+6f400
C:\Windows\Minidump\073116-7831-01.dmp
4 15 7601 413,120 31/07/2016 10:48:55

Removed or reset the modest overclock on the CPU and ran Memtest.
I do have these images and a question or two. This is well outside my comfort zone so forgive me if the questions are daft.
In this image you see Memtest list the RAM as DDR3 and it is DDR4 and shows timings of 19-15-15-31 when it should be 16-16-16-36, why is this?
odw3FPR.jpg.png


In this image at 10+ hours I have two errors I had none at 7 hours.
jtVbi5A.jpg.png


And this image confuses me. I went to have a look at the DRAM timings in the BIOS and instead of seeing 4 columns I see this, so have no idea where the correct timings should be entered as there seems to be only three which currently have 15-15-36 instead of 16-16-16-36 so as I say confused as to what should be entered where or even if I need to and just leave it at auto.
cWAZwac.jpg.png


Temps of CPU and GPU are fine, latest BIOS in place. Unfortunately my issues began after the installation of the 1080 as the PC had been running without issues with the new mobo/CPU/RAM since May when I was using a 980.

Do I RMA the RAM or whatever it is one does after a couple of months use?

Any help or advice welcomed.
 
Last edited:
if Memtest is finding errors then you have a faulty stick\sticks of ram.

You will need to RMA all the sticks of ram, with regards to your other questions i am sure someone else can answer them, i haven't used any recent boards so not too sure on the settings etc.

for the time being for testing you can take out on stick of ram and re run memtest, if it finds no errors then you have found the faulty stick if you still get errors put in the removed stick and take out another till the errors go.

try some more gaming and see if you still get the errors or not as it should sort it.
 
Cheers mate, as the Avexir Core Blue Series 16GB was bought as a package I doubt whether finding out if I have one faulty RAM will make much difference overall as I will have to return the 4 sticks would I not.
 
As LewisRaz said you will need to return the whole kit so if its 4 x 4GB the whole lot needs to go back but if its 2 sets of 2 x 4GB kits then only one set will need to go back.

regards
 
After getting an RMA number and label and being told it could take 28 to get a replacement I decided to do some tinkering as i was not totally convinced the RAM was at fault even with the two errors.
Updated the BIOS for a start. Reseated everything. Then messed about with various settings, gamed all day yesterday without issue. Then ran Memtest for 12 hours and no errors were shown.
Have I sorted it, time will tell?
 
Were you running a CPU overclock when you did the first memtest? Not a good idea if so, could produce false positives.

Also you really need to know what the spec timings are otherwise you don't know what you're testing! Big difference between 19-15-15 and 16-16-16.

BoatyMcBoatface said:
BIOS updates can often fix ram incompatibilities
Click to expand...

Seems unlikely as it was apparently working fine before the GPU change.
 
joeyjojo said:
Were you running a CPU overclock when you did the first memtest? Not a good idea if so, could produce false positives.
Click to expand...

No I had removed the overclock

joeyjojo said:
Also you really need to know what the spec timings are otherwise you don't know what you're testing! Big difference between 19-15-15 and 16-16-16.
Click to expand...

As you can see in my third image it is difficult to know where to input the 4 sets of timing numbers when on the face of it the Asus BIOS only has three boxes but i did input 16-16-36 in those.
I have emailed Asus asking for a bit of information on the Asus BIOS DRAM Timings page of the BIOS.
 
joeyjojo said:
Seems unlikely as it was apparently working fine before the GPU change.
Click to expand...

Only the first error says about nvidia causing it (before driver update).

Then he had a memory error in lengthly memtest, upgraded BIOS, cleared memtest error.

Out of interest, list the rest of your spec. Including PSU and SSD model.
 
BoatyMcBoatface said:
Then he had a memory error in lengthly memtest, upgraded BIOS, cleared memtest error.
Click to expand...

Other things changed too though,

'Updated the BIOS for a start. Reseated everything. Then messed about with various settings...'

Hopefully it was just a flaky BIOS - I've seen mysterious random crashes suddenly go away after a BIOS update before - but if not we're a bit short of info.
 
joeyjojo said:
Other things changed too though,

'Updated the BIOS for a start. Reseated everything. Then messed about with various settings...'

Hopefully it was just a flaky BIOS - I've seen mysterious random crashes suddenly go away after a BIOS update before - but if not we're a bit short of info.
Click to expand...

Would help if you were were specific on what info you are short of?
 
is that a Crucial M4 you're using?

are you on the latest firmware release? there's a big they get after 5200hours of use.

I ask because the crucial m5 doesn't exist.
 
You must log in or register to reply here.
Back
Top Bottom