Weird BSODs After upgrade

ciutarobert

Reputable
Jan 27, 2015
5
0
4,510
Hello!

I recently changed my MOBO,CPU and GPU and then i installed windows 8.1
everything is fine, i can play older games just fine but i just tried far cry 4, assassins creed unity and dying light at for each one of them after around 20-25 minutes of gaming on maxed out settings i get a random crash which i believe is equal to a BSOD except that it's not even blue anymore on this windows

Specs

Gigabyte Z97-HD3
I5 3690k
gtx 970 G1 gaming
corsair (orange one) 650 w
12 gb ram ( 11,9 usable )
120 gb kingston ssd
2x HDDs

Here are the minidump files
http://s000.tinyupload.com/index.php?file_id=05499146137441648499

I would also like to mention that i checked the temperatures and they all are allright even tho i find something weird with the cpu ( stock cooler )
in idle it's between 28 and 32 C* and in games like those mentioned above after a while it can reach 70. With prime95 and RealTemp testing it was above 85

Any ideas on what could cause the problems and how can i fix them?

Thanks a lot!
 
I would focus on getting a updated bios version and see if you still have the same issue.

you had two bugchecks, one in directx and one in USB code both might have been corrupted by another driver (WinRing driver would be suspected cause) You might want to run verifier on the driver or remove it after you update your BIOS

-I would suspect WinRing0x64.sys because of known bugs with windows 8.x
C:\Users\Rob\Desktop\Real Temp\WinRing0x64.sys Sat Jul 26 06:29:37 2008

your bios info:
BIOS Version F4
BIOS Release Date 05/07/2014
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z97-HD3
Processor Version Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3500MHz

I think this BIOS was released before your processor was released. I would update the BIOS to get new microcode settings for your CPU.
 

ciutarobert

Reputable
Jan 27, 2015
5
0
4,510



TX650M
I5 3690k
sorry for typing weird stuff , it was pretty late :D

i will try and update my BIOS now, thanks

//@RaDiKal_ those high temps are only in prime95 , in games its usually stable under 70*C
I will consider doing that aswell tho, thanks



//Bios is updated but i have to leave for a few hours, i also got rid of realtemp and WinRing0x64.sys

What software do you suggest for checking temperatures and such? it seems like everest is not recognizing my motherboard/cpu and their temperatures, will try finding a newer version meanwhile
 

ciutarobert

Reputable
Jan 27, 2015
5
0
4,510
Problem is still persisting, temperatures are ok but i find it pretty weird that the CPU heats and cools down fairly quick
even by 3* per second
BIOS succesfully updated and i got rid of that software as mentioned above

http://s000.tinyupload.com/?file_id=08378184074968482899
The last log

Also this is the first pc that i have build by myself almost entirely ( psu was in case still )
Maybe i did something wrong?

Also another thing is that i have 2x4 gb corsair vengance 1600 mhz in slots 1 and 3 and
2x2 OCZ gold 1333 MHZ in 2-4 but it used to run with no problems caused by that on the old MOBO

//I7Baby saw some of your other posts and i took the OCZs out
now i have 8 gb ram ( 7,86 gb usable ) , i am going to try again



seems to have fixed my problem
Thanks to everyone!
 
kind of looks like you were runing steam and the nvidia driver ran out of virutal memory and caused a bugcheck.

-kind of looks like you have zero free physical memory and no pagefile.sys
and the graphics driver choked and caused a bugcheck.

Committed pages: 2331915 ( 9327660 Kb)
********** Number of committed pages is near limit ********

sounds like a software bug.
0: kd> lmvm nvlddmkm
start end module name
fffff801`05815000 fffff801`06223000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Fri Jan 09 14:22:06 2015 (54B0548E)
CheckSum: 009D73FA
ImageSize: 00A0E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


hard to tell what the bug is on a minidump, you would need to change to a full memory or kernel memory dump to figure out what is using all of your virtual memory.

You could also make sure that you have free space on the drive where your pagefile is located (so it could expand), or increase the size of your pagefile.sys. This would delay the time it takes before the driver will crash.

you could use resoure monitor to see what is using your virtual memory, you could download poolmon.exe from the windows DDK to help find out.