BSOD 5x per day

[yabahut]

Hi all,

I´ve installed new Win7 Professional 32bit one week ago. First days was OK, but yesterday my OS falls 5x. Please help me with diagnostic and solve this problem. Thanks a milion

Windows 7 Professional 32bit
OEM

HDD WD Caviar black 500 GB - New (bought 1 week ago)
Rest of the HW is 2-3 years old

OS 1 week old installation

 

[Capt.Jack Sparrow]

Hello and Welcome !

Seems like some Hardware is causing the problem. Follow this article make sure you cover all the points. Stop 0x124 - what it means and what to try

sptd.sys is notorious for BSOD follow this article and uninstall it DuplexSecure - FAQ

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger

If your Overclocking please stop and reset everything to default settings. Run SFC /SCANNOW Command - System File Checker


Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
My System SpecsSystem Spec

Drivers to be Updated

AmdLLD.sys   Sat Jun 30 01:17:32 2007
nvmfdx32.sys Tue Jan 16 06:20:38 2007
nvstor32.sys Sat Dec 23 09:37:08 2006

Follow this guide for assistance in updating Drivers Driver Troubleshooting !! « Captain Debugger

Bugcheck:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
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: 8672d024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000181, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  1f
STACK_TEXT:  
807cd8cc 82c20f3f 00000124 00000000 8672d024 nt!KeBugCheckEx+0x1e
807cd908 82d17f04 86728051 8672d024 82cb14d0 hal!HalBugCheckSystem+0xab
807cd938 82c211f1 8672c578 82c2ee40 00000000 nt!WheaReportHwError+0x230
807cda4c 82c212e3 8672c578 8672c5c8 00000000 hal!HalpMcaReportError+0x3b
807cda70 82c2154f 00000000 8672c5c8 807cdb90 hal!HalpMceHandler+0x8b
807cda80 82c175f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
807cdb90 82c14261 00000008 807c8750 00000000 hal!HalpMcaExceptionHandler+0x87
807cdb90 00000000 00000008 807c8750 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
Followup: MachineOwner
---------

Hope this helps,
Captain