Jump to content



Photo

  • Please log in to reply
6 replies to this topic

#1 celahudini

celahudini

    Neowinian

  • Joined: 24-September 13

Posted 24 September 2013 - 16:11

Well a couple of months ago there was a thunderstorm near me and although my pc was turned off the PSU was plugged into the power source.

In the frist month I had maybe 2 or 3 BSODs but I dind't think much of it at the time. After a month or so my Razer Abyyssus died on me (USB device not recognized) and then the same thing happend with the wireless reciever of my Logitech gamepad (F710). Now the damn thing (the pc) just freezes or resets at will (no BSOD). Sometimes I can play some heavy games on my PC like GTA 4 Skyrim or whatever and I rarely get a reset. At other times nothing has to be running (defrag download or whatever) just the desktop is displayed and the keyboard and mouse freeze and stay so or the PC resets at will. It started happening on Win7 enterprise x64, after that I went to Win 8 x64 and the same thing kept happening so I went back to Win7 Enterprise x64 a couple of days ago.

Can anyone analyze my crash dumps and help me figure out what component is failing cause as everybody knows the Microsoft support are pretty much useless with this. I have a bunch of crash dumps from just the last couple of days (Win7) .

My Cpu specs:

Motherboard : Asus P5K Pro - latest BIOS

CPU : Intel Core 2 Duo E8400 @ 3.0 Ghz - never overclocked

