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

Fixing a friends computer BSOD 0x00000101


  • Please log in to reply

#1
rei158

rei158

    Member

  • Member
  • PipPipPip
  • 136 posts

Hey, a friend of mine gave me a computer to fix. It was fixed once in the summer when its' motherboard was switched. Now it is almost unable to boot itself, often running into loops. The main bsod seems to be
0x00000101 (00000061,00000000,807C2120,00000001)
A clock interrupt was mentioned in the bsod.
Googled a bit and it suggests processor failures.
Specs:
Windows 7 Ultimate SP1 32-bit
Pentium Dual Core E5200 2,5GHz

I ran chkdsk /f and doing sfc /scannow, at the moment no crashes have occurred.

Attached Files


Edited by rei158, 10 November 2015 - 01:43 PM.

  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,338 posts

Always happy to help but to do so we need help from yourself  ;)

 

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom left of the dialogue input box 
 
May I also ask that as a sign of appreciation for our free help that you let us know when you no longer require assistance and not leave the thread hanging, thank you  :)
 

  • 0

#3
rei158

rei158

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 136 posts

I am sorry for that I had left my other thread hanging a lot and closed it now.
As for the minidumps, they should be added in the first post.

I found an additional BSOD:
0x00000124


Edited by rei158, 10 November 2015 - 01:49 PM.

  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,338 posts

Please attach the dump files as detailed in my reply # 2, rar are not used here.


  • 0

#5
rei158

rei158

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 136 posts

My bad. Sorry =)

Attached Files


  • 0

#6
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,338 posts

The last three dumps point towards a problem with the CPU, some info here

 

If the system has or is being overclocked, go into the BIOS and restore the MBs default factory settings and test, please note that overclocking can seriously damage hardware and no amount of remedial steps would be able to put this right.

 

Going offline shortly as I have an early start but will check back asap tomorrow, hopefully another member may step in meanwhile.


  • 0

#7
rei158

rei158

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 136 posts

This computer is mostly used for browsing the net, storing pictures, printing, etc so it has not been overclocked.

While in the BIOS, I only had 2 options: Optimized and Fail-Safe settings, so I tried both:

1) Optimized settings - every boot ended with a crash after loading the Windows logo, once it made it to Desktop but crashed in a moment.

 

2) Fail-Safe settings - boots work half the times so I am able to be on the desktop for some time.

 

Tomorrow I will be back afternoon, about 16:00 or even later in my timezone +02:00.

Good night.


Edited by rei158, 10 November 2015 - 03:43 PM.

  • 0

#8
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,338 posts
Fail-Safe settings - boots work half the times so I am able to be on the desktop for some time.

 

 

The above settings are the correct ones, "optimized" settings are a form of overclocking which as you have found already causes instability.

 

Any more crashes since restoring the "fail safe" settings.

 

Download then run Speccy (free) and post the resultant url for us, details here,  this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s. 

 

JAFYI: Checked another dump from Sunday Nov 1st  which again points toward the CPU, there is an outside chance that the problem is driver related, Speccy may shed some light on if it is.

 

Kernel base = 0x82c48000 PsLoadedModuleList = 0x82d93e30
Debug session time: Sun Nov 1 12:47:56.540 2015 (UTC - 5:00)
System Uptime: 0 days 0:02:48.273
*******************************************************************************
* *
* 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: 8637d024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, 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_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 1f

STACK_TEXT:
82d6ed0c 82c1ffcd 00000124 00000000 8637d024 nt!KeBugCheckEx+0x1e
82d6ed48 82d1a6ec 8637f439 8637d024 82cc0130 hal!HalBugCheckSystem+0xab
82d6ed78 82c2027f 85d32d50 82c2de40 00000000 nt!WheaReportHwError+0x230
82d6ee8c 82c20371 85d32d50 85d32da0 00000002 hal!HalpMcaReportError+0x3b
82d6eeb0 82c2048d 00000000 85d32da0 00000000 hal!HalpMceHandler+0x8b
82d6eed0 82c205d6 00000000 85d32d50 82d6eff0 hal!HalpMceHandlerWithRendezvous+0x4b
82d6eee0 82c165f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
82d6eff0 82c13261 0000001b 801dd000 00000000 hal!HalpMcaExceptionHandler+0x87
82d6eff0 00000000 0000001b 801dd000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS


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


  • 0

#9
rei158

rei158

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 136 posts

Here is the url:

http://speccy.pirifo...zRTsoZkmT5bZFK3


  • 0

#10
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,338 posts
Any more crashes since restoring the "fail safe" settings.

 


  • 0

Advertisements


#11
rei158

rei158

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 136 posts
Yeah,half of the boots crash and it crashes in desktop too but sometimes i'm
able to watch a 20min video
  • 0

#12
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,338 posts

Nothing untoward showing in Speccy so will suggest a couple of things for you to do, quickest one first, download and run IntelBurnTest 2.54 (free) from here to stress test your CPU and Ram, please disregard any other product or service that may be offered at the link.


  • 0

#13
rei158

rei158

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 136 posts

Hey, on both times, when my computer didn't freeze from the test or from it's fault itself, the test failed after 2 minitests.
It said that the processor is unstable.

So does this mean I need to buy a new processor?

EDIT: Updated one of the logs, it was a wrong one.

Attached Files


Edited by rei158, 11 November 2015 - 02:12 PM.

  • 0

#14
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,338 posts

It doesn't look good but it could be the CPU socket** or even the power supply to the socket causing the instability.

 

Are you able to run any of the other tests.

 

Another test you can try is Prime 95, you can get the 32-bit version from the 64-bit link here

 

** MBs are more prone to failure than CPUs and the most common cause of CPU failure is extreme or overclocking gone bad.


  • 0

#15
rei158

rei158

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 136 posts

On the first go, both workers #1 and #2 failed soon enough and encountered hardware errors.

On the second go, worker #2 failed, but but #1 kept working for quite a long time after failing eventually.

 

Included the results file.

Attached Files


  • 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