Tech Help How do I know whats messed up?

[SigmaMX]

Hey bros, thanks in advance for the help.

I recently changed to a new Corsair Tower, bought a Gold certified CS750M power source, bought a Corsair water cooler for my CPU and now my gaming rig is misbehaving. Before that, with my (VERY) old stuff, I had not problems at all with hardcore 4K gaming, but now I cant even play CS:GO w/o the game crashing.

Here's my setup:

MB Asus B85
i7 4770k (2 years old)
GTX 980 (more than 2 years old)
16gb RAM, one Hyper X the other generic
SSD Corsair 256 gb
and two HDD for backup (total 2 TB)

First I was having problems with BSOD about "reading permissions" and nvidia driver. I took my stuff to look at and the tech guy apparently fixed it cuz I havent had any BSODs so far; still every game I play thats, how to speak? 3D? crashes.

i.e. I can play Starbound or a PSP simulator all day, but I cant play CS:GO for more than 10 minutes. No BSOD, the game just crashed, that game and any other one similar.

I just want to know what component do I need to change? I get it, stuff breaks, but WHAT?

Last time my gpu had major problems, I was getting no video from anything, but now I have video on games that are not very "heavy"?

I supposedly checked my SSD status and my RAM with Window's assistance programs and everythings fine. I even switched my GPU to the second slot and the problems are not as common but still there. For my GPU heat should not be an issue cuz the Open Hardware Monitor says I always have 50-60 ?C average, which I understand is within limits of great performance.

Any tips?

Thanks a bunch!

 

[Ric]

You say your game crashes. Sometimes when crashes occur, it's documented by Windows in the Console. You can read it in Event Viewer.

For instance, my power supply has been a piece of shit lately. So, my PC randomly turns off. It's logged in the event viewer.

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

under Custom Views > Administrative Events.

Can you see if your crashes are logged? If it is, it might point us to the culprit of the problem.

It would list it as an Application Error and the crash log would look like this:

Faulting application name: csgo.exe, version: 0.0.0.0, time stamp: 0x55ce3d41
Faulting module name: tier0.dll, version: 0.0.0.0, time stamp: 0x55f736b2
Exception code: 0x40000015
Fault offset: 0x00020ffe
Faulting process id: 0x6a4
Faulting application start time: 0x01d109ec8055a608
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\bin\tier0.dll
Report Id: f98d5acf-7613-11e5-850c-448a5b64fd36

 

[SigmaMX]

Thanks for the follow up Ric!

https://www.dropbox.com/s/pt1dwgu51dtfu6m/061917-13712-01.dmp?dl=0

Here's the last DMP from my BSOD Code 3B. Now its BSODing all over. I updated all driver files, cleaned registry and checked for SSD performance and so far no issues.

 

[Ric]

That last dump, this is what was revealed:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002eab63c, Address of the instruction which caused the bugcheck
Arg3: fffff8800881fb90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

The process that caused it: csgo.exe.

There's a bit more to this. I'll look at it again when I get back from dinner. Hopefully, we'll get your problem resolved because that sure is an annoying ****ing issue.

 

[Ric]

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

0x%08lx and %s are format specifiers. Both of those should translate into a hexadecimal 32 pointer value. Essentially, what's happening is a driver is causing a kernel mode access violation.

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: csgo.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002eab63c

If I had to guess, I'd start with taking a look at the recent Windows updates, or any updates you did, and roll them back to the last time you remembered playing uninterrupted.

Then I'd take a look into the video drivers, video card, and RAM.

Let me know.

 

[SigmaMX]

If I had to guess, I'd start with taking a look at the recent Windows updates, or any updates you did, and roll them back to the last time you remembered playing uninterrupted.

Then I'd take a look into the video drivers, video card, and RAM.

Let me know.

Well, I did a RAM test and everything was fine. Im guessing my GPU is starting to die, so Im gonna try get a new one and we'll see whats up

Thanks for the help Ric!

 

[Johnny]

SigmaMX I looked at that dump file and that is either caused by a bad stick of RAM or poor overclocking. I don't know what kind of memory test you performed but the only reliable memory test is to shut the system off, take out one stick of RAM, turn the system back on and play. If you keep getting crashes put the stick of RAM back in and take out the other stick of RAM and go back to gaming. This is assuming you have at least 2 sticks of RAM.

If you have overclocked anything then undo all of that.

 

[Dr. Havok]

Sorry for being late to the game here. I would suggest doing these 4 things and seeing if it helps.

1) Like Johnny stated, undo all overclocks and see how it runs.
2) Ideally you want your RAM to be of the same brand, model, speed, version/date, so go to one stick for now if you are mixing
3) Double check that PSU you just picked up. I have ran into many bad brand new PSU's before.
4) Run off of one harddrive (preferably your SSD) for quicker testing and to test for a possible faulty HDD. Even if your OS is not on an extra drive and its failing, it can impact many things on your box.

 

[SigmaMX]

Thanks guys.

I'll do all that and post the results!

 

[SigmaMX]

LOL I feel so dumb.

Yup, I had 2 different RAMs. I removed the older and SHAZAM everything is fine. No crashes, no BSOD, all love and cookies.

I'll get more RAMs with the same brand and model as the HyperX I already own.

Thanks everyone for all the help. I've been crying for months because of this and now I'm PC Master Race again.

Cheerz.

 

[Snipeye]

Curious; did you put the two sticks of RAM next to each other in the slots, or in every other slot? But yeah, you got it going forward; upgrade using similar sticks of RAM.

 

[SigmaMX]

Curious; did you put the two sticks of RAM next to each other in the slots, or in every other slot? But yeah, you got it going forward; upgrade using similar sticks of RAM.

I actually put both sticks on the pair slot, like blue and blue. And it worked fine for over a year, until it didnt :v

 

[SanoNTX]

Interesting that the RAM was at fault for not being the same brand and such. I agree with using all the same variants for RAM as well. Glad to see you fixed your problem ^_^

 

[Johnny]

The brand doesn't matter. The important things are frequency, voltage, and latency. His memory controller is on his CPU and it is only promised to work with ddr3 1333 and 1600 @ 1.5V. Most people have no idea where their memory controller is located and will go by the motherboard supported memory specs to choose their RAM. Poor practice in my opinion.

 

[SigmaMX]

The brand doesn't matter. The important things are frequency, voltage, and latency. His memory controller is on his CPU and it is only promised to work with ddr3 1333 and 1600 @ 1.5V. Most people have no idea where their memory controller is located and will go by the motherboard supported memory specs to choose their RAM. Poor practice in my opinion.

I honestly have no idea whats that all about, but i want yo learn... Any reading you could recommend, man?

 

[Johnny]

Just keep being a gaming enthusiast and building those rigs. You'll learn along the way. I don't really have any recommendations for reading material bc studying is lame.

 

[SanoNTX]

Just keep being a gaming enthusiast and building those rigs. You'll learn along the way. I don't really have any recommendations for reading material bc studying is lame.

Agreed! If you really want to learn, just keep doing! I learned computer stuff along the way from the age of 9 when I got my first system. Still learn new things everyday! I took A+/NET+ courses in high school and learned from those, but it still didn't beat what I learned on my own from hand-on experiences.