BSOD ntoskrnl.exe when gaming.

Gibbsy

New member
Local time
10:23 PM
Messages
1
Hi, I have been having random BSOD problems for a while now, mainly seems to be when gaming.

When a dump file is created ntoskrnl.exe seems to come up a lot. Gpu and cpu temps all seem fine 70/54-60 approx.

I hope from the mini dump file someone point out to me any potential reasons for these BSOD.

If any other information needed please ask.

Thanks in advance.
 

My Computer My Computer

At a glance

Win 7 Ultimate 64biti7 950Corsair 12gb CMZ12GX3M3A1600C9Gainward 580 Phantom3
OS
Win 7 Ultimate 64bit
CPU
i7 950
Motherboard
Asus p6x58d-e
Memory
Corsair 12gb CMZ12GX3M3A1600C9
Graphics Card(s)
Gainward 580 Phantom3
Sound Card
Xonar DG
Monitor(s) Displays
Samsung S27B750
Hard Drives
OCZ Agility3 120gb ssd
WD 2tb
PSU
Corsair tx650
Case
Corsair 950d
Cooling
Corsair H50
Welcome

You're having a 124 bug check, go through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html step by step. It may help you with your issue.

Code:
[FONT="Lucida Console"]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800a4d68f8, 0, 0}

Probably caused by : GenuineIntel

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

4: 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: fffffa800a4d68f8, 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:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0335b6f0 fffff800`0310eca9 : fffffa80`0a4d68d0 fffffa80`09e12b50 fffff8a0`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0335bc10 fffff800`02fef557 : fffffa80`0a4d68d0 fffff800`030692d8 fffffa80`09e12b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0335bc40 fffff800`02f56935 : fffff800`030caae0 00000000`00000001 fffffa80`0a6969e0 fffffa80`09e12b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0335bc80 fffff800`02ed5641 : fffff880`010cee00 fffff800`02f56910 fffffa80`09e12b00 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0335bcb0 fffff800`03162e5a : 00000000`00000000 fffffa80`09e12b50 00000000`00000080 fffffa80`09d765f0 : nt!ExpWorkerThread+0x111
fffff880`0335bd40 fffff800`02ebcd26 : fffff880`0316a180 fffffa80`09e12b50 fffff880`031750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0335bd80 00000000`00000000 : fffff880`0335c000 fffff880`03356000 fffff880`04350740 00000000`00000000 : nt!KiStartSystemThread+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_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

4: kd> !sysinfo cpuspeed
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
4: kd> !errrec fffffa800a4d68f8
===============================================================================
Common Platform Error Record @ fffffa800a4d68f8
-------------------------------------------------------------------------------
Record Id     : 01cdd00066c56ba3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/1/2012 20:14:04 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000106a5
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : a5 06 01 00 00 08 10 04 - bd e3 98 00 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  @ fffffa800a4d6b10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800a4d6a08
Section       @ fffffa800a4d6b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 4 Bank 5)
  Status      : 0xbe00000000800400
  Address     : 0x000007feed5d8e7f
  Misc.       : 0x0000000000000000[/FONT]

Other dump file shows ntfs errors which can be caused due to antivirus program. Uninstall Avast! and use MSE during your time of troubleshooting

  1. avast! Uninstall Utility | Download aswClear for avast! Removal
Recommended antivirus program for Windows 7 based on stability compared to others:-

:warn: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

  • Click on the :orb:
  • Type CMD on Search
  • Left click and Run as Administrator
  • Type SFC /scannow
Full tutorial here:
Run Disk Check on your hard disk for file system errors and bad sectors on it:
Hope this helps for now
 

My Computer My Computer

At a glance

Windows 10 Home 64BitIntel Core i5 10400 @ 2.90GHz8.00GB Single-Channel Unknown @ 1329MHz (16-2...
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self assembled
OS
Windows 10 Home 64Bit
CPU
Intel Core i5 10400 @ 2.90GHz
Motherboard
Intel Corporation DG41WV (PROCESSOR)
Memory
8.00GB Single-Channel Unknown @ 1329MHz (16-20-20-38)
Sound Card
Realtek High Definition Audio
Monitor(s) Displays
DELL E170S
Screen Resolution
1280x1024 pixels
Hard Drives
931GB TOSHIBA DT01ACA100 (SATA)
238GB TEAM TM8PS7256G (SATA SSD)
Case
Nothing Fancy
Cooling
Fans
Keyboard
A4 Tech Co LTD
Mouse
A4 Tech Co Ltd/Logitech
Internet Speed
25 Mbps
Back
Top