BSOD is getting worst even when I start open dota2

J

jstong

New Member
Messages
7
My PC BSOD when I start playing dota2. This problem happen since 2 years ago, but the problem is getting worst even when PC idle also getting BSOD. I have change hdd, ram and even take out graphic card using on board graphic also get BSOD.
I not sure wthere is the motherboard cause BSOD? :cry:

View attachment 61048
 

My Computer

System One

  • OS
    window 8.1
    Computer type
    PC/Desktop
    CPU
    Intel i5 3570
    Motherboard
    gigabyte z77m-d3h
    Memory
    Corsair 8gb
    Graphics Card(s)
    Radeon HD7850
Hi,
First thing you need to do is to visit Intel website and download latest drivers for your make and model.
Also updating mother board drivers.

Then next thing to do is to run diagnostic tool from Intel:
Intel® Processor Diagnostic Tool (64-bit)

When you complete this test post screenshot here.

Additionally, if test fails after driver update you can try to disable Level 2 cache in BIOS settings ( if there is such option ) and re-run the test.


Code: 
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


[B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
[COLOR=#ff0000]A fatal hardware error has occurred. Parameter 1 identifies the type of error[/COLOR]
[COLOR=#ff0000]source that reported the error. Parameter 2 holds the address of the[/COLOR]
[COLOR=#ff0000]WHEA_ERROR_RECORD structure that describes the error conditon.[/COLOR]
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000044d0028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, Low order 32-bits of the MCi_STATUS value.


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




[COLOR=#ff0000]BUGCHECK_STR:  0x124_GenuineIntel[/COLOR]


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  dota.exe


CURRENT_IRQL:  f


ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


STACK_TEXT:  
ffffd000`20189b38 fffff803`31448c93 : 00000000`00000124 00000000`00000000 ffffe000`044d0028 00000000`fe200000 : nt!KeBugCheckEx
ffffd000`20189b40 fffff803`3163d401 : 00000000`00000001 ffffe000`003afb50 ffffe000`003afb50 ffffe000`044d0028 : hal!HalBugCheckSystem+0xcf
ffffd000`20189b80 fffff803`31449120 : 00000000`00000728 00000000`00000002 ffffd000`20189f70 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`20189be0 fffff803`3144948d : ffffe000`00000010 ffffe000`003afb50 ffffd000`20189d88 ffffe000`003afb50 : hal!HalpMcaReportError+0x50
ffffd000`20189d30 fffff803`31449378 : ffffe000`003af7a0 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`20189d80 fffff803`314495c2 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`20189dc0 fffff803`3144974f : ffffe000`003af7a0 ffffd000`20189ff0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`20189df0 fffff803`315dcbbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`20189e20 fffff803`315dc971 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
[COLOR=#ff0000]ffffd000`20189f60 00000000`549588b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171[/COLOR]
00000000`1fa8f494 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x549588b0




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: GenuineIntel


IMAGE_NAME:  GenuineIntel


DEBUG_FLR_IMAGE_TIMESTAMP:  0


IMAGE_VERSION:  


FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache


FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}


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


2: kd> !errrec ffffe000044d0028
===============================================================================
Common Platform Error Record @ ffffe000044d0028
-------------------------------------------------------------------------------
Record Id     : 01d080f622165db4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
[COLOR=#ff0000]Notify Type   : Machine Check Exception[/COLOR]
Timestamp     : 4/27/2015 14:36:29 (UTC)
Flags         : 0x00000000


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe000044d00a8
Section       @ ffffe000044d0180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal


Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=#ff0000]Error Type    : Cache error[/COLOR]
[COLOR=#ff0000]Operation     : Data Read[/COLOR]
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000004


===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe000044d00f0
Section       @ ffffe000044d0240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal


Local APIC Id : 0x0000000000000004
CPU Id        : a9 06 03 00 00 08 10 04 - ff e3 ba 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00


Proc. Info 0  @ ffffe000044d0240


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe000044d0138
Section       @ ffffe000044d02c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
[COLOR=#ff0000]Severity      : Fatal[/COLOR]


[COLOR=#ff0000]Error         : DCACHEL2_DRD_ERR (Proc 2 Bank 8)[/COLOR]
  Status      : 0xfe20000000021136
  Address     : 0x0000000212c71040
  Misc.       : 0x000000f040000086
 

My Computer

System One

  • OS
    Windows 8.1 Enterprise
Addictive Gamer said:
Hi,
First thing you need to do is to visit Intel website and download latest drivers for your make and model.
Also updating mother board drivers.

Then next thing to do is to run diagnostic tool from Intel:
Intel® Processor Diagnostic Tool (64-bit)

When you complete this test post screenshot here.

Additionally, if test fails after driver update you can try to disable Level 2 cache in BIOS settings ( if there is such option ) and re-run the test.


Code: 
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


[B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
[COLOR=#ff0000]A fatal hardware error has occurred. Parameter 1 identifies the type of error[/COLOR]
[COLOR=#ff0000]source that reported the error. Parameter 2 holds the address of the[/COLOR]
[COLOR=#ff0000]WHEA_ERROR_RECORD structure that describes the error conditon.[/COLOR]
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000044d0028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, Low order 32-bits of the MCi_STATUS value.


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




[COLOR=#ff0000]BUGCHECK_STR:  0x124_GenuineIntel[/COLOR]


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  dota.exe


CURRENT_IRQL:  f


ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre


STACK_TEXT:  
ffffd000`20189b38 fffff803`31448c93 : 00000000`00000124 00000000`00000000 ffffe000`044d0028 00000000`fe200000 : nt!KeBugCheckEx
ffffd000`20189b40 fffff803`3163d401 : 00000000`00000001 ffffe000`003afb50 ffffe000`003afb50 ffffe000`044d0028 : hal!HalBugCheckSystem+0xcf
ffffd000`20189b80 fffff803`31449120 : 00000000`00000728 00000000`00000002 ffffd000`20189f70 00000000`00000000 : nt!WheaReportHwError+0x22d
ffffd000`20189be0 fffff803`3144948d : ffffe000`00000010 ffffe000`003afb50 ffffd000`20189d88 ffffe000`003afb50 : hal!HalpMcaReportError+0x50
ffffd000`20189d30 fffff803`31449378 : ffffe000`003af7a0 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
ffffd000`20189d80 fffff803`314495c2 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`20189dc0 fffff803`3144974f : ffffe000`003af7a0 ffffd000`20189ff0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`20189df0 fffff803`315dcbbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`20189e20 fffff803`315dc971 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
[COLOR=#ff0000]ffffd000`20189f60 00000000`549588b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171[/COLOR]
00000000`1fa8f494 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x549588b0




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: GenuineIntel


IMAGE_NAME:  GenuineIntel


DEBUG_FLR_IMAGE_TIMESTAMP:  0


IMAGE_VERSION:  


FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache


FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}


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


2: kd> !errrec ffffe000044d0028
===============================================================================
Common Platform Error Record @ ffffe000044d0028
-------------------------------------------------------------------------------
Record Id     : 01d080f622165db4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
[COLOR=#ff0000]Notify Type   : Machine Check Exception[/COLOR]
Timestamp     : 4/27/2015 14:36:29 (UTC)
Flags         : 0x00000000


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe000044d00a8
Section       @ ffffe000044d0180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal


Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=#ff0000]Error Type    : Cache error[/COLOR]
[COLOR=#ff0000]Operation     : Data Read[/COLOR]
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000004


===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe000044d00f0
Section       @ ffffe000044d0240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal


Local APIC Id : 0x0000000000000004
CPU Id        : a9 06 03 00 00 08 10 04 - ff e3 ba 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00


Proc. Info 0  @ ffffe000044d0240


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe000044d0138
Section       @ ffffe000044d02c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
[COLOR=#ff0000]Severity      : Fatal[/COLOR]


[COLOR=#ff0000]Error         : DCACHEL2_DRD_ERR (Proc 2 Bank 8)[/COLOR]
  Status      : 0xfe20000000021136
  Address     : 0x0000000212c71040
  Misc.       : 0x000000f040000086
Click to expand...

I have updated all intel driver and motherboard driver to latest version.
I also run the diagnostic tool from intel and result pass, but still getting BSOD.
attachment.php
 

My Computer

System One

  • OS
    window 8.1
    Computer type
    PC/Desktop
    CPU
    Intel i5 3570
    Motherboard
    gigabyte z77m-d3h
    Memory
    Corsair 8gb
    Graphics Card(s)
    Radeon HD7850
jstong said:
I have updated all intel driver and motherboard driver to latest version.
I also run the diagnostic tool from intel and result pass, but still getting BSOD.
Click to expand...

That's great!
It would help if you can provide your latest BSOD dumps, because currently we have only one which could be just about anything. Have you try to disable L2 cache in BIOS? and then reproduce BSOD?

Run memory test and share results:
Diagnosing memory problems on your computer
 

My Computer

System One

  • OS
    Windows 8.1 Enterprise
Addictive Gamer said:
jstong said:
I have updated all intel driver and motherboard driver to latest version.
I also run the diagnostic tool from intel and result pass, but still getting BSOD.
Click to expand...

That's great!
It would help if you can provide your latest BSOD dumps, because currently we have only one which could be just about anything. Have you try to disable L2 cache in BIOS? and then reproduce BSOD?

Run memory test and share results:
Diagnosing memory problems on your computer
Click to expand...

Run memory test and there is no problem detected. Here are the others dmp file.
I can't find how to disable L2 cache in BIOS.
View attachment 61064
 

My Computer

System One

  • OS
    window 8.1
    Computer type
    PC/Desktop
    CPU
    Intel i5 3570
    Motherboard
    gigabyte z77m-d3h
    Memory
    Corsair 8gb
    Graphics Card(s)
    Radeon HD7850
Hi,
I see you ran prime95 and that caused BOSD

I would run it again but this time with clean boot:
https://support.microsoft.com/en-us/kb/929135

Once you clean boot into windows run test again ( bellow is a link to Prime95 ):
GIMPS - Free Prime95 software downloads - PrimeNet

here is how will you run the test:

View attachment 60994

On next screen set "torture" setup like in following image and hit "OK"

View attachment 60995

After test is done post results.


Additional things you should consider is following:

Your BIOS is in beta stage, ( make sure you understand how to roll back BIOS )
GIGABYTE - Motherboard - Socket 1155 - GA-Z77M-D3H (rev. 1.1)

There is a kernel mode driver inside your temp folder:
C:\Users\<your user name>\AppData\Local\Temp\\cpuz138\cpuz138_x64.sys

Ensure drivers you have installed are from gigabyte website only, ( Except those that do not exist there such as ATI).

Please share results of prime95 test in clean boot mode before doing any other changes.
 

My Computer

System One

  • OS
    Windows 8.1 Enterprise
In clean boot I can run prime95 for an hours without BSOD and even playing dota2 also did not cause BSOD. So could it be some driver causing the BSOD? Here is the results of prime95 in clean boot

View attachment 61092
 

My Computer

System One

  • OS
    window 8.1
    Computer type
    PC/Desktop
    CPU
    Intel i5 3570
    Motherboard
    gigabyte z77m-d3h
    Memory
    Corsair 8gb
    Graphics Card(s)
    Radeon HD7850

My Computer

System One

  • OS
    window 8.1
    Computer type
    PC/Desktop
    CPU
    Intel i5 3570
    Motherboard
    gigabyte z77m-d3h
    Memory
    Corsair 8gb
    Graphics Card(s)
    Radeon HD7850
Ok, maybe I missed something but there are only 2 drivers that look suspicious:



Code: 
// Apple
[COLOR=#ff0000]
usbaapl64[/COLOR]


// ??

C:\Users\<your user name>\AppData\Local\Temp\\cpuz138\[COLOR=#ff0000]cpuz138_x64.sys[/COLOR]


// Microsoft

wpdupfltr
wudfwpdfs
wudfwpdmtp
hdaudaddservice

I don't think any of the above Microsoft drivers would cause troubles, so put apple driver and the other one to the list:

1. Right click on start button and click on Command prompt (Admin)
2. type verifier and hit enter
3. choose "Standard Settings" and click next
4. choose "Select driver names from the list" and click next
5. find usbaapl64 in the list and enable check button for that driver.
6. find cpuz138_x64.sys in the list and enable check button for that driver.
6. click finish and reboot PC

If any of the above 2 drivers try to cause troubles they will be reported.


At this point you can start slowly adding stuff back, that is enabling everything that clean boot disabled, as you add stuff back run quick prime95 test from time to time, that's the best way to find out what's causing troubles :)
 

My Computer

System One

  • OS
    Windows 8.1 Enterprise
Addictive Gamer said:
Ok, maybe I missed something but there are only 2 drivers that look suspicious:



Code: 
// Apple
[COLOR=#ff0000]
usbaapl64[/COLOR]


// ??

C:\Users\<your user name>\AppData\Local\Temp\\cpuz138\[COLOR=#ff0000]cpuz138_x64.sys[/COLOR]


// Microsoft

wpdupfltr
wudfwpdfs
wudfwpdmtp
hdaudaddservice

I don't think any of the above Microsoft drivers would cause troubles, so put apple driver and the other one to the list:

1. Right click on start button and click on Command prompt (Admin)
2. type verifier and hit enter
3. choose "Standard Settings" and click next
4. choose "Select driver names from the list" and click next
5. find usbaapl64 in the list and enable check button for that driver.
6. find cpuz138_x64.sys in the list and enable check button for that driver.
6. click finish and reboot PC

If any of the above 2 drivers try to cause troubles they will be reported.


At this point you can start slowly adding stuff back, that is enabling everything that clean boot disabled, as you add stuff back run quick prime95 test from time to time, that's the best way to find out what's causing troubles :)
Click to expand...

usbaapl64 able to add in the list but cpuz138 unable to find in the list, even I look into the driver file also not in there.
But my PC now not getting any BSOD when I play dota2 and run prime95 :D.

Thanks you so much Addictive Gamer :thumb:
 

My Computer

System One

  • OS
    window 8.1
    Computer type
    PC/Desktop
    CPU
    Intel i5 3570
    Motherboard
    gigabyte z77m-d3h
    Memory
    Corsair 8gb
    Graphics Card(s)
    Radeon HD7850
Hi again,

Problem still arise when I try playing game. Could it be graphic card driver or graphic card problem? Please help
Attached with latest dmp file.
View attachment 67440
 

My Computer

System One

  • OS
    window 8.1
    Computer type
    PC/Desktop
    CPU
    Intel i5 3570
    Motherboard
    gigabyte z77m-d3h
    Memory
    Corsair 8gb
    Graphics Card(s)
    Radeon HD7850
You must log in or register to reply here.
Back
Top