RAM: 4x1gb DDR2 Kingston HyperX (not really sure if it's working @800 Mhz or @1033)

GPU: Asus Gtx560 Ti 1gb

Other: Pci-E usb 3.0 controller

Hard drive: Western Digital 750gb Sata II I believe

Optical drives: LG Dvd-rw sata

PSU: Chieftec 650w

Peripherals : Logitech F710 gamepad,Logitech C260 webcam,Logitech wired mouse (the cheapest one lol), Gigabyte wireless keyboard

 

The 2 XML files are from C:\User\username\AppData\Local\Temp\

I also have 8 more dmp files from the last 5 days from C:\Windows\Minidump but the forum wont let me upload them here (You aren't permitted to upload this kind of file)

So if anyone can look into the files I'd greatly appreciate it. Thx in advance

Attached Files




#2 sc302

sc302

    Neowinian Senior

  • Tech Issues Solved: 23
  • Joined: 12-July 05
  • Location: NJ, USA

Posted 24 September 2013 - 16:34

http://www.osronline...fm?name=analyze

 

look for the dll or exe causing the crash dump or paste the dump here.



#3 OP celahudini

celahudini

    Neowinian

  • Joined: 24-September 13

Posted 24 September 2013 - 17:02

Well this is what I got

 

 

collapse.gifPrimary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`034566d0
Debug session time: Tue Sep 24 06:36:26.056 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:14.648
*******************************************************************************
* *
* 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: fffffa8004bb38f8, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`037e76f0 fffff800`034d3ca9 : fffffa80`04bb38d0 fffffa80`039ff660 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`037e7c10 fffff800`033b4e97 : fffffa80`04bb38d0 fffff800`0342e2d8 fffffa80`039ff660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`037e7c40 fffff800`0331c285 : fffff800`0348fb40 00000000`00000001 fffffa80`04ae0be0 fffffa80`039ff660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`037e7c80 fffff800`03292261 : fffff880`00e5fe00 fffff800`0331c260 fffffa80`039ff600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`037e7cb0 fffff800`03526bae : ff7fffbd`ff7dffff fffffa80`039ff660 00000000`00000080 fffffa80`0396eb30 : nt!ExpWorkerThread+0x111
fffff880`037e7d40 fffff800`032798c6 : fffff880`009e8180 fffffa80`039ff660 fffff880`009f2f40 ffffff7f`ffefdfff : nt!PspSystemThreadStartup+0x5a
fffff880`037e7d80 00000000`00000000 : fffff880`037e8000 fffff880`037e2000 fffff880`037e72d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
collapse.gifCrash Code Links collapse.gifLoaded Module List
start end module name
fffff800`00bc2000 fffff800`00bcc000 kdcom kdcom.dll
fffff800`03213000 fffff800`037f9000 nt ntkrnlmp.exe
fffff800`037f9000 fffff800`03842000 hal hal.dll
fffff880`00c00000 fffff880`00c72000 cng cng.sys
fffff880`00cbc000 fffff880`00d0b000 mcupdate mcupdate.dll
fffff880`00d0b000 fffff880`00d1f000 PSHED PSHED.dll
fffff880`00d1f000 fffff880`00d7d000 CLFS CLFS.SYS
fffff880`00d7d000 fffff880`00ddb000 msrpc msrpc.sys
fffff880`00e00000 fffff880`00e2f000 SCSIPORT SCSIPORT.SYS
fffff880`00e2f000 fffff880`00e7b000 fltmgr fltmgr.sys
fffff880`00eb1000 fffff880`00f71000 CI CI.dll
fffff880`00f71000 fffff880`00f9b000 ataport ataport.SYS
fffff880`00f9b000 fffff880`00fe2000 mv61xx mv61xx.sys
fffff880`01011000 fffff880`010d3000 Wdf01000 Wdf01000.sys
fffff880`010d3000 fffff880`010e3000 WDFLDR WDFLDR.SYS
fffff880`010e3000 fffff880`0113a000 ACPI ACPI.sys
fffff880`0113a000 fffff880`01143000 WMILIB WMILIB.SYS
fffff880`01143000 fffff880`0114d000 msisadrv msisadrv.sys
fffff880`0114d000 fffff880`01180000 pci pci.sys
fffff880`01180000 fffff880`0118d000 vdrvroot vdrvroot.sys
fffff880`0118d000 fffff880`01197000 iusb3hcs iusb3hcs.sys
fffff880`01197000 fffff880`0119f000 intelide intelide.sys
fffff880`0119f000 fffff880`011af000 PCIIDEX PCIIDEX.SYS
fffff880`011af000 fffff880`011b6000 pciide pciide.sys
fffff880`011b6000 fffff880`011d0000 mountmgr mountmgr.sys
fffff880`011d0000 fffff880`011d9000 atapi atapi.sys
fffff880`011d9000 fffff880`011e1000 mv61xxmm mv61xxmm.sys
fffff880`011e1000 fffff880`011ec000 amdxata amdxata.sys
fffff880`011ec000 fffff880`01200000 fileinfo fileinfo.sys
fffff880`01200000 fffff880`0120c000 BATTC BATTC.SYS
fffff880`0120c000 fffff880`01221000 volmgr volmgr.sys
fffff880`01221000 fffff880`0127d000 volmgrx volmgrx.sys
fffff880`01282000 fffff880`019e0000 kl1 kl1.sys
fffff880`019e0000 fffff880`019f5000 partmgr partmgr.sys
fffff880`019f5000 fffff880`019fe000 compbatt compbatt.sys
fffff880`01a00000 fffff880`01a1b000 ksecdd ksecdd.sys
fffff880`01a1b000 fffff880`01a2c000 pcw pcw.sys
fffff880`01a2c000 fffff880`01a36000 Fs_Rec Fs_Rec.sys
fffff880`01a43000 fffff880`01be6000 Ntfs Ntfs.sys
fffff880`01c00000 fffff880`01c60000 NETIO NETIO.SYS
fffff880`01c60000 fffff880`01c8b000 ksecpkg ksecpkg.sys
fffff880`01ccf000 fffff880`01dc1000 ndis ndis.sys
fffff880`01e2c000 fffff880`0202f000 tcpip tcpip.sys
fffff880`0202f000 fffff880`02079000 fwpkclnt fwpkclnt.sys
fffff880`02079000 fffff880`02089000 vmstorfl vmstorfl.sys
fffff880`02089000 fffff880`020d5000 volsnap volsnap.sys
fffff880`020d5000 fffff880`020dd000 spldr spldr.sys
fffff880`020dd000 fffff880`02117000 rdyboost rdyboost.sys
fffff880`02117000 fffff880`02129000 mup mup.sys
fffff880`02129000 fffff880`02132000 hwpolicy hwpolicy.sys
fffff880`02132000 fffff880`0216c000 fvevol fvevol.sys
fffff880`0216c000 fffff880`02182000 disk disk.sys
fffff880`02182000 fffff880`021b2000 CLASSPNP CLASSPNP.SYS
fffff880`021b2000 fffff880`021c0000 crashdmp crashdmp.sys
fffff880`021c0000 fffff880`021cc000 dump_ataport dump_ataport.sys
fffff880`021cc000 fffff880`021d5000 dump_atapi dump_atapi.sys
fffff880`021d5000 fffff880`021e8000 dump_dumpfve dump_dumpfve.sys
Mini Kernel Dump does not contain unloaded driver list
 
expand.gifRaw Stack Contents expand.gifDump Header Information expand.gifStrings

 

 

 

Googling WHEA_UNCORRECTABLE_ERROR (124) I found that It can be a number of reasons - CPU,MB,PSU or Overclocking

Is there anyway that I could narrow down which one of those is it? I'm planning on buying a new MB,CPU and RAM with the latest intel i7 1150 micro-architecture + a UPS and a voltage regulator which will probably set me back around 1000 euros so I wanted to know do I have to change my PSU as well



#4 sc302

sc302

    Neowinian Senior

  • Tech Issues Solved: 23
  • Joined: 12-July 05
  • Location: NJ, USA

Posted 24 September 2013 - 17:20

I would say it is the processor having issues.  Make sure the psu is big enough to deal with the load and you will be fine, going bigger isn't a bad idea being just around where you need to be can be an issue.  The computer will only draw what is needed so bigger isn't an issue, too small is.



#5 Tews

Tews

    Professional Lurker

  • Tech Issues Solved: 1
  • Joined: 13-October 03
  • Location: Somewhere on a beach

Posted 24 September 2013 - 17:27

 

Stop 0x124 - what it means and what to try

Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated. 

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. The most obvious examples are the RAM and HDD(s). For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing. For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc. Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
 
Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware. 
 

 

 

I hope this helps...



#6 sc302

sc302

    Neowinian Senior

  • Tech Issues Solved: 23
  • Joined: 12-July 05
  • Location: NJ, USA

Posted 24 September 2013 - 17:39

To narrow down, start bringing the machine down to stock out of box form.  Maybe even reinstall windows.  You will need to stress test the components...  If you are going to upgrade anyway see my previous post.  (sorry didn't pay attention to the rest of your reply post).



#7 OP celahudini

celahudini

    Neowinian

  • Joined: 24-September 13

Posted 24 September 2013 - 18:07

I hope this helps...

Well the first 5 steps are all checked. I will go through the rest of them now and report back. MDSCHED finished without any errors. I will try memtest86 and I think I have a bootable cd somewhere with GOLD MEMORY so I'll check the ram and if none report any errors the last option for RAM is I can taking a module out at a time and testing as I have 4 of them.  As far as the hard drive goes I checked it yesterday with hard disk sentinel and it reported 100% health and 0 bad sectors, estimating it's lifespan to around 2 more years 

 

 

To narrow down, start bringing the machine down to stock out of box form.  Maybe even reinstall windows.  You will need to stress test the components...  If you are going to upgrade anyway see my previous post.  (sorry didn't pay attention to the rest of your reply post).

 

Well honestly I was planning on buying a completly new PC since this one (whitout the Graphic Card and PSU) is 5 and a half years old now and at the time was payed somewhere in the range of 800 euros. IF and IF the motherboard, processor and Ram memory were 100% working and I wanted to sell them I think I couldn't even get 100 euros so I was planning on so to say RETIRING this computer. But as it turns out I guess I'll now have to buy a completely new PC, but than again I wanted to see If I can fix this one and maybe even invest some reasonable sum of money in it to make it working so I can give it away. 
I'll now try and stress test the components and see if I can narrow down the problem (at this point I wouldn't rule out kaspersky internet security or any other 3rd party software that I have installed lol)

 

Thx for the fast replies guys, will see If I can get any more info and I'll post again