SAS HDD and memory dump

Hi guys, first of all excuse me for my bad english, but i need help.
I have windows 7 Ultimate 64 bit and two HDD SAS in a RAID 0.
I got several Blue screen of death and i can't read any memory dump file.
The PC stop with this error 0x000000F4 (0x0000000000000003, 0xFFFFFA8008059A00, 0xFFFFFA80080590E0, 0xFFFFF80001D90540)

WRITING MEMORY DUMP .......

I think it can't write the file because of the SAS HDD am i correct?

I go to control panel-system-advanced options-options(my S.O. is in italian then i hope you can get where i go) and changed the place where to save the file dump and put there d:\memory.dmp
the HDD d: is IDE
But... still don't get any file... what and how i can do to make the system to write the file dump?

dalink said:

Hi guys, first of all excuse me for my bad english, but i need help.
I have windows 7 Ultimate 64 bit and two HDD SAS in a RAID 0.
I got several Blue screen of death and i can't read any memory dump file.
The PC stop with this error 0x000000F4 (0x0000000000000003, 0xFFFFFA8008059A00, 0xFFFFFA80080590E0, 0xFFFFF80001D90540)

WRITING MEMORY DUMP .......

I think it can't write the file because of the SAS HDD am i correct?

I go to control panel-system-advanced options-options(my S.O. is in italian then i hope you can get where i go) and changed the place where to save the file dump and put there d:\memory.dmp
the HDD d: is IDE
But... still don't get any file... what and how i can do to make the system to write the file dump?

Are you sure there are not DMP files? use these to find and upload them. https://www.sevenforums.com/crash-loc...d-problem.html


thanks

Ken

zigzag3143 said:

Are you sure there are not DMP files? use these to find and upload them. https://www.sevenforums.com/crash-loc...d-problem.html


thanks

Ken

Yes i'm sure there is no file dump, i don't have even the folder, i used the search function and scann all the entire HDD but nothing...

Nobody can help me?

Upup

Jonathan_King said:

Be sure the system is creating a minidump.

Yes i check already and it's like that, but no minidump file....and the only thing i can think it's something about the SAS HDD.. like the drivers are not working and then got the blue screen and it can't write on that HDD
That's why i also try to change the position where to save the minidump file in the second HDD that is a normal IDE HDD. But nothing....

ok i got a dmp file but was not a BSOD just a crash to the desktop and debugging the file i found (if i'm not wrong) that the problem is the driver for the HDD SAS as i suspected.
here the debug:

4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007b1d8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`025596f0 fffff800`01f04a79 : fffffa80`07b1d8d0 fffffa80`0551c680 00000000`000007ff 00000000`00000030 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02559c10 fffff800`01de65a7 : fffffa80`07b1d8d0 fffff800`01e5f5f8 fffffa80`0551c680 fffff8a0`00332940 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02559c40 fffff800`01d4eb85 : fffff800`01ec1360 fffff800`01e67580 00000000`00000000 fffffa80`0551c680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02559c80 fffff800`01cc7861 : fffff800`02112500 fffff800`01d4eb60 fffffa80`0551c680 38a238a2`38a238a2 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02559cb0 fffff800`01f5fa86 : 8a678a67`8a678a67 fffffa80`0551c680 00000000`00000080 fffffa80`055081b0 : nt!ExpWorkerThread+0x111
fffff880`02559d40 fffff800`01c98b06 : fffff880`0245d180 fffffa80`0551c680 fffff880`024681c0 b171b171`b171b171 : nt!PspSystemThreadStartup+0x5a
fffff880`02559d80 00000000`00000000 : fffff880`0255a000 fffff880`02554000 fffff880`02558bd0 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------