• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Problem Solving

J

Jerrin

Weaksauce
Joined
Jun 29, 2007
Messages
93
Hi All.

I've been struggling with some system instability for a little over a month. I've been working to eliminate the VC and memory. I think I may have stumbled across the problem.

I've noticed that my machine shows both disc drives (2 SSDs) but gives me the option to disable my main system drive. Almost like it is plug and play (says removal policy "better performance"). The other drive, my "steam" drive looks normal to me and just says "Enable write cashing on the device." It makes no reference to removal.

As far as my IDE/ATAPI controllers, I have: Intel 7 series/C216 Chipset family SATA AHCI controller 1E02 and "Standard SATA AHCI Controller.

I also notice that I have As media USB 3.0 eXtensible host controller (Microsoft) as well as Intel 7 Series/C216 Chipset family USB enhanced host controller.

I'm wondering if I have some strange conflict that is making my drives go crazy and cause freezes in some games. Any ideas?

For the record, I have a 3770K on an asus Maximus Gene with 16 gigs (2x8 sticks) of ram.
 
Have you checked SMART values for both drives to ensure one/both aren't dying? Verified connections and cables look good? What two types of drives? Have you tried removing data drive and seeing if problems persist? If they do, try swapping it to the other controller to identify if its a drive or controller issue?

Can you please explain 'drives crazy' a bit more specifically?
 
Last edited:
I suggest to check the Windows event log as it usually contains at least some hints if storage is the problem.
What makes you think it is related to your drives in the first place?

What I basically suggest is to disable the Asmedia SATA controller in BIOS and connect your drives to the PCH ports (should be the two red ports in the middle).
From what you wrote you do not have more than 2 drives. If you have a DVD or bluray drive, connect it to one of the black ports.
 
Last edited:
Thank you for the replies.

What is the best way to check the smart info and the windows event log? I admit I'm still trying to get used to windows 8.1.

A few years ago, I had a desktop that changed the drive names on occasion and caused some crashing. After I changed how they were plugged in, everything seemed to resolve. I'm thinking that may be the cause here or the interplay between the Intel and Asmedia solutions.

I read the manual and it seems, based on the physical locations of the plugs, I do have one SSD plugged into the Asmedia and one into the Intel slots (6gb SATA). The blu-ray drive is connected via the black port.
 
What is the best way to check the smart info
Click to expand...

There is a free program called:
CrystalDiskInfo


and the windows event log
Click to expand...
Right click on This PC or select it in explorer and click Manage.

Then Event Viewer

then Windows Logs

and look at System
 
Ok, this was very helpful. I think I see the problem, or at least one of the major problems.

In my system logs I can finally see the application errors. Namely several of my games, though not all, have been "freezing" which necessitated a reboot. The thing in common that many, though not all, of the errors have is: faulting module name: KERNALBASE.dll

In addition, the reocurring exception codes are: 0xe06d7363, 0xc0000005, and 0xc000041d. Primarily the first two.

Now I'm going to give CrystalDiskinfo a try.
 
CrystalDiscInfo shows my system drive health status is 100% and my game drive is 93% Both are SATA/600.
 
The one SSD for some reason has been detected as a removable drive. You can change this by changing a setting in the registry.

The other thing that can cause this is if you do not have all your drivers installed. Did you install the Intel RST driver? I am guessing no.

After that is installed, open up an administrator command prompt and type:
chkdsk /f c: (substitute the drive letter for the drive you want to scan. Do this for both drives). The non-boot drive will scan without a reboot. The boot drive will say it can't do it and ask if you want to do the scan on a reboot.. say yes and then do a reboot.
 
Thank you Cyclone3d.

Installed the driver off of Asus's support website and ran chkdsk on both drives.


Now I need to figure out what to do about the reoccurring errors and exception codes. Any ideas or common areas to check first?

Looks like changing the connections for the drives fixed the eject option for my system disc as it no longer shows up as an option.
 
Last edited:
Jerrin said:
Thank you Cyclone3d.

Installed the driver off of Asus's support website and ran chkdsk on both drives.


Now I need to figure out what to do about the reoccurring errors and exception codes. Any ideas or common areas to check first?

Looks like changing the connections for the drives fixed the eject option for my system disc as it no longer shows up as an option.
Click to expand...

Can you copy all of the info listed in those errors in event viewer and post here?
 
Here is the most recent error. Kicked me out of the game.


Log Name: Application
Source: Application Error
Date: 5/28/2014 10:07:18 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Description:
Faulting application name: JustCause2.exe, version: 1.0.0.2, time stamp: 0x4c1b5791
Faulting module name: JustCause2.exe, version: 1.0.0.2, time stamp: 0x4c1b5791
Exception code: 0xc0000005
Fault offset: 0x0051eeb5
Faulting process id: 0x119c
Faulting application start time: 0x01cf7ae8fa441053
Faulting application path: E:\Program Files (x86)\Steam\steamapps\common\Just Cause 2\JustCause2.exe
Faulting module path: E:\Program Files (x86)\Steam\steamapps\common\Just Cause 2\JustCause2.exe
Report Id: 5763404a-e6de-11e3-bf50-c86000c0c619
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-05-29T03:07:18.000000000Z" />
<EventRecordID>22198</EventRecordID>
<Channel>Application</Channel>
<Security />
</System>
<EventData>
<Data>JustCause2.exe</Data>
<Data>1.0.0.2</Data>
<Data>4c1b5791</Data>
<Data>JustCause2.exe</Data>
<Data>1.0.0.2</Data>
<Data>4c1b5791</Data>
<Data>c0000005</Data>
<Data>0051eeb5</Data>
<Data>119c</Data>
<Data>01cf7ae8fa441053</Data>
<Data>E:\Program Files (x86)\Steam\steamapps\common\Just Cause 2\JustCause2.exe</Data>
<Data>E:\Program Files (x86)\Steam\steamapps\common\Just Cause 2\JustCause2.exe</Data>
<Data>5763404a-e6de-11e3-bf50-c86000c0c619</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
 
