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: HP Elite M9600T Crash


19 May 2010   #1

Windows 7 Ultimate
 
 
HP Elite M9600T Crash

I have an HP Elite M9600T desktop. Love the computer, but one problem. Within the first 10-15 minutes of turning it on, it will blue screen and crash. Thing is, when it powers back on, it will run until I shut it down. If I leave it on 24/7, it runs beautifully. I've read threads where there were actual class action suits and things being considered for this machine. I am an HP supporter, don't wanna go that route. lol

I'm trying to find out what the actual problem is with the thing. I'm posting a couple of photos of the crash report. Also wrote down the code of 0x00000101 on the blue screen when it crashed this last time. Any ideas?

My System SpecsSystem Spec
.

19 May 2010   #2

Windows 7 Professional x64
 
 

Could you please upload your dmps for us? http://www.sevenforums.com/tutorials...en-forums.html

It looks like hardware failure. Read this article, please: http://www.sevenforums.com/crash-loc...-what-try.html

Especially test your RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run it for at least 5 passes.

Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/
Quote:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Try this free stress test: http://www.mersenne.org/freesoft/
Quote:
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
My System SpecsSystem Spec
19 May 2010   #3

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by jblue21 View Post
I have an HP Elite M9600T desktop. Love the computer, but one problem. Within the first 10-15 minutes of turning it on, it will blue screen and crash. Thing is, when it powers back on, it will run until I shut it down. If I leave it on 24/7, it runs beautifully. I've read threads where there were actual class action suits and things being considered for this machine. I am an HP supporter, don't wanna go that route. lol

I'm trying to find out what the actual problem is with the thing. I'm posting a couple of photos of the crash report. Also wrote down the code of 0x00000101 on the blue screen when it crashed this last time. Any ideas?


We need the actual DMP file created when your computer crashed. Use these to find and upload them to us. http://www.sevenforums.com/crash-loc...d-problem.html


Ken
My System SpecsSystem Spec
.


20 May 2010   #4

Windows 7 Ultimate
 
 

Ok, here's the minidump file from yesterday.
My System SpecsSystem Spec
24 May 2010   #5

Windows 7 Ultimate
 
 

So, anyone got any ideas from that DMP file?
My System SpecsSystem Spec
24 May 2010   #6

Windows 7 Professional x64
 
 

See my post above.

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_051910-75504-01.zip\051910-75504-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`03247e50
Debug session time: Wed May 19 10:45:05.794 2010 (GMT-4)
System Uptime: 0 days 0:00:12.776
Loading Kernel Symbols
...............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008ab6038, 0, 0}

Probably caused by : hardware

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

7: kd> lmntsmn
start             end                 module name
fffff880`00e00000 fffff880`00e57000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`0102f000 fffff880`0103a000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00e73000 fffff880`00f33000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`013c3000 fffff880`013f3000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d14000 fffff880`00d72000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`014cb000 fffff880`0153e000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`015df000 fffff880`015ed000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0143a000 fffff880`01450000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`02d8f000 fffff880`02da2000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`02c73000 fffff880`02d8f000   dump_iaStor dump_iaStor.sys Thu Jun 04 21:53:40 2009 (4A287AA4)
fffff880`01086000 fffff880`0109a000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0103a000 fffff880`01086000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0154f000 fffff880`01559000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01400000 fffff880`0143a000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`01600000 fffff880`0164a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`035e7000 fffff800`03630000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`017f2000 fffff880`017fb000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`010a4000 fffff880`011c0000   iaStor   iaStor.sys   Thu Jun 04 21:53:40 2009 (4A287AA4)
fffff880`011c0000 fffff880`011de000   jraid    jraid.sys    Fri Jul 17 11:31:50 2009 (4A609966)
fffff800`00ba2000 fffff800`00bac000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`014b1000 fffff880`014cb000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0179d000 fffff880`017c8000   ksecpkg  ksecpkg.sys  Mon Jul 13 19:50:34 2009 (4A5BC84A)
fffff880`00cbc000 fffff880`00d00000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00c5c000 fffff880`00c76000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00e60000 fffff880`00e6a000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01453000 fffff880`014b1000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`017e0000 fffff880`017f2000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0164b000 fffff880`0173d000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0173d000 fffff880`0179d000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`0300a000 fffff800`035e7000   nt       ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600)
fffff880`01220000 fffff880`013c3000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00da5000 fffff880`00dba000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d72000 fffff880`00da5000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`0153e000 fffff880`0154f000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00d00000 fffff880`00d14000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`011de000 fffff880`011e9e00   PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
fffff880`015a5000 fffff880`015df000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01000000 fffff880`0102f000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`017d8000 fffff880`017e0000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`00fe6000 fffff880`00ff3000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`017c8000 fffff880`017d8000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00dba000 fffff880`00dcf000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01559000 fffff880`015a5000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00f33000 fffff880`00fd7000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00fd7000 fffff880`00fe6000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00e57000 fffff880`00e60000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list
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: fffffa8008ab6038, 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`033696f0 fffff800`032c4a89 : fffffa80`08ab6010 fffffa80`06a36b60 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03369c10 fffff800`031a6547 : fffffa80`08ab6010 fffff800`0321f5f8 fffffa80`06a36b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03369c40 fffff800`0310eb95 : fffff800`03281360 fffffa80`08b35ab8 fffffa80`08b35ab0 fffffa80`06a36b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03369c80 fffff800`03089161 : fffff880`0106ae00 fffff800`0310eb70 fffffa80`06a36b60 3dcf3dcf`be74be74 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03369cb0 fffff800`0331f166 : dde5dde5`b4a6b4a6 fffffa80`06a36b60 00000000`00000080 fffffa80`069a7890 : nt!ExpWorkerThread+0x111
fffff880`03369d40 fffff800`0305a486 : fffff880`03171180 fffffa80`06a36b60 fffff880`0317c0c0 eeddeedd`b1e5b1e5 : nt!PspSystemThreadStartup+0x5a
fffff880`03369d80 00000000`00000000 : fffff880`0336a000 fffff880`03364000 fffff880`02ef1540 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
---------
My System SpecsSystem Spec
Reply

 HP Elite M9600T Crash




Thread Tools



Similar help and support threads for2: HP Elite M9600T Crash
Thread Forum
HP m9600t Win7 clock interrupt not received on secondary processor BSOD Help and Support
Sniper Elite V2... PC Campaign Gaming
Solved HP Pavillion m9600t Windows 7 Home Premium keeps crashing BSOD Help and Support
BSOD Win 7 on HP Elite w/i7 BSOD Help and Support
BSOD on HP Elite BSOD Help and Support
Sniper Elite Gaming
keyboard elite for bluetooth 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 06:42 AM.
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