Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD, hard drive failed showing in my computer once and then came back


08 Mar 2014   #1

win7 x64
 
 
BSOD, hard drive failed showing in my computer once and then came back

BSOD everyday after noticing that one of the hard drive failed to show in "my computer" after i did a diagnostic it went back. It hasnt disappeared since but i kept on getting bsods. It is the D: drive. My C: and E: is one separate hard disk. This is a company issued laptop and doesnt have any access to IT support from them now. I did error checking on the D: drive and it mentioned something about replacing a bad cluster. Thanks.

I couldnt get the SF diagnostic tool to work because i keep on getting errors on maybe five of the individual buttons so i resorted to the debug tool. Thanks. Please help.



Attached Files
File Type: vbs debug-gparayno-xxxx.vbs (385 Bytes, 0 views)
My System SpecsSystem Spec
.

08 Mar 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont start a new thread. Attach the data in your next post.
My System SpecsSystem Spec
08 Mar 2014   #3

win7 x64
 
 

I dont understand. Is there any data that I have to get now? Im attaching the debug files again.


Attached Files
File Type: vbs debug-dellm6600-xxxx.vbs (385 Bytes, 0 views)
My System SpecsSystem Spec
.


08 Mar 2014   #4

win7 x64
 
 

debug file zipped attached. sorry i thought i have attached the zip file. my mistake.


Attached Files
File Type: zip debug-GPARAYNO-1-EAG-Sun_03_09_2014__01201_32.zip (805.7 KB, 2 views)
My System SpecsSystem Spec
08 Mar 2014   #5
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Also search for any possible BIOS update in Dell for your model.
____________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800fde2028, be200000, 11152}

Probably caused by : GenuineIntel

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

7: 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: fffffa800fde2028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000011152, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0217cb58 fffff800`0381fa3b : 00000000`00000124 00000000`00000000 fffffa80`0fde2028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0217cb60 fffff800`039e2463 : 00000000`00000001 fffffa80`0fdcfd30 00000000`00000000 fffffa80`0fdcfd80 : hal!HalBugCheckSystem+0x1e3
fffff880`0217cba0 fffff800`0381f700 : 00000000`00000728 fffffa80`0fdcfd30 fffff880`0217cf30 fffff880`0217cf00 : nt!WheaReportHwError+0x263
fffff880`0217cc00 fffff800`0381f052 : fffffa80`0fdcfd30 fffff880`0217cf30 fffffa80`0fdcfd30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0217cd50 fffff800`0381ef0d : 00000000`00000008 00000000`00000001 fffff880`0217cfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0217cd90 fffff800`03812e88 : 00000000`00000001 fffff880`02174180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0217cdc0 fffff800`038ca4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0217cdf0 fffff800`038ca313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0217cf30 fffff880`05202c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0219cb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}

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

7: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.6, DMIVersion 38, Size=4820]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = Dell Inc.
BiosVersion = A07
BiosReleaseDate = 10/18/2011
SystemManufacturer = Dell Inc.
SystemProductName = Precision M6600
SystemVersion = 01
BaseBoardManufacturer = Dell Inc.
BaseBoardProduct = 04YY4M
BaseBoardVersion = A00
My System SpecsSystem Spec
Reply

 BSOD, hard drive failed showing in my computer once and then came back




Thread Tools



Similar help and support threads for2: BSOD, hard drive failed showing in my computer once and then came back
Thread Forum
Windows 7: External hard drive not showing up in my computer Hardware & Devices
External Hard Drive installed but not showing up on My Computer Hardware & Devices
external hard drive not showing in 'My Computer' Hardware & Devices
BSOD HDD Failed - Install Windows 7 on external hard drive from boot General Discussion
secondary hard drive not showing in my computer Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:59 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33