Windows 10: Error STOP

I am Latin, my name Abel Moreno, I do not speak English well. I have blue screen error. The error appears in any version of Windows. I have already tried version 7, 8, 8.1, 10 and 10 for workstation. I enclose the "minidump" files. In addition, I write the error messages that the "WinDbg Preview" program shows me. I have a system operative: Windows 10 for workstation.



Links to files: http://www.mediafire.com/file/hcqjskaoffww0nb/minidump-abelmoreno.rar/file

http://www.mediafire.com/file/hcqjskaoffww0nb/minidump-abelmoreno.rar/

[082418-26546-01.dmp]

Microsoft (R) Windows Debugger Version 10.0.18206.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\2\Desktop\082418-26546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`8fa02000 PsLoadedModuleList = 0xfffff801`8fdb0170
Debug session time: Fri Aug 24 08:45:36.773 2018 (UTC - 3:00)
System Uptime: 0 days 0:31:20.617
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffff85089dc87d00, 2, 0, fffff8018fa4e9e9}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+349 )

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

nt!KeBugCheckEx:
fffff801`8fbaaca0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb70f`31d39dc0=000000000000000a

[082418-28031-01.dmp]


Microsoft (R) Windows Debugger Version 10.0.18206.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\2\Desktop\082418-28031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`ee202000 PsLoadedModuleList = 0xfffff802`ee5b0170
Debug session time: Fri Aug 24 08:13:50.537 2018 (UTC - 3:00)
System Uptime: 0 days 13:29:19.379
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {ffffd4801557b808, 8a00000004200021, ffffab003941af00, a}

Probably caused by : memory_corruption ( nt!MiRaisedIrqlFault+e5a55 )

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

nt!KeBugCheckEx:
fffff802`ee3aaca0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffab00`3941ad50=00000000000000be


Thanks!!!

:)

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.

 

win 10 pro 64 stop code 0x0000007b 0xffffffffc0000034


The STOP 0x0000007B errors are caused by device driver problems, viruses, data corruption, and sometimes even hardware failures. You have tried update your drivers. If the problem still persist, try the steps:

• Run chkdsk on your hard drive. ...
• Perform an extensive test of your hard drive. ...
• Run the fixmbr command to create a new master boot record. ...
• Clear the CMOS. ...
• Update your BIOS. ...
• Update the hard drive controller's firmware if possible. ...
• Repair your Windows installation. ...
• Perform basic STOP error troubleshooting.

 

atioglxx.dll OpenGL Error !

*** errors in the installer !!!

* manuel make *

_____________________
1.step :

AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

Catalyst 9.9 Hotfix for Windows XP Professional and Home Edition

ati.com/drivers/hotfix/9-9_agp-hotfix_xp32_dd_ccc.exe

_____________________
2.step :

( install *Smile )

C:\ATI\Support\9-9_agp-hotfix_xp32_dd_ccc

_____________________
3.step :

C:\ATI\Support\9-9_agp-hotfix_xp32_dd_ccc\Driver\XP_INF\B_86849\atioglxx.dl_

( X:\....\9-9_agp-hotfix_xp32_dd_ccc\Driver\XP_INF\B_ ,,,, \atioglxx.dl_ )

_____________________
4.step :

( ReName *Smile )

atioglxx.dl_ -> atioglxx.dll

_____________________
5.step :

( Move *Smile )

atioglxx.dll -> C:\WINDOWS\system32

_____________________
6.step :

restart PC ! OK *Smile

ATi OpenGL (atioglxx.dll) No-Errors ! *Big Grin