[7Ult x64 SP1] WHEA_UNCORRECTABLE_ERROR 0x124 {0, fffffa80`07a678f8, 0, 0}. FIX: I changed the CPU.

Yesterday, I started the system backup, but I took too much time so I had to abort...
I guess there is no "fast" option? Which backup is recommended? I ve never done this before myself. System image or back up? Internal or external drive?
 
Uh?
Usually, you ought to do system backups (full, or all the partitions except data partitions, if you already backup your important files) and save them in an external drive (to avoid it can become corrupt for malware or other things).

If you have got two HDD/SSD, one for the system and one for data, you can temporarily save your (partial) system image (i.e., without data partitions) in the HDD/SSD you use for DATA.
In this case, if you will have issues with the system, you'll only restore your system image, i.e. overwriting system partitions only.

Example:

macrium.png


Tutorial: Using Macrium Free to Backup or Image your drives
 
Meanwhile,

I did a back up (including system image) via control panel > "back up and restore" which took 3 hours...

I also wanted to create a 'system repair disk' but that seems to be a problem > APPCRASH. This same problem is explained in: Recdisc.exe crashing for making system repair disc - Windows 7 Help Forums
However, I don't have Box sync installed..

I also managed to find 3 spare CPU's. This CPU seems to be quite popular among tech.
 

Attachments

  • 1604054863492.png
    1604054863492.png
    132.8 KB · Views: 4
I.e., haven't you got a CD or USB to boot your PC just in case?
Why didn't you try macrium?

I was allready trying in windows..
Yes I ve an USB, but because of the error it is not possible to proceed and select an usb drive.

And then (yesterday) the computer stopped working.. no boot, only black screen.
So I replaced the CPU with one of the spares today. The guy who sold them to me told me to reset the BIOS, which I did and all seems to work until now (fingers crossed!).
I guess it's no longer necessary to do the prompr command? Can we now conclude the CPU was the problem?
 
Ok, thanks. I ll evaluate half november. So hopefully this issue can be closed.
I also intend to check the cpu temperatures regulary. As you can see, the values are fast quit high (only surfing). Should I worry? I've 3 additional fans in my coolermaster (front, back and top):
1604170759996.png

The problem with the system repair disk mentioned above is however not solved. But mayby this does not belong here?
 
Last edited:
It seems the file I saw, i.e. MCUpdate.DLL, is a Windows Media Center (MC) file.


The new dump shows the same as the other ones.

Not to step on any toes, but no, it is not.

MCUpdate.dll is a library from VirusScan Enterprise.
Mcupdate_AuthenticAMD.dll and mcupdate_GenuineIntel.dll are cpu microcode blobs

In true microsoft spirit, there are two entirely different mcupdate.exe's, one for WMC,and the other is the Microcode loader for the above mentioned dlls, but no mcupdate.dll native to windows.
 
Not to step on any toes, but no, it is not.

MCUpdate.dll is a library from VirusScan Enterprise.
Mcupdate_AuthenticAMD.dll and mcupdate_GenuineIntel.dll are cpu microcode blobs

In true microsoft spirit, there are two entirely different mcupdate.exe's, one for WMC,and the other is the Microcode loader for the above mentioned dlls, but no mcupdate.dll native to windows.

Thanks!

You can see my 17th post, where I asked jonesbxl if he used mcafee in the past.
By the way, I searched it (again) and found:
Read More:
From one of jonesbxl's minidumps:
Code:
fffff880`00c9f000 fffff880`00cee000   mcupdate   (deferred)           
    Image path: mcupdate.dll
    Image name: mcupdate.dll
    Browse all global symbols  functions  data
    Timestamp:        Sat Nov 20 14:03:51 2010 (4CE7C737)
    CheckSum:         0004F97E
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


BaseAddress      : 0xfffff88000c9f000
    Name             : mcupdate.dll
    Size             : 0x4f000
As I (and we) can see a different date of mcupdate.dll, I made another search:
Read More:
You can see they've got, almost all, the same date.
Therefore, mcupdate.dll was also a microsoft dll available on "media center" machines.
Then, it was expanded to either Mcupdate_AuthenticAMD.dll or mcupdate_GenuineIntel.dll, when it was necessary.
 
Hello everyone, even though I marked this as solved (no more BSOD's after I replaced the CPU), the PC still "freezes" from time to time, which is annoying. I ve no idea why, since there is no message. Is there a way to find the source(s)? The freezing always happen when surfing the internet.
 
Which browser are you using? Does the entire system remain unresponsive or your web browser?
 
  • In the command prompt (admin), type (copy/paste)
    Code:
    cleanmgr /sageset:1
    A cleanmgr window will be presented, in which you can choose the items to be deleted.
    I'd select them all, but you can choose to avoid some options.
    To start the cleanup, you need to launch this other command:
    Code:
    cleanmgr /sagerun:1
    And the cleanup will start: wait until it finishes.
  • Download and install iobit driver booster free.
    Open it, click tools, click "Clean unplugged device data", scan, clean, close.
  • In the command prompt (admin), type (copy/paste)
    Code:
    pnputil -e > "%userprofile%\desktop\pnputil-enumeration.txt"
  • In the command prompt (admin), type (copy/paste)
    Code:
    dism /online /get-drivers /format:table > "%userprofile%\desktop\dism-getdrivers.txt"
  • Download regseeker, unzip it, click regseeker.exe.
    Click applications and startup.
    Click services, click the information header to sort the items, enlarge the headers so we can see the items, take a (png/jpg) screenshot and save it on your desktop.
    Click drivers, click the information header to sort the items, enlarge the headers so we can see the items, take a (png/jpg) screenshot and save it on your desktop.
  • Download nirsoft shellexview, unzip it, click shexview.exe, take a screenshot and save it on your desktop.
  • Zip up screenshots, pnputil and dism logs.
  • Take fresh logs from your system (bsodcollectionapp)
  • Send those two files here (i.e., new logs and bsodcollectionapp files)
 

Attachments

The old logs displayed drive problems.

Please run the sysnative log collector > post new log files
SysnativeBSODCollectionApp | Sysnative Forums



1) Open administrative command prompt (ACP) and type or copy and paste:
2) sfc /scannow
3) wmic recoveros set autoreboot = false
4) wmic recoveros set DebugInfoType = 2
5) wmic recoveros get autoreboot
6) wmic recoveros get DebugInfoType
7) bcdedit /enum {badmemory}

8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


9) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


10) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows | Seagate
How to use SeaTools for Windows | Seagate Support US
SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums



11) Open administrative command prompt and type or copy and paste:
chkdsk /b /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


Disk Check - Windows 7 Help Forums


12) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10
Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums




19) These steps / tests can be performed overnight:
a) HD Tune full error scan
b) Sea Tools for Windows long generic test
c) Chkdsk /b /v




Code:
Event[3401]:
  Log Name: System
  Source: Ntfs
  Date: 2020-09-23T20:00:24.313
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Event[3402]:
  Log Name: System
  Source: Ntfs
  Date: 2020-09-23T20:00:24.313
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Event[3403]:
  Log Name: System
  Source: Ntfs
  Date: 2020-09-23T20:00:24.313
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Event[3404]:
  Log Name: System
  Source: Ntfs
  Date: 2020-09-23T20:00:24.313
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Event[3405]:
  Log Name: System
  Source: Ntfs
  Date: 2020-09-23T20:00:24.313
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.


Code:
Event[33717]:
  Log Name: System
  Source: Disk
  Date: 2020-03-29T11:36:37.717
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The driver detected a controller error on \Device\Harddisk3\DR3.

Event[33718]:
  Log Name: System
  Source: Disk
  Date: 2020-03-29T11:36:37.217
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The driver detected a controller error on \Device\Harddisk3\DR3.

Event[33719]:
  Log Name: System
  Source: Disk
  Date: 2020-03-29T11:36:36.717
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The driver detected a controller error on \Device\Harddisk3\DR3.

Event[33720]:
  Log Name: System
  Source: Disk
  Date: 2020-03-29T11:36:36.217
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Jonas-PC
  Description:
The driver detected a controller error on \Device\Harddisk3\DR3.


Code:
Windows has made corrections to the file system.


Code:
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
Free Space: 307.6 GB
Total Space: 476.8 GB
File System: NTFS
      Model: WDC WD5000AAKS-00UU3A0 ATA Device

      Drive: D:
Free Space: 340.6 GB
Total Space: 476.9 GB
File System: NTFS
      Model: TOSHIBA DT01ACA050 ATA Device

      Drive: E:
      Model: HL-DT-ST DVD-RAM GH22LP20 ATA Device
     Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7601.17514 (Dutch), , 0 bytes
 
@zbook is it necessary to run all those commands? If the logs state that Windows has made corrections to the filesystem, then chkdsk will probably not achieve much at all.
 
@zbook is it necessary to run all those commands? If the logs state that Windows has made corrections to the filesystem, then chkdsk will probably not achieve much at all.


There were recurrent chkdsk problems.

The tests can be run overnight to rule in / rule out recurrent problems.

And the second drive can be tested.
 
Back
Top