Its been a week. Starting last sunday. I was playing video games and listening to music. Then my PC would BSOD and do its file dump. After restarting my PC everything was fine for a few more hours. Then it would BSOD again !!
I've tried restoring to last config. - didnt fix it
I've tried updating my graphics driver. - didnt fix it
I've tried updating windows. - didnt fix it
I've updated my network driver too - didnt fix it..

I dont know what else to dooo. And I dont want to restore my comp. I dont even know if that would fix it.

My specs are:
OS: Vista
Video card: GeForce 8600GT
Processor: AMD Athlon 62x2 Dual Core
HD: 320gb
RAM: 2GB

I have encountered all of the STOP errors :

***STOP: 0x00000007E (000000x5, 0x000000000, 0x828037BC, 0x828034B8)
and
DRIVER IRQL NOT LESS OR EQUAL
STOP: 0x000000D1
and
DRIVER IRQL NOT LESS OR EQUAL
STOP: 0x000000D1
USBPORT.SYS - address 88232EB7 base at 88230000, DateStamp 4549b26d
and
An attempt was made to write to read-only memory.
STOP: 000000BE
afd.sys - Adress 88A496B4base at 88A39000, DateStamp 4549b341



Thanks you, please try and help

Hello.

Read this http://www.pchelpforum.com/xf/threa...se-read-before-posting-in-this-section.27453/

I have a problem with doing that because my computer wont get passed its BSOD, or when it does. A BSOD will happen before I'm able to download

Do you have the capacity to download the file from some other, put it on a flash drive and then quickly turn on your PC just long enough to collect the information?
If yes, download this http://www.mediafire.com/?hoawhb3d7dq48e4 and place it on a USB flash drive.
If the machine still can't last long enough in normal mode, try starting it in safe mode. Simply, after turning the PC on keep tapping the F8 key which should start a menu in which you should see an option labeled "safe mode". Choose that and wait for the machine too boot. If it seems to stall a bit, wait 5-10 minutes.

If doesn't work either, try starting the PC in any mode, go here

Code:

c:\windows\minidump

copy all the files you find in that folder to the desktop, archive them all into one file and attach here. Doing this shouldn't take more then a minute.

Okay !
So I've uploaded a folder with all of the files found on "c:\windows\minidump" of my PC. One thing I have noticed is that the files are from 6/28 when my BSODs have been happening since 6/24. IDK if that would help you or not but I think you should know.

Question, what are the possibilities that a BSOD is caused by a virus? Should I download a free antivirus and scan my PC because my previous antivirus program has expired?

Thank you,
scktz

One of the memory dumps tells us there's a hardware related problem

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 89fb3028, Address of the WHEA_ERROR_RECORD structure.
Arg3: f6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000181, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************

BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Idle

CURRENT_IRQL:  1b

STACK_TEXT:  
874eef84 877a6f1f 00000124 00000000 89fb3028 nt!KeBugCheckEx+0x1e
874eefa0 874cee6a 89fb3028 89fb4008 00000001 hal!HalBugCheckSystem+0x37
874eefc0 877a6ede 89fb4008 89fb4120 874eeff4 nt!WheaReportHwError+0x10c
874eefd0 877a6fff 00000003 89fb4008 00000000 hal!HalpReportMachineCheck+0x28
874eeff4 877a389f 801dc000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3
874eeff4 00000000 801dc000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD__UNKNOWN

BUCKET_ID:  0x124_AuthenticAMD__UNKNOWN

Followup: MachineOwner

There's a number of these, as well

Code:

Mini070112-02.log
Debug session time: Mon Jul  2 00:10:07.493 2012 (UTC + 2:00)
System Uptime: 0 days 0:01:55.287
IRQL_NOT_LESS_OR_EQUAL (a)
Arg1: 00000000, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, bitfield :
Arg4: 874a91ab, address which referenced memory
IMAGE_NAME:  ntkrpamp.exe
PROCESS_NAME:  Idle
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  0xA_nt!KiUnwaitThread+14
874f1b74 874a91ab badb0d00 00000001 87e85fd4 nt!KiTrap0E+0x2ac
874f1bfc 874a9842 00000000 874f4820 874f6180 nt!KiUnwaitThread+0x14
874f1ce8 874a9421 00000000 00000000 00001cde nt!KiTimerExpiration+0x20d
874f1d50 8749147e 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
874f1d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46

which often means a BIOS update would be in order, especially since your current BIOS is rather old. However, since this is a HP product, finding a bios will not be easy, if at all possible.

As for the other dumps, which were probably caused by drivers, the usual suspect is this driver

Code:

45ED2E6E 2007 Mar 06 10:03:42 WG311T13.sys

which belong to your wireless USB adapter. You should look into updating that device or uninstalling it for the time being, to see if that helps alleviate the issues.

For the error caused by my wireless USB adapter. I've updated that driver as well as my graphics..

How do you think I should go by looking for this BIOS update? And do these memory dumps hint to what the hardware failure could be?
All help is appreciated,

-scktz

The problem with the BIOS is that you're using custom made boards for HP computers, those usually don't offer much support. What's the exact product name for your system?

That type of error points to the CPU or the motherboard. You can download these
http://www.alcpu.com/CoreTemp/
http://www.softpedia.com/get/Others/Home-Education/Prime95.shtml
Start both programs, use small fft test on prime95 for a while while monitoring temperatures in coretemp. Lets see if you can recreate that error.

My system name is: HP Pavilion a1744x

and I will get started on that test. What will you want me to look for to relay back to you?

Crashes and/or too high temperatures.

There is a bit newer bios version available http://h10025.www1.hp.com/ewfrf/wc/...dlc=en&lc=en&os=2093&product=3347764&sw_lang=

So I've had Prime95 running with Core Temp monitoring my temp.
Its been running for 6 minutes now. Max temps in both cores are 71-70 w/ 100% Load
No Crashes yet.

EDIT: Been running for 14 minutes, Max temps in Core #0 is 72c, Core #1 is 70c w/ 100% Load
No Crashes yet.

EDIT: Running for 30 minutes, Max temps in Core #0 is 72c, Core #1 is 70c w/ 100% Load
No Crashes yet.

That's a probably too high temperature for this CPU. Do you have any kind of overclocking enabled in BIOS? You should check on the inside of your case for dust buildup, especially on the heatsinks and the ventilators. The best way to clean is to use a can of compressed air or an air compressor on a lower pressure settings, just give it a good blow of air.

I dont know how to check overclocking, but I've already cleaned the inside of my PC the day the crashes started happening.
I'm going to update my BIOS to check if that fixes the problem

Go to BIOS setup and find the option "load setup defaults," save and exit afterwards. You can enter the BIOS setup by tapping F2 or DEL key after turning the PC on.

So I've updated my BIOS and setup my BIOS to defaults.
However I'm still getting BSOD.. What else do you think I can try doing.. Should I uninstall and remove my wireless USB adapter?