Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD problem


  • Please log in to reply
8 replies to this topic

#1 MaxMillion

MaxMillion

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:09 AM

Posted 18 July 2018 - 09:02 AM

Hello friends, I recent had a new system built and when I do audio editing it randomly BSOD on me.

I have the machine perhaps 8 months but the last month started doing a lot of BSOD

CPU is not overclocked, running at 4.2 Ghz always

Crash Analysis reads:

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: ffffa800e5710028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
ffffbe01`13484be8 fffff803`f37be520 : 00000000`00000124 00000000`00000000 ffffa800`e5710028 00000000`be000000 : nt!KeBugCheckEx
ffffbe01`13484bf0 fffff80c`d06014ba : ffffa800`e5710028 ffffa800`e50805f0 ffffa800`e50805f0 ffffa800`e50805f0 : hal!HalBugCheckSystem+0xd0
ffffbe01`13484c30 fffff803`f30e6ff1 : ffffa800`e5710028 00000000`00000000 ffffa800`e50805f0 ffffa800`e50805f0 : PSHED!PshedBugCheckSystem+0xa
ffffbe01`13484c60 fffff803`f37bfc60 : 00000000`00000728 00000000`00000005 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
ffffbe01`13484cc0 fffff803`f37bffc0 : 00000000`00000010 ffffa800`e5080640 ffffbe01`13484e68 00000000`00000005 : hal!HalpMcaReportError+0x50
ffffbe01`13484e10 fffff803`f37bfeae : ffffa800`e4d07f50 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
ffffbe01`13484e60 fffff803`f37c00f2 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffffbe01`13484ea0 fffff803`f37c0390 : ffffa800`e4d07f50 ffffbe01`134850d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffbe01`13484ed0 fffff803`f2fc493b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffbe01`13484f00 fffff803`f2fc45ff : 00000000`00000000 fffff803`f2fc4517 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffbe01`13485040 fffff80c`d1123ea2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1bf
ffff8c03`b126f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

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

 

 

 

Speccy reads:

http://speccy.piriform.com/results/ioa3COgjbnDviTutu6PFYGB

 

 

 

 

Any info on what may causing the issue?

Thanks so much in advance

 

 

 



BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,299 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:09 AM

Posted 18 July 2018 - 09:14 AM

BC BSODs Posting Instructions - http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/ , please provide the requested data in your next post to this topic.

 

Louis



#3 MaxMillion

MaxMillion
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:09 AM

Posted 18 July 2018 - 09:22 AM

Hi Louis,
Attached is the SysnativeFileCollectionApp
 
The Speccy link above provides all further info


Sorry here it is:

Attached Files


Edited by hamluis, 24 July 2018 - 06:33 AM.


#4 MaxMillion

MaxMillion
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:09 AM

Posted 20 July 2018 - 01:29 AM

Anyone?



#5 dmccoy

dmccoy

  • BSOD Kernel Dump Expert
  • 1,059 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:09 AM

Posted 23 July 2018 - 12:26 PM

The WHEA_UNCORRECTABLE_ERROR (124) is usually related to hardware errors. If under warranty you may want to return. 
 
If not start by testing the following:

Test Hard drive:
Please Download and Run SeaTools for Windows
 
1.  Once it starts it will scan for all drives connected to your computer. 
2.  Select drive you want to test.
3.  Select the Long Generic Test under the Basic Tests menu
4.  When the test is complete you will see the result under Test Status
5.  The test will indicate either Pass or Fail. 
6.  Provide the Results in your reply.

How to Use:
https://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Test Memory:
Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool

This may take hours so plan to run it overnight.
Testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes
When Memtest86+ has completed 8 or more passes take a picture and post an image and upload to your reply

MemTest86+ - Test RAM BSOD Tutorials

Stress Test Your CPU - Prime 95
https://www.tenforums.com/tutorials/16474-prime95-stress-test-your-cpu.html

- 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 please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "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).
Monitor the CPU temperature and DON'T let it exceed 85ºC. If it does, then you probably have a CPU cooling problem. This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.


We are all volunteers so please by kind, courteous and respectful of all staff and members

 

I try to respond in 24-48 hours normally and I am more active on weekdays than weekends. However, sometimes due to my health, family or life it may take me a little longer. If you have not heard from me within 72 hours then please PM me a reminder. 

 

BC BSOD Posting Instructions 


#6 MaxMillion

MaxMillion
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:09 AM

Posted 23 July 2018 - 02:26 PM

Thanks for the info,

i do have different warranties for the individual parts but not for the whole build, so it is crutial to determine exactly the part that is causing the issue.

Will try what you suggest and post the results.



#7 MaxMillion

MaxMillion
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:09 AM

Posted 24 July 2018 - 05:08 AM

So, so far i came up with these tests

 

1. Seatools - Pass

http://www.mediafire.com/view/jtv5rj3ta0et92b/seatools_1.PNG

 

2.Memtest

http://www.mediafire.com/file/z24a54nuyz43bxs/IMG_0535.JPG

 

3. Temperature

http://www.mediafire.com/view/bk4m9bht1b2h6ed/222.PNG

 

4. Prime 95

http://www.mediafire.com/view/cbgq2i47jtc1ufj/3333.PNG


Edited by MaxMillion, 24 July 2018 - 05:09 AM.


#8 MaxMillion

MaxMillion
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:09 AM

Posted 24 July 2018 - 09:17 AM

Update:

Prime95 running for 8 hours with still no errors

 

so, Im having 0 errors with HD / RAM / CPU so far after all tests completed,

is there a way to check the motherboard? any other info maybe?

 

Thank you



#9 dmccoy

dmccoy

  • BSOD Kernel Dump Expert
  • 1,059 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:09 AM

Posted 25 July 2018 - 01:04 PM

Please follow the tutorial below to run driver verifier.
https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation. It should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

When you get a Blue Screen Error (BSOD) then Rerun the Sysnative app and upload the file.

We are all volunteers so please by kind, courteous and respectful of all staff and members

 

I try to respond in 24-48 hours normally and I am more active on weekdays than weekends. However, sometimes due to my health, family or life it may take me a little longer. If you have not heard from me within 72 hours then please PM me a reminder. 

 

BC BSOD Posting Instructions 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users