First BSOD on my Desktop Computer

[IndyLive]

Hello Everyone,

I have reccently had several BSOD's while playing Dark Souls 2.

I am uploading the crash dump file for those who would be kind enough to review it. However, I cannot specify the cause of this problem short of it always happening during the time I am playing Dark Souls 2.

Thanks,

Dan

 

[Shintaro]

Ok, the crash dump indicates that the CPU may be faulty, this may or may not be correct. There are a couple of things that you can try:
Install Driver Verifier and see if a more complete crash dump file will give more detail to the hardware crash.
Or
Try updating your BIOS.
I believe this HERE is your motherboard.
Be aware that incorrectly flashing your BIOS can brick your motherboard.

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: fffffa80096d7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010014, 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:  DarkSoulsII.ex
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`009f7a58 fffff800`03a01a3b : 00000000`00000124 00000000`00000000 fffffa80`096d7028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`009f7a60 fffff800`03596463 : 00000000`00000001 fffffa80`06fc6870 00000000`00000000 fffffa80`06fc68c0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7aa0 fffff800`03a01700 : 00000000`00000728 fffffa80`06fc6870 fffff880`009f7e30 fffff880`009f7e00 : nt!WheaReportHwError+0x263
fffff880`009f7b00 fffff800`03a01052 : fffffa80`06fc6870 fffff880`009f7e30 fffffa80`06fc6870 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7c50 fffff800`03a00f0d : 00000000`00000004 00000000`00000001 fffff880`009f7eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7c90 fffff800`039f4e88 : fffffa80`09801640 00000000`80000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7cc0 fffff800`0347e4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7cf0 fffff800`0347e313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7e30 fffff800`03485b05 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0c39c170 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAcquireResourceSharedLite+0x55


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_TLB
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_TLB
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_tlb
FAILURE_ID_HASH:  {b49c6f57-bc2b-eda7-054a-fc323ea8c38d}

Driver verifier

The Driver Verifier tool that is included in every version of Windows since Windows 2000 it is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior.

***FIRST: Please backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Windows 7 Startup Repair feature.)

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select:
   ---- Special Pool
   ---- Pool Tracking
   ---- Force IRQL Checking
   ----Deadlock Detection
   ---- Security Checks (Windows 7 & 8)
   ---- DDI compliance checking (Windows 8)
   ---- Miscellaneous Checks
   
5. Click "Next"
6. Select "Select driver names from a list" and click "Next"
7. Then select all drivers NOT provided by Microsoft and click "Next"
8. Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Will I see anything when I enable Driver Verifier?

No, Driver Verifier configures Windows so that people looking at the crash dump files get (in most cases) more detailed information about what actually crashed the computer.
​

How Long should I wait for a crash?

- If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
​

How do I turn Driver Verifier off?!

- Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page.

- Or press the Windows Key + R, and type in "verifier /reset" (Without the quotes)

- Then locate and zip up the memory dump file and upload it with your next post. then locate and zip up the memory dump file and upload it with your next post.
​

I can't get in to Windows, what do I do?

- If Windows will not start and get to a login screen or desktop, because it crashes too soon, try it in Safe Mode.


- If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
​

How do I put the crash dump files in a Zip file?

Instructions on putting files in a Zip file and extracting (Taking them out) again are explained HERE.
​