ok, it could be the video drivers or maybe the chipset drivers. Did you install the chipset drivers for your motherboard?

What video card do you have and what version of drivers are you running?

It could also be a bad stick of RAM, but I want to verify other stuff first.
 
Yes, I installed the newest drivers on the Asus website. I have a Gigabyte GHZ edition GTX 780. I'm using the new drivers that were just released.

For tonight, I'll go ahead and run prime all night and list any errors if any.


Latest freeze, no error listing, but a warning:

Log Name: System
Source: Display
Date: 5/29/2014 12:12:53 AM
Event ID: 4101
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-05-29T05:12:53.000000000Z" />
<EventRecordID>24226</EventRecordID>
<Channel>System</Channel>
<Security />
</System>
<EventData>
<Data>nvlddmkm</Data>
<Data>
</Data>
</EventData>
</Event>


I have 78 of these warnings, caused by the exact same thing. They start the day I added the new video card. April 8th.
 
O.k.... Do you have the latest BIOS installed for your motherboard?

What is your power supply?

How is airflow through your case?

What temps are your CPU and GPU running at?

What CPU cooler do you have?

What are the rest of your system specs? Are you overclocking?

Did you reset the BIOS when you installed the new video card?
 
Yes, I updated my bios to the latest on the website.

Right now the case is open to air as I have one panel off. It seems like airflow and cooling are ok, based on the bios reports. What's a good program to monitor that while in windows?

I have a nocua D-14 for cooling and I am gently overclocking the CPU (turbo boost to 4.1), but not the video card.

I did not reset the bios. Should I do that? Is that something that should be done with a new videocard?

I'll report what prime did later tonight.
 
Sometimes a motherboard will not redetect stuff properly when a card is switched out. That is why I asked if you reset the BIOS. I kind of doubt that is what is causing your problem though.

Go ahead and test your RAM. Use HCI memtest. You will need to run multiple copies to test all of your RAM. A single error means you have a bad stick.

http://hcidesign.com/memtest/

Also, you did not answer all of my questions.
 
Sorry I missed the temps and the power supply question.

The highest I've ever seen the cpu get is 74C and that was after running the new heaven benchmark for a couple of hours or so. When I was running the Gigabyte monitoring program, the temps on the VC seemed very reasonable, less than 70C. To be sure, I'd probably need an active monitoring program after gaming for an hour or two.

Power supply is a Seasonic Gold X750.

Results from Prime 95 (using blend option) "Torture test completed 587 tests in 10 hours 44 minutes - 0 errors 0 warnings."
 
ok, Go ahead and do the RAM test I linked.

One other thing I came across if that doesn't show anything up is that .NET might be corrupted. I saw some posts where people uninstalled all .NET stuff and re-installed and it fixed it.

Another thing you could do is run a system file scan and see if it picks anything up.

admin command prompt and type in:
sfc /scannow
 
Ok, I ran the scannow and got:

"Windows Resource Protection did not find any integrity violations."

Question: what do the .net showup as when looking at programs to uninstall? Are they the XNA Framework Redistributable 3.1 and 4.0?

I don't mind trying to uninstall them and re-install if that might work.

I'll leave the ram test you linked on overnight and update you tomorrow morning.
 
Ran 8 threads for a little over 10 hours. Average for each thread was 661% of 1500mb.

0 errors on all threads.
 
The .NET stuff should show as

Microsoft .NET Framework ............

I think the RAM should be good since you didn't see any errors. HCI usually shows up errors within a few minutes. You did only test 12GB though. Still I think you should be OK.

Next thing is to write down all your current BIOS settings and then reset the BIOS to see if you get any error when running at stock speed.
 
There is nothing in my uninstall list that says, Microsoft .NET Framework. If it's supposed to show up, I can see what one problem may be....

I'll try the bios reset this evening. I appreciate your help with this.
 
Ok, I visited Microsoft's site and read up on how to look for .net in the registry. Looks like I have a few versions, apparently ending with 4.5. I have one v.4 and one v4.0. Though the version key is different in both.

I also reset the bios.
 
Last edited:
You can alternatively try to set back your RAM frequency to 1066Mhz or 1333Mhz.
 
I used a program to remove the Nvidia drivers, delete the NV folder, and clean the registry. I then reinstalled the latest drivers using a clean install. Afterwards, I tested one of my games that locked around every 15 minutes in; I played for 2 hours without a glitch or freeze. After I do a few more hours of testing, to try and make sure, I'll update.

Thank you all for your help thus far.


UPDATE: Didn't work, still freezes. What program do you recommend to run in the background to monitor temps while in game or tabbing out? Perhaps things are getting too hot.
 
Last edited:
What exact board is it? IV gene? I had iv extreme p 67 with same issues. It was definitely the motherboard and seemed to be voltage/bottleneck issues. Anything intensive would freeze the system for a few secs or I would get the tdr issue with my 680. I swapped everything on the board along with psu and same issue. The board completely died 2 months later and a**holes at asus wouldn't rma it even thou it was 6 months old. They said they "couldn't find the serial # in their system" although I sent them copies of the receipt and pics of the the boards stickers...
 
You must log in or register to reply here.
Back
Top