Driver Verifier BSoD on checking BIOS, 0x000000C4

Levyathyn · 30 Oct 2012

I need help with this, can't quite figure out the problem. It's really... odd. In addition to other minor system problems in this brand new build, I have a somewhat recurring driver crash related to the common Driver Verifier problem. I can't find the driver myself, so I don't know which one or ones it may be. In addition, the crash most frequently occurs when using AIDA64/Everest to check my motherboard's specs. I can view most of it, including the hardware set-up, but clicking 'BIOS' or 'ACPI' to check those parts causes an instant crash. I don't know if this is normal.

I'm not so much versed in drivers or Driver Verifier, so before I did anything I wanted to come here. Also, I tried to upload my SF data correctly, let me know if you need anything else, or if I made a mistake. Thanks for taking a look.

Arc · 31 Oct 2012

First, Disable Driver Verifier.
Driver Verifier - Enable and Disable

Then uninstall AIDA64 Extreme Edition

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {83, 99bc018, 2c, 99bc}

*** WARNING: Unable to verify timestamp for kerneld.x64
*** ERROR: Module load completed but symbols could not be loaded for kerneld.x64
Probably caused by : kerneld.x64 ( kerneld+218d )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000083, MmMapIoSpace called to map, but the caller hasn't locked down the MDL pages.
Arg2: 00000000099bc018, Starting physical address to map.
Arg3: 000000000000002c, Number of bytes to map.
Arg4: 00000000000099bc, The first page frame number that isn't locked down.

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


BUGCHECK_STR:  0xc4_83

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  aida64.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000356d3dc to fffff800030e6fc0

STACK_TEXT:  
fffff880`04a2c3b8 fffff800`0356d3dc : 00000000`000000c4 00000000`00000083 00000000`099bc018 00000000`0000002c : nt!KeBugCheckEx
fffff880`04a2c3c0 fffff800`0356dc53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`04a2c400 fffff800`0357e9a6 : 00000000`099bc018 00000000`00000000 00000000`00000002 00000000`00000000 : nt!MmCheckMapIoSpace+0xe3
fffff880`04a2c450 fffff880`0848418d : 00000000`099bc018 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierMmMapIoSpace+0x46
fffff880`04a2c490 00000000`099bc018 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kerneld+0x218d
fffff880`04a2c498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x99bc018


STACK_COMMAND:  kb

FOLLOWUP_IP: 
kerneld+218d
fffff880`0848418d ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  kerneld+218d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kerneld

IMAGE_NAME:  kerneld.x64

DEBUG_FLR_IMAGE_TIMESTAMP:  508d112b

FAILURE_BUCKET_ID:  X64_0xc4_83_VRF_kerneld+218d

BUCKET_ID:  X64_0xc4_83_VRF_kerneld+218d

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

1: kd> lmvm kerneld
start             end                 module name
fffff880`08482000 fffff880`0848d000   kerneld  T (no symbols)           
    Loaded symbol image file: kerneld.x64
    Image path: \??\C:\Program Files (x86)\AIDA64 Extreme\kerneld.x64
    Image name: kerneld.x64
    Timestamp:        Sun Oct 28 16:34:11 2012 (508D112B)
    CheckSum:         0000AF16
    ImageSize:        0000B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Let us know the results.

Levyathyn · 31 Oct 2012

Well, that alone seemed to have fixed most of my problems. I never expected Driver Verifier to be behind so much trouble, though. Game slowdown, IE9 crashes, Boot CD failures... I can even get DriverAgent to work. It's crazy.

Well, thank you for your help. It's a load off my mind that, at least for now, that post seems to have covered everything. I'll be honest, I expected a lot worse. ^_^

Arc · 01 Nov 2012

Was there a reason that you enabled driver verifier? It is risky, if it is not properly guided by any experienced person.

Update the thread with the latest situation .... is there any issue remaining or not.

Have you uninstalled AIDA64 Extreme?

Levyathyn · 01 Nov 2012

Arc said:

Was there a reason that you enabled driver verifier? It is risky, if it is not properly guided by any experienced person.

Update the thread with the latest situation .... is there any issue remaining or not.

Have you uninstalled AIDA64 Extreme?

Completely uninstalled.

As for Driver Verifier, I've never used it before, and it was enabled by default, so a lot of my various problems have been there since the beginning of this computer a month or so ago. That's why I was sort of touchy about disabling, or even how to.

I've been stressing everything a bit, and there seems to be no problem remaining. I had cleared up a few issues, like something with my .Net 4 framework, and some problem with my drivers, but since I accidentally solved everything else before I made this thread, I'm good. Thank you again.