Windows 7 BSOD - HAL

mrochester · 11 Apr 2012 at 19:13

Hi all

My parent's PC has started to BSOD fairly frequently (maybe once a day) and in the system event log there's an error about when this happens, and I've no idea what it really means.

HAL - The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system.

I've tried reseating all the RAM. I've very recently cloned their existing 64GB SSD to a 256GB SSD and installed this in its place. Could this be the issue? The BIOS is the most up to date available, and there have been zero issues with the system until this point anyway. Maybe a reinstallation of Windows is on the cards?

Any thoughts greatly appreciated.

Thanks

M.

Destination · 11 Apr 2012 at 19:30

Did you align the new drive with the cloning process?
A win 7 install will align itself correctly, but cloning can mess up the process.

mrochester · 11 Apr 2012 at 19:32

Hikari Kisugi said:
Did you align the new drive with the cloning process?
A win 7 install will align itself correctly, but cloning can mess up the process.

No, I just cloned the drive using Casper 6, and swapped the disks over!

Philtor · 12 Apr 2012 at 00:34

I would be doing a clean install at this stage.

mrochester · 18 Apr 2012 at 17:35

Thanks all for the replies. I have done a clean install, and sadly I am no further forward with this

The computer is still BSODing and I'm still getting HAL - The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system - errors in the even viewer.

I'm also seeing a LOT of atapi errors stating 'The driver detected a controller error on \Device\Ide\IdePort2.'

And another one called BugCheck that says 'The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa80033acb30, 0xfffffa80033ace10, 0xfffff80002d87660). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041812-10233-01.'

Has anyone got any idea what could be going on here?

Many thanks

M

oli356 · 18 Apr 2012 at 17:43

Upload the dump files somewhere

mrochester · 18 Apr 2012 at 18:59

oli356 said:
Upload the dump files somewhere

I'll try but it's more than 300mb so it'll take quite a while!

oli356 · 18 Apr 2012 at 19:10

mrochester said:
I'll try but it's more than 300mb so it'll take quite a while!

Meant to say the ones in
C:\Windows\Minidump

mrochester · 18 Apr 2012 at 19:16

oli356 said:
Meant to say the ones in
C:\Windows\Minidump

There's just one, and here it is!

I had to grant myself permission to upload this...

http://dl.dropbox.com/u/5667504/041812-10233-01.dmp

oli356 · 18 Apr 2012 at 19:32

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80033acb30, fffffa80033ace10, fffff80002d87660}

Probably caused by : csrss.exe

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80033acb30, Terminating object
Arg3: fffffa80033ace10, Process image file name
Arg4: fffff80002d87660, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa80033acb30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`030cf0e8 fffff800`02e0e772 : 00000000`000000f4 00000000`00000003 fffffa80`033acb30 fffffa80`033ace10 : nt!KeBugCheckEx
fffff880`030cf0f0 fffff800`02dbbf7b : ffffffff`ffffffff fffffa80`0440f600 fffffa80`033acb30 fffffa80`033acb30 : nt!PspCatchCriticalBreak+0x92
fffff880`030cf130 fffff800`02d3b0f4 : ffffffff`ffffffff 00000000`00000001 fffffa80`033acb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`030cf180 fffff800`02a83f13 : fffffa80`033acb30 fffff800`c0000005 fffffa80`0440f600 00000000`00a809e0 : nt!NtTerminateProcess+0xf4
fffff880`030cf200 fffff800`02a804d0 : fffff800`02acf9df fffff880`030cfb78 fffff880`030cf8d0 fffff880`030cfc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`030cf398 fffff800`02acf9df : fffff880`030cfb78 fffff880`030cf8d0 fffff880`030cfc20 00000000`76f99c12 : nt!KiServiceLinkage
fffff880`030cf3a0 fffff800`02a84302 : fffff880`030cfb78 00000000`00000000 fffff880`030cfc20 00000000`00a810e8 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`030cfa40 fffff800`02a82e7a : 00000000`00000001 00000000`00a80f98 00000000`00a85d01 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`030cfc20 00000000`76f99ac6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00a80fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f99ac6


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

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

I'm with Phil, "I would be doing a clean install at this stage. "

mrochester · 18 Apr 2012 at 19:35

oli356 said:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80033acb30, fffffa80033ace10, fffff80002d87660}

Probably caused by : csrss.exe

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80033acb30, Terminating object
Arg3: fffffa80033ace10, Process image file name
Arg4: fffff80002d87660, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa80033acb30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`030cf0e8 fffff800`02e0e772 : 00000000`000000f4 00000000`00000003 fffffa80`033acb30 fffffa80`033ace10 : nt!KeBugCheckEx
fffff880`030cf0f0 fffff800`02dbbf7b : ffffffff`ffffffff fffffa80`0440f600 fffffa80`033acb30 fffffa80`033acb30 : nt!PspCatchCriticalBreak+0x92
fffff880`030cf130 fffff800`02d3b0f4 : ffffffff`ffffffff 00000000`00000001 fffffa80`033acb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`030cf180 fffff800`02a83f13 : fffffa80`033acb30 fffff800`c0000005 fffffa80`0440f600 00000000`00a809e0 : nt!NtTerminateProcess+0xf4
fffff880`030cf200 fffff800`02a804d0 : fffff800`02acf9df fffff880`030cfb78 fffff880`030cf8d0 fffff880`030cfc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`030cf398 fffff800`02acf9df : fffff880`030cfb78 fffff880`030cf8d0 fffff880`030cfc20 00000000`76f99c12 : nt!KiServiceLinkage
fffff880`030cf3a0 fffff800`02a84302 : fffff880`030cfb78 00000000`00000000 fffff880`030cfc20 00000000`00a810e8 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`030cfa40 fffff800`02a82e7a : 00000000`00000001 00000000`00a80f98 00000000`00a85d01 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`030cfc20 00000000`76f99ac6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00a80fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f99ac6


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

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

I'm with Phil, "I would be doing a clean install at this stage. "

I've just done a clean install on Sunday...

Anyone got any other ideas?

mrochester · 22 Apr 2012 at 08:07

Anyone got any further ideas please?

cats_five · 22 Apr 2012 at 08:45

If you put the original smaller SSD back, what happens? If the problems persist, does disconnecting everything except the bare essentials (screen, keyboard, mouse, network) help?

mrochester · 22 Apr 2012 at 10:11

cats_five said:
If you put the original smaller SSD back, what happens? If the problems persist, does disconnecting everything except the bare essentials (screen, keyboard, mouse, network) help?

Unfortunately that SSD has now gone somewhere else. The 256GB that's replaced it worked just fine in the laptop it came from.