Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Replaced several parts, but I am still getting BSOD


  • Please log in to reply
23 replies to this topic

#1 worskies

worskies

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 11 January 2012 - 01:21 PM

Let me start off by saying that I've been getting blue screen errors for quite some time since I bought my computer. At first they were somewhat rare, but then became much more common throughout the months. The errors always occurred when I had a video game running, and after searching the stop code on google I found out that my video card was the problem. With that said, I went out and bought a video card. Just last week I installed it. The blue screen problem did not go away though.

Now recently I assumed my hard drive was causing the BSOD. Apart from the blue screen, I was also having problems with my OS starting correctly. I ran a diagnostic test for my hard drive and it failed it twice. So after seeing that, yesterday I went to Best Buy and bought a new hard drive. I backed up everything, created an image of Windows 7, then installed the new HDD and transferred all my content into it.

My computer worked better and I wasn't having problems with Windows, but just a few minutes ago I got a blue screen while playing TF2. The error message was 0x0000007E. I looked up the code and it points to the hardware I already replaced. What could be the problem?

Specs:
Windows 7 64 bit
AMD Phenom II X2 555
ATI Radeon 6770 HD
Seagate Barracuda HDD
Acer S201HL
Gigabyte GA870AUD3

Let me note that I have gotten that specific error code before I replaced any parts.

BC AdBot (Login to Remove)

 


#2 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:11:30 AM

Posted 11 January 2012 - 01:26 PM

First make sure that you have installed the latest drivers (inc. chipset drivers) from the respective manufacturers.

Use BlueScreenView to provide details about your errors.

  • Download the .zip file and extract to a folder on your desktop. Open that folder and run BlueScreenView.exe.
  • After BSV completes its scan, click Edit > Select All. Then click File > Save Selected Items and save the report to your desktop as BSOD.txt
  • Open BSOD.txt in Notepad and copy all of its content to your next reply.

===========================================

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#3 worskies

worskies
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 11 January 2012 - 01:35 PM

Hello again.

==================================================
Dump File : 011112-18860-01.dmp
Crash Time : 1/11/2012 9:52:35 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`032ed03a
Parameter 3 : fffff880`031246f8
Parameter 4 : fffff880`03123f60
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+3d3f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+8603a
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011112-18860-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 276,328
==================================================

#4 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:11:30 AM

Posted 11 January 2012 - 01:51 PM

What antimalware program(s) are you using?

Is the BSOD recurring? If so, does it only recur when you play TF2?

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#5 worskies

worskies
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 11 January 2012 - 02:07 PM

I use Microsoft Security Essentials.

It occurs when I play any video game.

#6 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:11:30 AM

Posted 11 January 2012 - 02:53 PM

If you disable MSE, will it still occur?

Are you using CD emulation software?

Also, is your BIOS set to AHCI and are the appropriate AHCI drivers installed?

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#7 worskies

worskies
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 11 January 2012 - 03:24 PM

Yes. I had BSOD even with other anti-virus programs.

No.

I don't think so. I went into my BIOS and saw IDE. Should it be AHCI instead?

#8 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:11:30 AM

Posted 11 January 2012 - 05:32 PM

Make sure your backups are current.

Instructions on changing from IDE to AHCI: http://windows7themes.net/switch-to-ahci-after-install-windows-7.html

Download and install the latest chipset drivers. http://download.gigabyte.us/FileList/Driver/motherboard_driver_amd_chipset_8-series_win7.exe

Edited by LucheLibre, 11 January 2012 - 05:33 PM.

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#9 worskies

worskies
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 11 January 2012 - 06:06 PM

I'll get right on that. I got a different blue screen a few minutes ago, by the way.

==================================================
Dump File : 011112-18579-01.dmp
Crash Time : 1/11/2012 2:59:25 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`032c1cfe
Parameter 3 : fffff880`098c1800
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011112-18579-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 276,328
==================================================

#10 worskies

worskies
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 11 January 2012 - 06:35 PM

When I was downloading the drivers, I crashed AGAIN. Different one this time:

==================================================
Dump File : 011112-14788-01.dmp
Crash Time : 1/11/2012 3:30:20 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffffff`ffffffd0
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`032806ac
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011112-14788-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 276,048
==================================================

When I restarted, Windows did not start up and I got the error code I explained in my first post. It's running fine now, though. At the moment at least..

EDIT: I ran a Memory Diagnostic Test and I failed it. Could this mean it is my RAM that is the problem?

Edited by worskies, 11 January 2012 - 07:05 PM.


#11 LucheLibre

LucheLibre

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Tennessee
  • Local time:11:30 AM

Posted 11 January 2012 - 10:48 PM

It's odd that before you were only getting BSODs during gameplay. Coincidence I suppose.

At any rate, follow these instructions to narrow it down.

Use MemTest86+ to test your memory for failure.

  • Download the latest version of the Pre-Compiled Bootable ISO (.zip), extract the ISO to a folder of your choice, and burn it to a blank CD. Instructions
  • Remove every stick of RAM except the one closest to the CPU. Remember to keep your arm touching the case as you do this.
  • Boot the affected computer from the CD. Pressing F12 on the BIOS screen is the most common way to bring up the 'boot device' menu. If necessary, adjust your BIOS settings to boot from the DVD/CD drive first.
  • Memtest is designed to repeat its test continuously. It is recommended that you allow the program to complete several 'passes' before declaring that stick of memory error-free.
    • Note: These tests can be very lengthy.
  • If Memtest finds an error, it will list it in red. There is no need to continue the test if an error is found.
  • After several clean passes (or an error), press the power button until the computer turns off.
  • Take out the currently installed stick, install the next stick in its place, and begin step 3 again.
  • Report the results in your next reply.

====================================================

If it looks like I know what I'm doing, there's a pretty good chance the only reason for that is because
I once asked someone to run chkdsk /r and a BC Advisor smacked me in the back of the head.

~ LL ~


#12 worskies

worskies
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 12 January 2012 - 02:17 AM

Ok. This whole process probably took me at least 5 hours.

I ran the test with both sticks of ram. About half way through errors began to show up - over 400 at the very least. After a couple of passes, I tested both sticks of RAM individually. Neither showed any errors. I then switched the places and tested again individually, but I still got no errors. Finally I retested both together in their original places for over 2 passes, and to my surprise there were no errors. I just finished running the Windows Memory Diagnostic again and my computer did fine.

I don't know if I'm missing something, but I find it a bit odd. Could it be that the people who built my computer installed the RAM incorrectly?

#13 AustrAlien

AustrAlien

    Inquisitor


  • Members
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:01:30 AM

Posted 12 January 2012 - 02:22 AM

I suggest that you leave memtest86+ to run (with both sticks installed) for 24 hours to have a fair degree of confidence in the result.

Edited by AustrAlien, 12 January 2012 - 02:23 AM.

AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#14 hamluis

hamluis

    Moderator


  • Moderator
  • 56,124 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:30 AM

Posted 12 January 2012 - 02:24 PM

FWIW, a suggested guide to running Memtest: Memtest86+ Guide-How To's - Overclockers Forums - http://www.overclockers.com/forums/showthread.php?t=409152

When I've resorted to running it...I ran it with each module in each slot (only had 2 slots), with both modules together, then switched the location of each and ran both modules again. My premise was that it could be a bad RAM slot/board problem.

Louis

#15 worskies

worskies
  • Topic Starter

  • Members
  • 55 posts
  • OFFLINE
  •  
  • Local time:08:30 AM

Posted 12 January 2012 - 05:45 PM

I ran it for 16 hours and had no errors. I turned it off because I am going to be away for a couple of days.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users