Question
263 views

BugCheck 3B on Intel NUC w/Windows 7

karatpie asked on

I'm getting a random BugCheck on a newly installed Windows 7 OS on my Intel NUC.

Verified the latest Intel video drivers for this model of NUC are installed.

BugCheck 3B, {c0000094, fffff880041d5cfa, fffff88008731040, 0}

*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Page 1c9bc1 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : igdkmd64.sys ( igdkmd64+1b3cfa )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000094, Exception code that caused the bugcheck
Arg2: fffff880041d5cfa, Address of the instruction which caused the bugcheck
Arg3: fffff88008731040, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
igdkmd64+1b3cfa
fffff880`041d5cfa f7f1            div     eax,ecx

CONTEXT:  fffff88008731040 -- (.cxr 0xfffff88008731040;r)
rax=0000000000000000 rbx=fffffa8007b62c60 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80090e72f0 rdi=fffffa8007b89c80
rip=fffff880041d5cfa rsp=fffff88008731a28 rbp=0000000000000000
 r8=0000000000000000  r9=000000000003d090 r10=0000000000000000
r11=0000000000000000 r12=00000000000001c2 r13=fffffa8007b62c60
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
igdkmd64+0x1b3cfa:
fffff880`041d5cfa f7f1            div     eax,ecx
Last set context:
rax=0000000000000000 rbx=fffffa8007b62c60 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa80090e72f0 rdi=fffffa8007b89c80
rip=fffff880041d5cfa rsp=fffff88008731a28 rbp=0000000000000000
 r8=0000000000000000  r9=000000000003d090 r10=0000000000000000
