Windows 7: My Win7 Freezes

Jesse27 · 31 Dec 2009

My Windows 7 freezes everytime it starts up. After logging in, a few minutes it would hang up, all i would do is press the restart button.

Here is the log that may be useful.

Code:

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          12/31/2009 7:32:56 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      2CPRESLER
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x00000000, 0x8507a594, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\Minidump\123109-18406-02.dmp. Report Id: 123109-18406-02.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-12-31T11:32:56.000000000Z" />
    <EventRecordID>20527</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>2CPRESLER</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x00000124 (0x00000000, 0x8507a594, 0x00000000, 0x00000000)</Data>
    <Data Name="param2">C:\Windows\Minidump\123109-18406-02.dmp</Data>
    <Data Name="param3">123109-18406-02</Data>
  </EventData>
</Event>

zigzag3143 · 31 Dec 2009

Quote: Originally Posted by Jesse27

My Windows 7 freezes everytime it starts up. After logging in, a few minutes it would hang up, all i would do is press the restart button.

Here is the log that may be useful.

Code:

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          12/31/2009 7:32:56 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      2CPRESLER
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x00000000, 0x8507a594, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\Minidump\123109-18406-02.dmp. Report Id: 123109-18406-02.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-12-31T11:32:56.000000000Z" />
    <EventRecordID>20527</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>2CPRESLER</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x00000124 (0x00000000, 0x8507a594, 0x00000000, 0x00000000)</Data>
    <Data Name="param2">C:\Windows\Minidump\123109-18406-02.dmp</Data>
    <Data Name="param3">123109-18406-02</Data>
  </EventData>
</Event>

Hi and welcome

We really need the dmp file. but from the bug check it looks a hardware issue

upload the dmp and we can look at it for you

Ken J+

Jesse27 · 31 Dec 2009

Attached is the dump file said in the error log.

Jesse27 · 31 Dec 2009

Sorry for Bumping. Anyone?

zigzag3143 · 31 Dec 2009

Quote: Originally Posted by Jesse27

Sorry for Bumping. Anyone?

Hi jessi and welcome

this one was caused by hardware. bugcheck124 can be caused by Hardware, Incompatibility, May be driver corruption

Since your drivers all appear up to date I would

download memtestx86 and run it for 3 or 4 passes
run a system file check
type cmd in search>right click and run as admin>sfc /scannow

IF YOU ARE OVERCLOCKING STOP

Hope this helps

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\123109-18406-02.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
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82850000 PsLoadedModuleList = 0x8298f570
Debug session time: Thu Dec 31 06:32:45.656 2009 (GMT-5)
System Uptime: 0 days 0:00:09.546
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, 8507a594, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

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: 8507a594, 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:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
80e0ecc4 829131c5 8507a578 829adf88 829adf80 nt!WheapCreateTriageDumpFromPreviousSession+0x32
80e0ece4 82913fe1 829adf80 8507a578 829adfb0 nt!WheapProcessWorkQueueItem+0x56
80e0ed00 828ab043 829adf80 00000000 842c3798 nt!WheapWorkQueueWorkerRoutine+0x1f
80e0ed50 82a37d16 00000001 a9f8d5d3 00000000 nt!ExpWorkerThread+0x10d
80e0ed90 828d9159 828aaf36 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_MAE_PRV

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_PRV

Followup: MachineOwner
---------

Jesse27 · 10 Jan 2010

I purchased a new Power Supply Unit with higher Watts and that fixed the problem.
Thanks for the help guys.

djpaulc · 29 Sep 2010

Hi Jesse

I am having a similar problem with freezes on startup. Just wondered what was your old power supply units wattage and your new one too? I am running a 650w one now, thinking maybe its not enough.

CarlTR6 · 29 Sep 2010

Quote: Originally Posted by Jesse27

I purchased a new Power Supply Unit with higher Watts and that fixed the problem.
Thanks for the help guys.

Glad you solved the problem and thanks for reporting back with the solution.

gr00vechamp · 15 May 2012

I can confirm with 100% certainty that this is a power supply failure. I am running Windows 7 32bit with a Pentium 4 3.0 GHz processor and 2GB of RAM on an older ASUS P4C800-E mother board. I am also running a SATA mirror. The power supply that failed was an ATX Switching 400W.
For a little over a month my computer would crash and restart itself (No BSOD). I thought it acted and sounded like when a transformer blows in my neighborhood and I would hear a snap from my computer before it shut down. So to me this pointed to a power supply issue as I would hear the same snap when my computer shutdown while I still had electricity.
So I ordered a new 600W ATX Switching power supply and it arrived today. As I walked into the room where my computer is I had every intention of shutting down the computer to start the power supply replacement process when I hear the familiar "SNAP' and the computer shutdown. Only this time it did not restart itself and my efforts to turn it on with the power switch were futile. I worried that the M/B had failed. As I removed the old 400W power supply I noticed the back of it (side facing the M/B inside the case) was encrusted with dust and even the internal parts of the power supply were completely encased in dust. This is because I was to lazy to put the cover back on my computer case and let it run that way for a couple of months.
I am happy to say that after installing the new 600W power supply the computer booted right up after I went into the BIOS and updated the system time settings. I got the new power supply off of Ebay from UnionPros for $24.00 shipped.

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_PRV

Followup: MachineOwner

Windows 7: My Win7 Freezes

My Win7 Freezes problems?