BSOD playing a game ntoskrnl.exe

Hi, I have had my new computer since June, It is a new Haswell one and I use the integrated graphics. Over the last 3 months there has been a few random crashes but not many, it has performed well but the graphics driver sometimes crashes and when it does it says its for windows 8 not windows 7. Today it's been on since about 9 so quite a long time then just at 10 to 5 it BSOD and I went into the BIOS and looked at the temps and it was 30 degrees system and 50 degrees CPU. I am not sure what caused the BSOD and would like you guys to have a look for me.

Thanks =)

ascomputers said:

Have you checked your RAM?

No, Could you give me a guide on how to check it please?
Thanks. It just happened again, it first happened on 28th now today on the 2nd its happened again been fine last 4 days, exact same error just when doing random stuff.

Update: Ran driver verifier for all drivers and it kept crashing on startup so I went in safe mode and turned it off. Attached are the 2 minidump files I got.

Thanks again guys.

Hello Andrew89898 and welcome to the Forums,

Your first rar is incomplete, please rerun the SF Diagnostic Tool again and make sure that MSINFO, DXDIAG and Host.txt are included this time.
More info BSoD Posting Instructions.

----------

Your initial dump file points to this;

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80096d3028, be000000, 100110a}

Probably caused by : GenuineIntel

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

Usual cause: Fatal hardware error.
More info Bug check 0x124_0.

----------

If we dig deeper in the dump file we see that the following driver is the cause of your BSoD;

Code:

2: kd> dps fffff880063b0000 fffff880063b6000
fffff880`063b44e0  fffffa80`0a086a90
fffff880`063b44e8  fffffa80`0a016800
fffff880`063b44f0  fffff880`063b4550
fffff880`063b44f8  fffff880`04f1fe92Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0xbae92

Driver reference table: igdkmd64.sys.

----------

Since I do not have the MSINFO and DXDiag files, I do not have all the information required to pinpoint the integrated chipset, so I will have to advice you to update it using the Driver Update Utility - Graphics.
After doing this, please completely remove the old driver by running a scan with Driver Sweeper.

----------

Now when we look at the dump files created after running Driver Verifier, we see this;

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {0, 0, 0, 0}

Probably caused by : tcpipreg.sys ( tcpipreg!InterfaceAddressRegKeyChangeHandler+109 )

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

It points to tcpipreg.sys, which is a Windows driver that shouldn't fail on it's own.

If we look at the stack, we see this;

Code:

