Getting errors on my PC now

futurefields

Diamond Member
Jun 2, 2012
6,470
32
91
I think I might have a bad memory stick or something, I don't know. I noticed some games kind of running dodgy. So i try to run the Memory Stress Test in Intel XTU and it crashes everytime.

This morning I just tried to load up a bot match in Advanced Warfare and it blue screened just as the game was set to load, got this error:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: c5
BCP1: 0000000200000001
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF800030079BC
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1





Any insight?

Also Im not sure how i can test a bad ram stick. I only have 8gb of ram, 2 sticks. If I take one out, I will be down to 4gb which means most of my new games wouldnt run well anyways.
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
how
I think I might have a bad memory stick or something, I don't know. I noticed some games kind of running dodgy. So i try to run the Memory Stress Test in Intel XTU and it crashes everytime.

Also Im not sure how i can test a bad ram stick. I only have 8gb of ram, 2 sticks. If I take one out, I will be down to 4gb which means most of my new games wouldnt run well anyways.

Well, even with just 4 GB a game will run, but if it is your ram causing problems, you will need to figure out if it is one of them or both of them, and get it (them) replaced.

Windows has a built memory test that can be configured on long it runs to try to generate an error.

http://www.howto-connect.com/windows-10-detect-ram-issues-with-windows-memory-diagnostic-tool/

Alternately, you can download and use Memtest86:

http://www.memtest86.com/

Lastly, you can download WhoCrashed and see if it can provide any additional info on the crash:

http://www.resplendence.com/whocrashed
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Well, the only decision you need to make is to replace both sticks, or test them one at a time. Running slower may be a pain, but it's better than all your games crashing, isn't it?
 

futurefields

Diamond Member
Jun 2, 2012
6,470
32
91
I ran the memory test in Windows 7 (mdsched.exe) and it said no errors were detected. Is this sufficient to be trusted that I don't have any actual errors on the RAM?

Another symptom is my display driver has been randomly crashing (its actually the thing that crashes when I try to run the memory stress test in Intel XTU) I havent tried reinstalling or updating my video drivers yet though because it just seems like something like that wouldn't cause these problems.
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
If you run the original memory stress test again, do you still get errors?
 

futurefields

Diamond Member
Jun 2, 2012
6,470
32
91
The intel XTU one?

Just ran it. It crashed again.

Ra2JiIW.png


Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: perftune.exe
Problem Signature 02: 5.2.0.14
Problem Signature 03: 5551759e
Problem Signature 04: PerfTune
Problem Signature 05: 5.2.0.14
Problem Signature 06: 5551759e
Problem Signature 07: 28
Problem Signature 08: 10
Problem Signature 09: System.InvalidOperationException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
 
Last edited:

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
The intel XTU one?

Just ran it. It crashed again.

Download WhoCrashed in the first post I responded to (post #2), and see if it can narrow down the source of the crash.

I ran the memory test in Windows 7 (mdsched.exe) and it said no errors were detected. Is this sufficient to be trusted that I don't have any actual errors on the RAM?

Generally when testing for RAM errors, you want it to test the ram for a few hours (looping) to see if it can generate an error.

Are your CPU temps good?
 
Last edited:

futurefields

Diamond Member
Jun 2, 2012
6,470
32
91
Yes CPU never runs nice and cool never seems to go over 60 degrees. I will check out that Who Crashed program next.
 

futurefields

Diamond Member
Jun 2, 2012
6,470
32
91
Here's some WhoCrashed report after clicking analyze:


System Information (local)
--------------------------------------------------------------------------------

computer name: MEGATRON
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, Z77 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8540737536 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 5/30/2016 2:36:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053016-19078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0xC5 (0x200000001, 0x2, 0x0, 0xFFFFF800030079BC)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 5/30/2016 2:36:52 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x19940D)
Bugcheck code: 0xC5 (0x200000001, 0x2, 0x0, 0xFFFFF800030079BC)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 350.12
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 350.12
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_CORRUPTED_EXPOOL





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 350.12 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 

futurefields

Diamond Member
Jun 2, 2012
6,470
32
91
I tried updated my Nvidia driver, symptoms are exactly the same. I have Windows 7 updating disabled. I just get a few of the updates when I do a fresh install of Windows 7 and then I disable it after that.
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
I tried updated my Nvidia driver, symptoms are exactly the same. I have Windows 7 updating disabled. I just get a few of the updates when I do a fresh install of Windows 7 and then I disable it after that.

What are the model numbers of your video card and power supply, and how long have you had them?
 

futurefields

Diamond Member
Jun 2, 2012
6,470
32
91
EVGA GTX 970 SSC and Rosewill Capstone 650 (650 watt 80+ gold). I've had the power supply since 2012, the GPU since 2015.
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
If your system was stable up until the recent crashes, and the crashes seem to happen when you place a load on your system (Intel XTU), my first guess would be your PSU is beginning to be flaky.

PSUs that don't just suddenly die, tend to start causing system crashes and instability (especially with a higher load) on their march to death.

If you have another PSU, or have a friend with one you can test with, that would be my first troubleshooting step if that was happening to my system.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,587
10,225
126
That's clearly a GPU VRAM or system RAM error, which could be caused by a flaky PSU. Or a bad GPU or RAM stick.
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
That's clearly a GPU VRAM or system RAM error, which could be caused by a flaky PSU. Or a bad GPU or RAM stick.

Agreed, has to be one of those three with the GPU or PSU at the top of the list. I had a XFX 7850 video card do that exact same thing, and I RMAed it. They ended up sending me a brand-new unit so I guess it wasn't fixable.