Freezes while playing minecraft and a recent bsod(0x000000d1)

ant9985 · 21 Jul 2014

Hello all. Sorry for wall of text but I want to give as much info as possible.

I don't remember what I was doing while I had the bsod on the 17th July, but I remember the system freezing twice while playing the game Minecraft. I have had this computer over a year and have played Minecraft for a long time without problems though. The freezes only started recently, after the bsod perhaps.

Description of freeze: Minecraft will freeze then turn white after a little while, I will still be able to move my cursor but nothing I click on will work.

The first freeze I had, I pressed the reset button, but it was very slow to load, didn't get to the motherboard logo screen before I pushed the power button to turn it off. It first displays numbers very fast at bottom right(this is normal) and hanged at A2(before I turned it off). Then computer was fine for days.

The second freeze, I waited and after maybe 5 minutes, there was a blue screen, but it had no error code. It said it was collecting bug report info or something(took a long time about it too, I'm not sure if it got anything) and it suggested I try a windows repair. When it had finished, my computer restarted, but it was slow again, but I waited this time, and it failed to boot and gave a screen I don't remember, probably suggesting fixes. Actually I think it said it failed to boot because a file was missing(didn't give file name I don't think). Maybe that was the screen that suggested a repair.
So i tried inserting the win7 dvd and selecting language and clicking repair my install. It gave me a weird message saying it was incompatible with my windows, yet it is the same disc I used to install windows.

I tried googling the incompatible windows dvd and someone suggested the boot order in the BIOS needs to have your windows hard drive as the primary boot option for repair to work. I looked in BIOS and it says UEFI hard drive as the first boot option. Idk if this is my primary/windows drive(I have two) which is an SSD, but I know my other drive was listed later, so i doubt it's my second drive. I just wonder if there is some sort of problem with it since the BIOS isn't giving me it's actual name, just UEFI hard drive w/e that is.

System spec.:
Processor: Intel Core i5-3570k 3.4GHz
Installed memory (RAM): 8GB
System type 64-bit Operating System(windows 7 Home premium)
Graphics card: Nvidia GeForce GTX 660
Primary hard drive(windows): Samsung SSD 840 PRO Series
Secondary hard drive: I forget
Optical drive: LG super multi dvd-RW
Motherboard: Z77A-GD65 Gaming(MSI)
Sound: Sound Blaster Z
Antivirus: Kaspersky Internet Security 2014

Thanks very much if you took the time to read, I appreciate it.
I'm very worried because after the freezes, it seemed like the problems continued all through the blue screen and restart process, seems serious.

Arc · 21 Jul 2014

Hi ant9985.

The recent BSOD is caused by Killer e2200 driver.

Code:

BugCheck D1, {fffff88009261000, 2, 0, fffff88004a6ffa0}

*** WARNING: Unable to verify timestamp for e22w7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
Probably caused by : e22w7x64.sys ( e22w7x64+19fa0 )

Followup: MachineOwner
---------

Which is sort of old.

Code:

    Image name: e22w7x64.sys
    Timestamp:        Wed Dec 05 22:13:48 2012 (50BF79C4)

Update it from Driver Downloads | Qualcomm Atheros, Inc.

Also Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Let us know the result.

ant9985 · 21 Jul 2014

Thanks so much Arc.

Can I ask, did it take a long time to learn how to read these logs I attached?

Also, I never use that program you listed. Would it be ok to untick it from msconfig and not use it again? Or do I need to update the driver for it to stop the bsods?

Edit1: I've disabled all but windows operating system like you've said. Only Nvidia geforce experience still starts on it's own(has item in system tray and has NvBackend.exe in processes menu). Also, I didn't see an option for my Kaspersky security in my msconfig startup tab which makes me think there are some hidden startup programs.. Any way I can unhide them so I can disable Nvidia geforce experience?

Arc · 22 Jul 2014

Reading dumps may take a time, depends on how much you are doing. It is like learning mathematics or literature or fine art. Nothing very special.

The program/driver that I listed is your onboard network adapter. Are you sure that you never use it?

I checked your system again; you dont have any alternative way to connect to the network.

I suggested for the update because it is a must. If you dont want/need to connect to internet, you may disable it in msconfig.

In you msconfig startup tab, uncheck all, accept > OK. You dont need any of them, and there is nothing hidden other than those.

The other things you are finding are services. As far as there is no problem, let them be as they are.

ant9985 · 22 Jul 2014

Thanks for replying again.

Oh ^^ I assumed it was 'Qualcomm Atheros Killer Network Manager' listed in msconfig. I guess they are not the same thing as when i clicked it's system tray icon it gave me info about my pc that i didn't really need. So I removed it from msconfig startup and it doesn't appear in system tray any more, but I am still able to connect to the internet, so I guess it wasn't needed but is just some software that came with the things you mentioned?

I'll update the driver for my network card then. Don't think I need the network manager in startup thought right?
Your help is appreciated :) thanks.

Arc · 22 Jul 2014

Yes, the network manager is a bloated program included in the killer driver. It is not only unnecessary, but problematic. It contains Bigfoot network bandwidth controller which is a real problem when it is in action, like all the other programs of the same line.

Good job on removing it from startup. The bandwidth controller will not be active automatically anymore. :)

Let us know for any further BSOD.

ant9985 · 22 Jul 2014

Thanks a lot! for the info, and will do :)