STACK_TEXT:  
fffff880`035e7488 fffff800`0356a4ec : 00000000`000000c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`035e7490 fffff800`0356af2b : 00000000`00000293 fffff800`0310784c 00000000`00000003 fffff800`03107a90 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`035e74d0 fffff800`0357bba8 : 00000000`6547654c 00000000`00000080 00000000`00000010 fffff880`0000007f : nt!ExAllocatePoolSanityChecks+0xcb
fffff880`035e7510 fffff800`0357be17 : 00000000`00000000 00000000`00000000 fffff980`6547654c fffff980`1f03efec : nt!VeAllocatePoolWithTagPriority+0x88
fffff880`035e7580 fffff880`0673d5a1 : 00000000`00000000 00000000`00000000 fffff980`1f03efd0 fffff800`0357713c : nt!VerifierExAllocatePoolWithTagPriority+0x17
fffff880`035e75c0 fffff880`0673c7bb : fffff880`06743c20 fffff980`1f03efd0 fffff980`1b8aaf90 fffff980`1f03efd0 : tcpipreg!InterfaceAddressRegKeyChangeHandler+0x109
fffff880`035e76f0 fffff880`0673ba59 : fffff880`00000001 00000000`00000103 fffff980`1b8aaf70 00000000`00000001 : tcpipreg!TcpipRegQueryAndUpdateKeyValue+0x363
fffff880`035e7780 fffff880`01991754 : fffff880`06741a60 00000000`00000004 00000000`00000000 00000000`00010202 : tcpipreg!TcpipRegStartRegistryKeyNotification+0xbd
fffff880`035e77d0 fffff880`0673c293 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`06747073 : NETIO!RtlInvokeStartRoutines+0x34
fffff880`035e7810 fffff800`034c7787 : 00000000`00000006 fffffa80`0bfc87b0 fffffa80`0bfba000 00000000`00000001 : tcpipreg!DriverEntry+0x257
fffff880`035e7860 fffff800`034c7b85 : 00000000`00000010 00000000`00000000 00000000`00000010 00000000`00010206 : nt!IopLoadDriver+0xa07
fffff880`035e7b30 fffff800`030e6261 : fffff880`00000000 ffffffff`800006a4 fffff800`034c7b30 fffffa80`06d38660 : nt!IopLoadUnloadDriver+0x55
fffff880`035e7b70 fffff800`0337abae : 00000000`00000000 fffffa80`06d38660 00000000`00000080 fffffa80`06caf300 : nt!ExpWorkerThread+0x111
fffff880`035e7c00 fffff800`030cd8c6 : fffff880`03365180 fffffa80`06d38660 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035e7c40 00000000`00000000 : fffff880`035e8000 fffff880`035e2000 fffff880`035e6ef0 00000000`00000000 : nt!KxStartSystemThread+0x16

It again points to tcpipreg.sys, but this time also to NETIO.sys, which is yet another Windows driver.

----------

Let's look at the other dump file you got from Driver Verifier;

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80096b7028, be000000, 100110a}

Probably caused by : GenuineIntel

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

Hmm, another hardware error..

Code:

0: kd> dps fffff80000b97000 fffff80000b9d000
fffff800`00b9bc00  fffff800`00b9bed0
fffff800`00b9bc08  00000000`00000004
fffff800`00b9bc10  00000000`00000000
fffff800`00b9bc18  fffffa80`07349900
fffff800`00b9bc20  fffff880`04dc8f70Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x138f70

Code:

fffff800`00b9c840  00000000`00000000
fffff800`00b9c848  00000000`0000000f
fffff800`00b9c850  00000000`00000000
fffff800`00b9c858  ffffd89e`375aa5af
fffff800`00b9c860  fffff880`048e5dc0Unable to load image iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
 iusb3xhc+0x6adc0

Driver reference table: iusb3xhc.sys.

Two failing drives this time; the integrated graphics chip driver, and the USB port driver.

----------

I would advice you to update the USB driver from here. After doing this please completely remove the old driver by running a scan with Driver Sweeper.

----------

After updating both drivers, please upload the requested files and follow ascomputers his advice on your RAM.


Good luck and keep us posted,
Nommy

Hello Andrew89898,

EDIT!

It seems that you have posted a link to your machine's page while I was posting, and so I have missed it in my initial post. Please use the driver links in this post instead of my other post as they are more accurate.

----------

Code:

0: kd> lmvm igdkmd64
start             end                 module name
fffff880`04c90000 fffff880`050c9fe0   igdkmd64   (deferred)             
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Wed May 08 02:15:19 2013 (51899917)
    CheckSum:         00442E25
    ImageSize:        00439FE0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

0: kd> lmvm iusb3xhc
start             end                 module name
fffff880`0487b000 fffff880`0493e000   iusb3xhc   (deferred)             
    Image path: iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Fri Dec 21 15:40:49 2012 (50D474F1)
    CheckSum:         000C0A88
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As you can see, the conclusion of my previous post was right; both drivers are outdated.

You can find both drivers here.
Fill in the correct OS information before downloading anything!
Attachment 288251

Again, after installing them do a run with Driver Sweeper as shown in my previous post.

----------

To check your RAM for issues you could use the following hardware test;
Please run Memtest86+ to test your RAM for issues.

   Tip

Let Memtest run for at least 10 passes and preferably overnight as it may take very long to complete.
Especially read part three of the tutorial, which explains you to test each RAM stick in all DIMM slots to filter out failing slots.

Arc said:

Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Good luck and keep us posted,
Nommy

Hello andrew89898,

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80096b7028, be000000, 100110a}

Probably caused by : GenuineIntel

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

More info Bug Check 0x124_0
Usual causes: failing hardware, failing drivers.

----------

Code:

2: 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: fffffa80096b7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, 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:  eurotrucks2.ex

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0336da58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

As we can see, the first parameter of the stop code is 0x0, caused by a Machine Check Exception. This usually indicates a hardware error.

----------

Please preform the following hardware tests in order to rule out faulty hardware;
Please run Memtest86+ to test your RAM for issues.

   Tip

Let Memtest run for at least 10 passes and preferably overnight as it may take very long to complete.
Especially read part three of the tutorial, which explains you to test each RAM stick in all DIMM slots to filter out failing slots.

Arc said:

Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

----------

Stress test the graphics card using Furmark GPU Stress Test.

   Information

During the test please check the screen for artifacts.
The purpose of this test is to make your machine crash and create dump files so that we can pinpoint the cause of your problem.

   Tip

Please run Furmark once when your machine has just started, and once again when your machine has been active for several hours.

----------

Stress test the CPU with Prime95.
Under Advanced, please check "Round off checking".
Please choose the "In-place large TFF's test.

   Tip

Be sure to keep an eye on your temperatures when running these tests, especially the Large FFTs. We recommend the free utility Speedfan.

   Note

As with all hardware tests, Prime95 is not fail-safe. If the test passes for 2 hours with no errors, it is most likely to be stable. Unfortunately, it sometimes makes mistakes and gives a clean bill of health to faulty hardware.

   Note

When Prime95 has crashed your system, please continue by following the BSOD posting instructions.

----------

   Warning

Do not do this step if your hard drive is an SSD!

Please scan your hard drive with Chkdsk.

1. Click on the
2. Open an Elevated Command Prompt.
3. Type the following;
   chkdsk C: /F
   Replace C: with the letter of your hard drive.
4. You will get a message that your drive is in use and that Chkdsk will be run at start up.
5. Please exit the command prompt, close and save any open programs and restart your machine. Chkdsk will now scan at boot.

   Warning

Do not attempt to cancel or stop the scan, this might result in a loss in data and could render your Windows unusable!

----------

Please also provide a screenshot of Speccy so that we can see your system temps;
Please download Speccy.

1. Download and install Speccy.
2. Open Speccy. Click on the Summary tab.
3. Click on File and then on Save Snapshot.
4. Set the save location as your desktop and upload the file by following this tutorial.
   Please upload a snapshot of your machine in the following situations;
   
   • Idle, after startup.
   • After being used for a few hours.
   • After straining the GPU by, for example, playing some High Res games.
   
   

----------

Code:

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
  Vendor                        American Megatrends Inc.
  BIOS Version                  F4
  BIOS Starting Address Segment f000
  BIOS Release Date             05/16/2013
  BIOS ROM Size                 800000

Your BIOS is outdated, please update it to the F6 version from here.
Attachment 296171
----------

If no errors where found by the hardware tests, and updating your BIOS didn't solve it, please enable Driver Verifier to pinpoint a failing driver.
Read before continuing How to use Driver Verifier.

Arc said:

   Information

Why Driver Verifier:
It puts a stress on the drivers, and so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Please use the following settings;

YoYo155 said:

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 everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
7. Select "Finish" on the next page.

Good luck and keep us posted,
Nommy