Random BSOD/Freezing

[Ray89]

Good evening! My PC is having some strange and random problems. Sometimes, it gets BSOD, sometimes it just freezes. Usually, i am just using the web or playing an emulator.

At first, i thought it was some issue with my VGA (Nvidia xfx GTS 250) so i just took it off but the problem persisted. I also formatted the PC but it didn't help too....

My specs:
- Windows 7 Professional x86
- the original installed OS on the system? - Yes
- an OEM or full retail version? - Full Retail
- What is the age of system (hardware)? - 2 years
- What is the age of OS installation (have you re-installed the OS?) - 1 month

Thanks!

 

[writhziden]

Problem Devices:

Device is not present, not working properly, or does not have all of its drivers installed.
A device has a configuration problem that prevents it from working properly.
The device, MpKsl7f09df6d, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_MPKSL7F09DF6D\0000.
1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.
Explanation of Error Codes Generated by Device Manager
Manage Devices in Windows

Device is not present, not working properly, or does not have all of its drivers installed.
A device has a configuration problem that prevents it from working properly.
The device, MpKsl9cc05bde, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_MPKSL9CC05BDE\0000.
1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.
Explanation of Error Codes Generated by Device Manager
Manage Devices in Windows

Security Software (this is just to check that the software is installed and working properly; nothing needs to be done with this information at this time):

MSC	"c:\Program Files\Microsoft Security Client\msseces.exe" -hide -runkey

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Ray89\Windows_NT6_BSOD_jcgriff2\041412-24180-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82c03000 PsLoadedModuleList = 0x82d4c4d0
Debug session time: Sat Apr 14 09:48:30.716 2012 (UTC - 6:00)
System Uptime: 0 days 0:41:07.354
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
........
0: 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: 00000000, Machine Check Exception
Arg2: 8619b01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: f635c000, High order 32-bits of the MCi_STATUS value.
Arg4: 2a000128, 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:  dwm.exe

CURRENT_IRQL:  1f

STACK_TEXT:  
82d27d2c 83023fcd 00000124 00000000 8619b01c nt!KeBugCheckEx+0x1e
82d27d68 82cd4aac 8603d679 8619b01c 82c7b2d0 hal!HalBugCheckSystem+0xab
82d27d98 8302427f 8619c780 83031e40 00000000 nt!WheaReportHwError+0x230
82d27eac 83024371 8619c780 8619c7d0 00000000 hal!HalpMcaReportError+0x3b
82d27ed0 830245dd 00000000 8619c7d0 82d27ff0 hal!HalpMceHandler+0x8b
82d27ee0 8301a5f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
82d27ff0 83017261 00000000 801df000 00000000 hal!HalpMcaExceptionHandler+0x87
82d27ff0 00000000 00000000 801df000 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
---------

For the above crash, see http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following to supplement the steps in that link.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

It also appears you have NVIDIA and ATI software installed for graphics. This could be causing conflicts.

nvoclock	99fa1000	99fa8400	Tue Sep 04 20:26:31 2007 (46de13d7)	00009e7e		nvoclock.sys
atikmdag	8e815000	8ec69000	Fri Apr 24 04:50:20 2009 (49f1996c)	00402d61		atikmdag.sys

It also does not help that the drivers are out of date. This may provide double chances of conflict.


Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.