Windows 7: Random BSODs and Crashes (in-game/idle/browsing)

Muggie · 24 Jun 2012

Hello.
I am having some crazy BSODs and crashes in my PC since like one month ago. I've even bought a new PSU and reinstalled Windows (less than 24 hours ago), but nothing has changed. Actually, It just gets worse. When I play games, most games that require a good PC crash, like Team Fortress and CoD MW3 (hl2.exe has stopped working/iw5mp.exe has stopped working), and BSOD while playing Diablo III and GTA IV. These are like the only games I'm playing nowadays.

My PC Specs:
AMD Phenom II X4 965 Black Edition (Age: ≃ 8 months)
2x2 4GB DDR3 RAM (Age: ≃ 8 months)
Motherboard Biostar TA890GXB HD (Age: ≃ 8 months)
PSU Corsair TX650M (Age: ≃ 24 hours)
Graphics Card ATI Radeon HD 5770 VAPOR-X SAPPHIRE 1GB DDR5 (Age: ≃ 2-years-old)

The graphics card is the oldest component and I have had some BSODs that mentioned AMD .dll files, so I think it could be the problem, but anyway... Can any of you analyze it, please?

Windows 7 Home Premium x64

FredeGail · 24 Jun 2012

Hello Muggie and welcome to Sevenforums.

BSOD Report

There's a few things to look out for here, hopefully I'll get some conclusions on them.

Drivers to be aware of

Code:

BIOS64   BIOS64.sys   Sun Jun 08 02:12:00 2003 (3EE27F50)
----------------------------------------------------------------
klif     klif.sys     Wed Apr 20 12:34:31 2011 (4DAEB6B7)
----------------------------------------------------------------

Your BIOS64, is a Biostar product. I have yet no experience with this product, but it seems like it's some sort of an I/O driver. See if you're able to update it. BIOSTAR :: Download
Kaspersky, klif.sys, is a known BSOD causer. If you want a stable security software, you should go for software like MSE. Use the Kaspersky Uninstall Utility. If you have purchased Kaspersky, consider contacting their Support.

Bugcheck

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PROCESS1_INITIALIZATION_FAILED (6b)
Arguments:
Arg1: ffffffffc0000428, Indicates the NT status code that caused the failure.
Arg2: 0000000000000003, (reserved)
Arg3: 0000000000000000
Arg4: 0000000000000000

You have had the PROCESS1_INITIALIZATION_FAILED (6b), which indicates problems with Harddisk or cable problems, usually. Make sure you're not having a disk without power from the PSU. It happens that you remember to plug the SATA cable in the Harddisk, but forget to power it up.
This counts for the Disk Reader too - at least what I know from experience.

Also go to BIOS, and ensure you're having the Boot-device as number 1 on the Boot-priority.

Another bugcheck you have experienced, is the c0000221, though, windbg has a hard time discovering the exact information on it. Overall it also carries errors on the harddisk.

Disk checking

For disk checking you should have a look on this tutorial, it doesn't harm.

Disk Check

Summery

Code:

Unknown bugcheck code (c0000221)
Unknown bugcheck description
Arguments:
Arg1: fffff8a000141610
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
-----------------------------------------
Unknown bugcheck code (c0000221)
Unknown bugcheck description
Arguments:
Arg1: fffff8a000202160
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
-----------------------------------------
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000306a
Arg4: 0000141b000020d4

Memory management
At last have a scan with Memtest86+ and leave it for 7-8 passes. One of the bugchecks includes the popular Memory_management 1a.

Memtest86+ - Advanced Memory Diagnostic Tool

Thanks for the provided information.

Best Regards,
Frederik.

Muggie · 24 Jun 2012

Thanks for the repply.
About the BIOS64.sys, I've just updated it, but I was already having problems before (actually that's why I updated)
And for the Kaspersky... It could really be the problem. I mean, I never had any of these problems 'til I bought this. So I lost 30 dollars? :S

For the Disk Checking... I ran chkdsk /r when I reinstalled Windows and the problem persists.

But thanks anyway. I will run memtest86+, but I used that one from Windows and It didn't point any errors. I will try it again.

FredeGail · 24 Jun 2012

Quote: Originally Posted by Muggie

Thanks for the repply.
About the BIOS64.sys, I've just updated it, but I was already having problems before (actually that's why I updated)
And for the Kaspersky... It could really be the problem. I mean, I never had any of these problems 'til I bought this. So I lost 30 dollars? :S

For the Disk Checking... I ran chkdsk /r when I reinstalled Windows and the problem persists.

But thanks anyway. I will run memtest86+, but I used that one from Windows and It didn't point any errors. I will try it again.

There's a good amount of chance that the problem lies in Kaspersky. If you want to keep the software, I recommend calling or writing an email to their Costumer Service. I'm sure they'll treat you well as you paid for their software.
Make sure that it's updated to the fullest edge also.

Keep uploading new .dmp files in-case of BSOD.

Best of luck!
Frederik.

Muggie · 24 Jun 2012

I uninstalled Kaspersky and ran CCleaner to delete any remaining registry entries. No BSOD yet. I will try to play Team Fortress 2 and see if it doesn't crash anymore.

But until the moment, everything seems to be OK.

Muggie · 24 Jun 2012

Ok, now my game didn't stop working, but this occurred: “Display driver AMD stopped responding and has recovered”.
I think it is the same of "hl2.exe has stopped working.", but now the "real error" has appeared (in my opinion). What do you think?

Muggie · 24 Jun 2012

Game crashed...
Kaspersky mustn't be the cause. I'm really doubtful about my Graphics Card.
Am I the only one that has realized EVERY SINGLE THREAD about games crashing and BSODs has "ATI RADEON" name on it? I mean, nobody who owns a nVidia VGA has these problems, seriously.

Muggie · 24 Jun 2012

New BSOD while the PC was idle! Posting dump file...

FredeGail · 25 Jun 2012

Hi Muggie,

BSOD Report

Update your Graphic Driver

We want to get your Graphic Drivers a clean reinstall. Left-over files are the ones we want to avoid. Let's go through a tutorial that'll show you.

i) Make your way to Nvidia Driver Page
ii) Uninstall the one you currently have and all its extensions
iii) Download Driver Sweeper
iv) Get to safe mode (without network) and search for Driver Sweeper in your

v) Select all the ATI components and analyse them
vi) Clean them, head into Windows without internet and download the driver.

"Maybe" corrupted Windows

Your dumps points to your Windows, this is likely caused by it cannot find the real driver to trick the cause on, though - it's worth checking if Windows is working as it should.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

This is the most common command to use. It scans for corrupted Windows files, and tries to repair them.

SFC /SCANNOW Command - System File Checker

Memory

Your memory still reports issues, if you haven't been running the Memtest86+ for more than 6 passes - I recommend doing so.

Best Regards,
Frederik.

Muggie · 25 Jun 2012

I'm having some problems to reinstall ATI drivers, but I think it is not the problem (I've just reinstalled Windows).
When I try to enter in safe mode, the system crashes in driver CLASSPNP.SYS and then I can't do anything but try again. After some time, I couldn't even head into Windows anymore. I recovered the system to what it was before I reinstalled ATI drivers and the system worked again.

Windows 7: Random BSODs and Crashes (in-game/idle/browsing)

Random BSODs and Crashes (in-game/idle/browsing) problems?