I have a new Lenovo G550 laptop.The machine shuts off about one minute after boot.I realised that once I disable the power service ,there is no power failure and the machine runs smoothly.However ,the power service is required to be running in order for the audio to be functional .The machine stays up well in Safe mode ,no problems.
I've attached the dmp file .Please if anyone has any ideas ,I will be very grateful.
Hello and welcome to the site.
You are getting 0x124 stop errors. Here's the best methods to troubleshoot/repair:
https://www.sevenforums.com/crash-loc...-what-try.html
I'd check the battery to make sure it isn't too old and working incorrectly nowadays.
Hi and welcome
This crash was probably caused by hardware. There isnt enough info to reliably say what hardware
I would
download memtestx86 and run for several hours at least. That will identify ram issues, and heat issues.
Run the system file check to verify and repair your system files
type cmd in search>right click and run as admin>SFC/SCANNOW
If you are overclocking stop
if you have a raid update its driver
As usual if you get more crashes upload them
Ken J+
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\120909-14804-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x81e10000 PsLoadedModuleList = 0x81f58810 Debug session time: Wed Dec 9 15:16:42.166 2009 (GMT-5) System Uptime: 0 days 0:00:04.666 Loading Kernel Symbols ........................................... Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, 85b9d6ac, 0, 0} 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: 00000000, Machine Check Exception Arg2: 85b9d6ac, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000, High order 32-bits of the MCi_STATUS value. Arg4: 00000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: 8b20fcc4 81edefc5 85b9d690 81f77c28 81f77c20 nt!WheapCreateTriageDumpFromPreviousSession+0x32 8b20fce4 81edfdef 81f77c20 85b9d690 81f77c50 nt!WheapProcessWorkQueueItem+0x56 8b20fd00 81e7df2b 81f77c20 00000000 843b54c0 nt!WheapWorkQueueWorkerRoutine+0x1f 8b20fd50 8201e66d 00000001 acf28ab9 00000000 nt!ExpWorkerThread+0x10d 8b20fd90 81ed00d9 81e7de1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_PRV Followup: MachineOwner ---------
There is a way to edit the registry so that the audio services do not rely on other services and can start without them. I used to do this for a different reason but I forget the exact registry keys to edit. You can Google it if interested. But I'd concentrate on updating all the drivers first, as H2SO4 and Ken say.
Quote