|17 Jan 2012||#1|
| || |
BSOD and small PC freezes
Since 2 days ago my PC started freezing every 2 secs for about 3 mins, then ran normally for about 5mins then started freezing again. Today i got two bsods that you can see in the files. Last BSOD occurred right after i tried to change the windows theme from aero to basic.
I havent updated any software or any hardware in the last week so i have no idea why this is happening.
I have this windows installed for about 3 months.
|My System Specs|
|17 Jan 2012||#2|
| || |
> These crashes were caused by memory corruption (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Using Driver Verifier to identify issues with Windows drivers for advanced users
> > Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ
when you're done you can use this Freeware:
MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place
Using MagicISO to create ISO image files
> > > It appears you need to install SP1.
Please run the update readiness tool and then update to SP-1
Ensure you install the correct 64 or 32 bit option for your system)
Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)
|My System Specs|
|17 Jan 2012||#3|
| || |
Is your system overclocked at all? If so you should remove it now and see if the problem resolves.
Otherwise you've got a pretty nasty set of results in the debugger.
I'll just reference you to this.
Stop 0x124 - what it means and what to try
Probably caused by : hardware Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * 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: 0000000000000000, Machine Check Exception Arg2: fffffa80094c8038, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000b4342000, High order 32-bits of the MCi_STATUS value. Arg4: 000000007d000145, 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: audiodg.exe CURRENT_IRQL: f STACK_TEXT: fffff880`009f0a08 fffff800`033ef903 : 00000000`00000124 00000000`00000000 fffffa80`094c8038 00000000`b4342000 : nt!KeBugCheckEx fffff880`009f0a10 fffff800`02f87293 : 00000000`00000001 fffffa80`094ca620 00000000`00000000 fffffa80`094ca670 : hal!HalBugCheckSystem+0x1e3 fffff880`009f0a50 fffff800`033ef5c8 : 00000000`00000728 fffffa80`094ca620 fffff880`009f0db0 00000000`00000000 : nt!WheaReportHwError+0x263 fffff880`009f0ab0 fffff800`033eef1a : fffffa80`094ca620 fffff880`009f0db0 fffffa80`094ca620 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`009f0c00 fffff800`033e2e8f : 00000000`002a6d10 00000000`00000001 fffff880`009f0e30 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`009f0c40 fffff800`02e6fe6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47 fffff880`009f0c70 fffff800`02e6fcd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`009f0db0 000007fe`f5a971a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 00000000`0242f638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f5a971a0 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE Followup: MachineOwner ---------
|My System Specs|
|18 Jan 2012||#6|
| || |
I removed the overclocked on my cpu,
Checked the memory and no probs
Running driver verifier for 8 hours in normal pc use, so far no problems
installed SP 1
uninstalled daemon tools
So far no more BSODS or lock-ups, hope it stay this way... ill claim it solved if no problems arise until tomorrow.
|My System Specs|
|Similar help and support threads for2: BSOD and small PC freezes|
|BSOD BSOD Driver irql-not-less-or-equal/freezes with immediate restart||BSOD Help and Support|
|Random small freezes for a second and blue screens of death||BSOD Help and Support|
|Strange BSOD`s after small overclocking||BSOD Help and Support|
|BSOD after small oc||BSOD Help and Support|
|Small window and small text||General Discussion|
|Odd BSOD after freezes||BSOD Help and Support|
|BSOD and freezes W7 64 bit||BSOD Help and Support|