Playing Mass Effect Andromeda, BSOD, hal.dll (0xFFFFF8027EA2E627)

Hi,

I had BSOD when playing MEA and that was first one in that game. Had one crash, but game just shut down and i was back in desktop. I have looked EA forums and i´m not only one who has problems with that game.
My PC have had no problems before and everything has worked fine.

Just want to make sure that it´s not my PC which has problems.
Log in attachments.

Thank you.


On Sun 26.3.2017 6.10.54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032617-3390-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8027EA2E627)
Bugcheck code: 0xA (0xB0, 0xFF, 0x0, 0xFFFFF8027EA2E627)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 26.3.2017 6.10.54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalProcessorIdle+0x2C7)
Bugcheck code: 0xA (0xB0, 0xFF, 0x0, 0xFFFFF8027EA2E627)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Hey and Welcome JBL74 (it might be weird my welcoming you to the site since this is my first post Lol).

First of I'm a rookie BSOD analyst, I just started this week and I'm sure that some of the more senior analysts will stop by and be able to help you better than me. I'm not able to find any usefull information from the .dmp file. So I would suggest running Driver Verifier in order to generate a BSOD that might give us some more information on what's causing the issue.

Enable and Disable Driver Verifier in Windows 10

I´m now in BSOD bootloop. Allready tried to disable verifier with bootdisc command prompt and from startup settings, but it´s not working. Don´t know how can i disable it. Or it´s disabled and Windows is messed up somehow.

Okey so the system got a BSOD running driver verifier and now you are stuck in a boot loop and you are not able to disable verifier by entering the command into the command prompt or through the startup settings.
Did you create a restore point prior to activating driver verifier? If so can you try to restore the system?

You can also try to enter safe mode and try to disable it from there.

Safe mode and command prompt didnt work either. I have to try install windows again and see if that helps.