Brand new computer running Windows 8 - 2 crashes in first day

Hi everyone,

Any assistance with this problem would be much appreciated :)

I bought a new computer yesterday, running Windows 8. I use the computer primarily for photo editing so this morning I installed my copy of Photoshop CS4 on the computer and needed to install an ACR update, which I downloaded from Adobe.

The first of the crashes occurred as I was trying to download the update (Camera Raw 5.7). This is the .dmp file from that crash - https://skydrive.live.com/redir?resid=B50D32B2D4102B3F!187&authkey=!AHogu8RLIx59Nt4&ithint=file%2c.dmp

After restarting, I completed the download of the update, installed it and made sure that Photoshop was running correctly, which it was.

The second crash occurred this evening (Photoshop not running, no downloads in progress etc.) This is the .dmp file from that crash - https://skydrive.live.com/redir?resid=B50D32B2D4102B3F!188&authkey=!AJ97jn-_skkL03Y&ithint=file%2c.dmp

Obviously, since this is a brand new computer, I wouldn't expect it to be crashing at this rate. I'm assuming that either the Photoshop installation or the ACR update has caused some problems (though nothing I have read has suggested that it should).

Can anyone cast any light on this? Many thanks in advance!


 

Question Info


Last updated March 24, 2018 Views 379 Applies to:
Answer
Hi,

You are going through the same exact thing a user is dealing with here - http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/windows-8-crashes-after-entering-sleep-mode/b140bccd-29ae-414b-840c-ed5269c26ea0

The attached DMP files are of the ACPI_BIOS_ERROR (a5) bug check.

This bug check indicates that the Advanced Configuration and Power Interface (ACPI) BIOS of the computer is not fully compliant with the ACPI specification.

BugCheck A5, {1000, 0, 80001000, 25}

1000 = ACPI_BIOS_USING_OS_MEMORY.

ACPI had a fatal error when processing a memory operation region. The memory operation region tried to map memory that has been allocated for OS usage.

This bug check appears generally in these 2 scenarios:

1. BIOS bug / corrupt and needs to be solved with an update or return to manufacturer.

2. Rootkit (not very common).

Given you have the exact same problem + the same model of HP, etc... this is a big problem on HP's part. Contact them and let them know you'd like a replacement ASAP, preferably if possible of a working model.

Regards,

Patrick
Debugger/Reverse Engineer.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.