Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

PC keeps restarting (BSOD) and sometimes won't boot (Resolved)


  • Please log in to reply

#91
JoeBenyon

JoeBenyon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 153 posts
After reinstalling Windows everything worked fine up until I installed Google Chrome and opened it, Windows froze and I had to reboot.
  • 0

Advertisements


#92
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,025 posts

Try uninstalling Chrome and installing FF from here


  • 0

#93
JoeBenyon

JoeBenyon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 153 posts

When I rebooted chrome was uninstalled gain and I just tried playing a basic windows game (Solitaire) and after a minute or so windows froze up again. Then when waiting to log in I got the clock interrupt BSOD. :(

**Edit** It seems that idling on the desktop works fine now but after doing something after being idle causes a reboot.

 

After a restart I managed to get this error report from windows if it helps:

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional information about the problem:

BCCode: 124

BCP1: 0000000000000000

BCP2: FFFFFA800764E8F8

BCP3: 0000000000000000

BCP4: 0000000000000000

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\121914-37549-01.dmp

C:\Users\Joey\AppData\Local\Temp\WER-47720-0.sysdata.xml


Edited by JoeBenyon, 19 December 2014 - 05:54 PM.

  • 0

#94
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,763 posts

We will need to see the dump file.

Start the computer in safe mode with networking.

Go to C:\Windows\Minidump\121914-37549-01.dmp

Drag it to the desktop.

Zip up the file.

Attach  the zipped file in your next reply. 


  • 0

#95
JoeBenyon

JoeBenyon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 153 posts

Here you go. :)

Attached Files

  • Attached File  dump.zip   10.58KB   23 downloads

  • 0

#96
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,763 posts

I don't have the Debugging tools on my computers, so will get help from another member.

In normal mode, can you run IE without getting crashes?


  • 0

#97
JoeBenyon

JoeBenyon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 153 posts
Okay :)
No I can't, it froze once whilst trying to send an email with just IE open.
  • 0

#98
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,763 posts

What about Safe Mode with Networking, does IE crash?


  • 0

#99
JoeBenyon

JoeBenyon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 153 posts

Nope, everything works fine in Safe Mode with Networking.


  • 0

#100
phillpower2

phillpower2

    Tech Staff

  • Technician
  • 20,025 posts
The dump again points to the CPU having issues and such damage is often caused by bad OCing, note what I have highlighted below and for suggested remedial steps see here courtesy of H2SO4 on the Windows Seven Forums.
 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`01c11000 PsLoadedModuleList = 0xfffff800`01e56e90
Debug session time: Fri Dec 19 18:49:42.243 2014 (UTC - 5:00)
System Uptime: 0 days 0:00:24.743
*******************************************************************************
*                                                                             *
*                        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: fffffa800764e8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
 
Debugging Details:
------------------
 
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
 
BUGCHECK_STR:  0x124_AuthenticAMD
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
STACK_TEXT:  
fffff880`0218d5b0 fffff800`01ed4d29 : fffffa80`0764e8d0 fffffa80`06727b60 00000000`0000000d 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0218dad0 fffff800`01db4217 : fffffa80`0764e8d0 fffff800`01e2e658 fffffa80`06727b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0218db00 fffff800`01d1b865 : fffff800`01e903a0 00000000`00000001 fffffa80`076b9820 fffffa80`06727b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0218db40 fffff800`01c9ba21 : fffff880`010ade00 fffff800`01d1b840 fffffa80`06727b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0218db70 fffff800`01f2ecce : 00000000`00000000 fffffa80`06727b60 00000000`00000080 fffffa80`0671b740 : nt!ExpWorkerThread+0x111
fffff880`0218dc00 fffff800`01c82fe6 : fffff880`020a5180 fffffa80`06727b60 fffff880`020b00c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0218dc40 00000000`00000000 : fffff880`0218e000 fffff880`02188000 fffff880`0218ca90 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: AuthenticAMD
 
IMAGE_NAME:  AuthenticAMD
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
 
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
 
Followup: MachineOwner
---------

  • 0

Advertisements


#101
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,763 posts

Thanks Phillpower2 for the interposition and the troubleshooting link.


  • 0

#102
JoeBenyon

JoeBenyon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 153 posts
Should I RMA my CPU and see if that fixes the problem?
  • 0

#103
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,763 posts

Yes, IF, a fail after performing step 7, given that you have tried extensive hardware test. 

"7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc. Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause." 


  • 0

#104
JoeBenyon

JoeBenyon

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 153 posts
Okay I will have to do it in a few days. Merry Christmas :)
  • 0

#105
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 6,763 posts

OK.   Thanks and seasons greeting to you and your family. 


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP