64-bit troubles. Need help!

[Brian A.]

Hey everyone. I just subscribed to these forums because I was hoping to get some advice about what to do. My tech knowledge is pretty limited, so I will try to explain the problems to the best of my ability.

I'm running Vista Home Premium x64. At least 4-5 times a day my computer completely freezes up and will remain that way until I manually restart it. I've looked at the problem reports and solutions and there seems to be 2 main problems. Most of the errors are under the group called "windows." the Problem event name states there was a blue screen error. I've heard of the blue screen error, but I thought it was odd that my screen didn't actually turn blue. The other problems are under the group "windows explorer." The error name there is "AppHangB1." I have no idea what that means. Any help would be much appreciated! thank you.

 

[roy69]

Hi Brian, how old is your computer and did you buy it from a shop?

List your system specs.

Does your computer hang in safe mode?

Have you got service pack 1 installed?

AppHang error is where an application will hang, mainly due to memory errors.

Check out your cooling and run a memory test.

You can also look in your performance and reliability logs as well as the error logs you have looked in.

The peroformance logs are a good thing to look at because it gives you a chart showing how reliable your computer is on a day to day basis.

You need to supply more info from your error logs to help more.

 

[Brian A.]

My computer is less than a week old. I didn't build it myself. I ordered it online. My specs are:

Core 2 Extreme 9650 @ 3GHz
EVGA nForce 780i mainboard
2 x 2GB Corsair Dominator PC2 8500 @ 800 MHz
EVGA GeForce 9800 GX2 with latest drivers
CoolerMaster Cosmos S Case
CoolerMaster 1,000 watt PSU

It does not hang in safe mode and I got it with SP1 already installed. Below are a few details about my errors.

Problem
Shut down unexpectedly

Date
5/18/2008 9:02 PM

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Extra information about the problem
BCCode: 50
BCP1: FFFFFA6006F8A000
BCP2: 0000000000000001
BCP3: FFFFFA6002652D7A
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Product
Windows Explorer

Problem
Stopped responding and was closed

 

[Brian A.]

I made one small error on my last post. My current system memory is 2 gigs of Corsair PC6400 DDR2 @ 800 MHz. The memory I listed in my specs aboue is the memory i ordered from newegg yesterday. I will be installing that memory when it gets here tomorrow.

 

[dmex]

Hi, I have looked up your BlueScreen crash code...

Bug Check 0x50

The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.

If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

Cause

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system driver service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Steven

 

[Brian A.]

Thank you very much! That gives me a good starting point. I was clueless before. There were a few other problems on the list. If anyone can make sense of them your help would be much appreciated.

Problem
Video hardware error

Date
5/19/2008 3:19 AM

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6001.2.1.0.768.3

Extra information about the problem
BCCode: 117
BCP1: FFFFFA80024D54E0
BCP2: FFFFFA6002612D80
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

 

[Brian A.]

This is the other one

Product
Windows Explorer

Problem
Stopped responding and was closed

Date
5/19/2008 12:55 AM

Problem signature
Problem Event Name: AppHangB1
Application Name: Explorer.EXE
Application Version: 6.0.6001.18000
OS Version: 6.0.6001.2.1.0.768.3

 

[dmex]

Bug Check 0x117: VIDEO_TDR_TIMEOUT_DETECTED

The VIDEO_TDR_TIMEOUT_DETECTED bug check has a value of 0x00000117. This indicates that the display driver failed to respond in a timely fashion.
Parameters

The following parameters are displayed.
Parameter Description
1 The pointer to the internal TDR recovery context, if available.
2 A pointer into the responsible device driver module (for example, the owner tag).
3 The secondary driver-specific bucketing key.
4 Reserved.


Post some screenshots of both CPUID and GPU-Z Video card GPU Information Utility and we can get a good idea about the last two...

Steven

 

[Brian A.]

I have all the pictures. Thanks a lot for taking the time to help me.

 

[roy69]

If your computer is less than a week old, contact the manufacturer. It is thier responability to correct the error or give you a working unit.

You may be able to fix it yourself but this may invalidate the warrantee.