BSODs for Quite Some Time, potential e1c62x64.sys issue

[Femur68]

Hello sevenforums,

I come to you with an issue I've had for awhile with my custom built PC. On occasion, my PC will BSOD completely out of nowhere. It doesn't seem to matter what I'm doing on my PC. Whether it's browsing the web, playing video games, or doing schoolwork, it'll BSOD.

Over the past few days (as you'll see in the .zip I've attached) the crashes have spiked tremendously, so I'm finally looking to get this issue resolved once and for all. I attempted to solve the issue myself first, but to no avail. This is what I've done so far.

1. I found a helpful thread here on the sevenforums via google that gave me a start on figuring out what was causing the issue.

2. I downloaded the windbg (Windows Debugger) tool as the guide said, and followed the steps to get it set up to read my .dmp files (I already have Visual Studio installed).

3. Whenever I go to open up .dmp files though in the tool, it says that the symbol path is invalid, even though I set it to SRV*c:\symbols*http://msdl.microsoft.com/download/symbols just like the guide states (I also found a couple other sources that said to set it to the same thing). Here is an image of what I get when I attempt to open the file.

4. However, despite it saying there was an invalid symbol path, it spits out this exact line shown here. The guide I was using said that the very same line would appear in my file if a driver or program is causing the issue. I'm not sure if this e1c62x64.sys reason is the true reason behind my crash (and wasn't some sort of by-product of the debugger tool failing to fully open the file due to an invalid symbol path). But, I will say that when my computer last crashed this morning, I can say with ~90% confidence I saw the e1c62x64.sys issue pop up on the physical blue screen right before the computer shut off.

5. So, this guide stated that I should check out this Driver Reference Table here if this appeared to be the issue for my system. After searching the list for a bit, I found a few things that might be the cause of the crashes.

a. amdkmpfd.sys - This is associated with my AMD graphics card.
b. atdcm64a.sys - This also appears to be associated with my graphics card.

6. I went to the AMD website, updated my graphics card driver, and yet it still crashes. I'm not sure if there is something else in my system causing this issue that's on that Driver Reference Table I haven't found yet, or if the issue might be something non-driver related.

I have attached the .zip of all my previous .dmp files created from previous crashes (yes, there's a lot of them). I was hoping someone on here could crack a few open and help me figure out what's been causing this issue. Any help on this topic would be greatly appreciated.

 

[Pauly]

All of your dump files are stating errors 0xD1 & 0x9F which are both driver related and all are blaming the driver you listed which is dated e1c62x64.sys Tue Sep 21 22:34:15 2010 which is your intel gigabit network driver

Try updating this driver first and see if it helps the situation

Can you post a shot of your disk management as well please as I noticed this in your system info

Total Physical Memory:     16,351 MB
Available Physical Memory: 13,624 MB
Virtual Memory: Max Size:  33,212 MB
Virtual Memory: Available: 30,210 MB
Virtual Memory: In Use:    3,002 MB
[B]Page File Location(s):     C:\pagefile.sys[/B]
[B]                                         F:\pagefile.sys[/B]

 

[Femur68]

Alright I updated that driver. Hopefully that solves the issue finally.

Also, was this what you were looking for?

Image 1

Image 2

 

[Femur68]

Update: Looks like the problem hasn't been solved. My PC just BSoD'd again.

Just to verify I am updating the correct driver, I went to Intel's website here, downloaded their driver update utility, located the driver that needed updating, and updated it.

Here's a screenshot of the driver update utility. Before I updated the driver, the installed version was something insanely outdated, was version 11.1 if I remember correctly.

I attached the latest .dmp file the PC generated. I doubt it's any different, but who knows.

 

[Pauly]

To see disk management window click start then type diskmgmt.msc maximize window and take a snip
Your C drive is way to full, you need plenty of space there to allow for pagefile & hiberfile etc, please free up space on that drive, this may also explain why your pagefile is split is across drives/partitions but cant be sure until we see disk management screen
Heres mine so you know what we are after - the circled bit is whats important so make sure that text is on view
View attachment 366632

Please upload snips directly to your post its much easier to view
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Your most recent dump is exactly the same and the driver is still dated 2010 so has not updated

 

[Femur68]

Alright, here's my disk management:

It does look like stuff is split. I'll try and make some more space on my SSD. Is there a recommended % capacity I try and keep it under?

Also, was there something wrong I did when I updated my driver before? Was that not the correct driver I had to update before (shown in the image posted in my third post), or was my process in updating that driver incorrect?

 

[Femur68]

Update: I went back and attempted to upgrade my network driver again, it was giving me the error "The installed version of Intel Proset is not supported for upgrades." So as per this thread on the the Intel forums here I uninstalled the Intel Proset software and then attempted to reupdate my gigabit network driver, and it appears to have updated successfully.

Proof:

 

[Pauly]

Personally I would leave 10-15GB of space to be safe, this gives windows plenty of room to work with.
Unless you have an operating system on your F drive then it should not be marked active, see this to change it
http://www.sevenforums.com/tutorials/197157-partition-mark-inactive.html

If you run the collector tool again we can verify the exact driver that has been updated, any more crashes since last time ?