r11=0000000000000000 r12=00000000000001c2 r13=fffffa8007b62c60
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
igdkmd64+0x1b3cfa:
fffff880`041d5cfa f7f1            div     eax,ecx
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff880041d8031 to fffff880041d5cfa

STACK_TEXT:  
fffff880`08731a28 fffff880`041d8031 : fffff880`00000000 00000000`0000000c fffffa80`075a1000 fffff880`040aebf6 : igdkmd64+0x1b3cfa
fffff880`08731a30 fffff880`041d8f24 : fffffa80`0ad70400 00000000`00000801 00000000`00000000 fffff880`041d7cc3 : igdkmd64+0x1b6031
fffff880`08731a60 fffff880`041d7044 : fffffa80`07b89c80 00000000`00000000 00000000`00000002 00000000`00000000 : igdkmd64+0x1b6f24
fffff880`08731ac0 fffff880`041d695c : 00000000`00000000 00000000`0000000b fffffa80`090e72f0 fffffa80`0672d5d0 : igdkmd64+0x1b5044
fffff880`08731b50 fffff880`04189470 : fffffa80`0672d5d0 00000000`0000000b fffffa80`0ab046a0 fffff880`041bb76e : igdkmd64+0x1b495c
fffff880`08731b80 fffff880`0417106d : fffffa80`0ab046a0 00000000`030e0300 fffffa80`07b99c30 fffffa80`07bd6010 : igdkmd64+0x167470
fffff880`08731bd0 fffff880`0416fdee : 00000000`00000060 00000000`00000000 00000000`0000007f fffffa80`07b99000 : igdkmd64+0x14f06d
fffff880`08731d80 fffff880`0416e878 : fffffa80`07bd6010 fffff880`08732310 00000000`00000000 fffffa80`06f8a8f0 : igdkmd64+0x14ddee
fffff880`08731f50 fffff880`041719d1 : fffff880`08732310 fffffa80`07dc6290 fffffa80`06f90990 fffffa80`07bd6010 : igdkmd64+0x14c878
fffff880`08731fa0 fffff880`0419db4e : fffffa80`0acc83b0 fffffa80`0acc8300 00000000`030e0300 fffffa80`07b99000 : igdkmd64+0x14f9d1
fffff880`08731fd0 fffff880`0419e06a : fffffa80`07b9aa10 fffffa80`07bd6010 fffff880`08732200 00000000`00000000 : igdkmd64+0x17bb4e
fffff880`08732010 fffff880`0419c5ea : 00000000`00000000 fffff880`08732259 fffff880`087321d0 fffffa80`07df8958 : igdkmd64+0x17c06a
fffff880`08732050 fffff880`0406d2cd : fffff880`087321d0 fffff880`08732259 00000000`030e0300 fffffa80`07b9a010 : igdkmd64+0x17a5ea
fffff880`08732170 fffff880`0403c3d5 : fffffa80`07b9a010 fffff800`02e910a3 00000000`00000000 fffff880`03ee91f0 : igdkmd64+0x4b2cd
fffff880`087321a0 fffff880`0403bbb6 : fffffa80`075a1000 fffff880`030e0300 00000000`00000000 fffffa80`07b9a010 : igdkmd64+0x1a3d5
fffff880`087322c0 fffff880`03fb54ed : fffffa80`07dc6290 fffffa80`07dc6290 00000000`ffffffff fffff880`ffffffff : igdkmd64+0x19bb6
fffff880`087322f0 fffff880`03fb07ec : 00000000`00000000 fffffa80`07dc6290 00000000`00000000 00000000`00000000 : dxgkrnl!DXGMONITOR::_QueryDriverRecommendMonitorModes+0x179
fffff880`08732350 fffff880`03fa7c39 : fffffa80`07dc6290 fffffa80`ffffff04 00000000`030e0300 00000000`0000000a : dxgkrnl!DXGMONITOR::_InitializeMonitor+0x1e0
fffff880`087323a0 fffff880`03fa72a9 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgkrnl!MONITOR_MGR::_CreateSimulatedMonitor+0x151
fffff880`08732400 fffff880`03fa4072 : 00000000`00000005 00000000`00000005 00000000`030e0300 fffffa80`07df88b0 : dxgkrnl!MONITOR_MGR::_HandleCreateSimulatedMonitor+0x329
fffff880`08732470 fffff880`03f43286 : 00000000`00000000 fffffa80`07dc9001 00000000`fffffd08 fffff880`087326cc : dxgkrnl!MonitorCreateSimulatedMonitor+0x1be
fffff880`087324d0 fffff880`03f43a81 : fffff880`087326c0 00000000`00000000 00000000`00000005 00000016`7ff55e82 : dxgkrnl!DisplayConfigHelperCreateSimulateMonitor+0x1e6
fffff880`08732550 fffff880`03f442ea : fffff880`08732600 fffff880`087326e0 fffffa01`00000004 fffffa80`07dc9000 : dxgkrnl!DisplayConfigHandleMonitorInvalidation+0x235
fffff880`087325c0 fffff880`03f450f4 : 00000000`fffff83e 00000000`00006e52 00000000`00000000 00000000`00000000 : dxgkrnl!HandleMonitorDepartureCase+0x42a
fffff880`08732690 fffff960`001d6df6 : fffff900`c1b43c20 fffff8a0`181ff7b0 00000000`00000002 fffff900`c1a233b0 : dxgkrnl!DxgkSimulateMonitorsIfNecessary+0x98
fffff880`08732790 fffff960`0016ecdb : 00000000`00000000 fffff880`08732b60 fffff8a0`ffffbf0d fffff8a0`181ff7b0 : win32k!DrvProcessMonitorEventCallback+0xe2
fffff880`08732800 fffff960`0006506c : fffffa80`0ad119f0 fffffa80`0ad119f0 fffff880`08732b60 00000000`00000000 : win32k!VideoPortCalloutThread+0x1fb
fffff880`08732a80 fffff960`000e619a : fffffa80`00000004 fffff880`031f59a0 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x4c
fffff880`08732ab0 fffff800`02ec0e53 : fffffa80`0ad119f0 00000000`00000004 000007ff`fffa6000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`08732ae0 000007fe`fcb31eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`033cf948 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fcb31eea


FOLLOWUP_IP: 
igdkmd64+1b3cfa
fffff880`041d5cfa f7f1            div     eax,ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd64+1b3cfa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5338fa92

STACK_COMMAND:  .cxr 0xfffff88008731040 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_igdkmd64+1b3cfa

BUCKET_ID:  X64_0x3B_igdkmd64+1b3cfa

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_igdkmd64+1b3cfa

FAILURE_ID_HASH:  {25da8cdb-48ff-77b2-53eb-1577aff8a252}

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

1 person had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on
Hi,

In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

If you don't know where .DMP files are located, here's how to get to them:

1. Navigate to the %systemroot%\Minidump folder.

2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

If you are going to use Onedrive but don't know how to upload to it, please visit the following:

Upload photos and files to Onedrive.

Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick
Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress