Share via

BSODs on HP Elitedesk 800 G1

Anonymous
2014-06-06T11:11:36+00:00

Hi there,

My company has purchased some HP Elitedesk 800 G1 desktop machines for development use.  We have installed a manual build of Windows 7 x64 Enterprise N on the machines, and some additional software, plus all the appropriate drivers from HP's website.  However, two of the machines keep crashing with BSODs.  This was a particular problem during Windows Updates following initial installation.

The BSOD erros have pointed to either memory or drivers as the cause of the issue, but I'd be really grateful if you could look at the minidumps and see what you think.  You can download a zip file containing the minidumps, msinfo32 output and hardware specs here: 

https://drive.google.com/file/d/0B2i0lcneVsLkd2hRVGVDLUFUS0k/edit?usp=sharing

Please let me know if you would like any further information.

Best regards

Baskii

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2014-06-19T15:19:37+00:00

    BugCheck C1, {fffff98020628d10, fffff98020628080, 7b42f0, 23}

    Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for VBoxNetFlt.sys

    *** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys

    Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+132 )

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    NETIO!NetioDereferenceNetBufferListChain+132

    fffff880`01913872 4c8bb42490000000 mov     r14,qword ptr [rsp+90h]

    SYMBOL_STACK_INDEX:  6

    SYMBOL_NAME:  NETIO!NetioDereferenceNetBufferListChain+132

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: NETIO

    IMAGE_NAME:  NETIO.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  5294760d

    FAILURE_BUCKET_ID:  X64_0xC1_23_VRF_NETIO!NetioDereferenceNetBufferListChain+132

    BUCKET_ID:  X64_0xC1_23_VRF_NETIO!NetioDereferenceNetBufferListChain+132

    Followup: MachineOwner


    I would remove Virtual box.

    fffff880052fb000 fffff88005326000   VBoxNetFlt T (no symbols)          

        Loaded symbol image file: VBoxNetFlt.sys

        Image path: \SystemRoot\system32\DRIVERS*VBoxNetFlt.sys*

        Image name: VBoxNetFlt.sys

        Timestamp:        Fri May 16 08:01:15 2014 (5375FE0B)

        CheckSum:         0002AE3F

        ImageSize:        0002B000

        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    =====================================

    Use !analyze -v to get detailed debugging information.

    BugCheck C1, {fffff98012336cd0, fffff98012336018, 174330, 23}

    Unable to load image \SystemRoot\system32\DRIVERS\e1d62x64.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for e1d62x64.sys

    *** ERROR: Module load completed but symbols could not be loaded for e1d62x64.sys

    Probably caused by : e1d62x64.sys ( e1d62x64+21124 )

    Followup: MachineOwner

    Driver Description: Intel Gigabit Adapter NDIS 6.x driver

    Update or rollback at the HP Link below.

    ========================================

    0: kd> !sysinfo machineid

    Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=2856]

    BiosMajorRelease = 2

    BiosMinorRelease = 21

    BiosVendor = Hewlett-Packard

    BiosVersion = L01 v02.21

    BiosReleaseDate = 12/17/2013

    SystemManufacturer = Hewlett-Packard

    SystemProductName = HP EliteDesk 800 G1 SFF

    SystemFamily = 103C_53307F G=D

    SystemSKU = H5T99ET#ABU

    BaseBoardManufacturer = Hewlett-Packard

    BaseBoardProduct = 1998

    HP EliteDesk 800 G1 Small Form Factor PC

    http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_bd9b6997fbc7fc515f4cf4626f5c8d01=wsrp-navigationalState%3DswEnvOID%253D4059%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.tpst=bd9b6997fbc7fc515f4cf4626f5c8d01&sp4ts.oid=5387477&ac.admitted=1403189915084.876444892.492883150

    1 person found this answer helpful.
    0 comments No comments

8 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-06-10T08:03:22+00:00

    Many thanks for your reply.  I have run driver verifier, and I found that when I selected all of the non-Microsoft drivers, Windows failed to boot - it crashed and restarted while showing the Windows splash screen.

    I was able to boot into safe mode, so I re-ran driver verifier, several times, selecting one or two non-Microsoft drivers each time.  The first time Windows failed to boot, I had selected some Intel iastor drivers, so it's possible that they are causing the issue.

    The minidump files generated during the driver verifier tests are here: https://drive.google.com/file/d/0B2i0lcneVsLkOXdfQnBydkZORnM/edit?usp=sharing

    Please let me know if they help to pin the issue down.

    Many thanks

    Baskii

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2014-06-06T11:18:36+00:00

    These crashes were related to memory corruption (probably caused by a driver). Please run these tests to verify your memory and find which driver is causing the problem.


    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    Since it is more likely to be a driver please run verifier first.

    1-Driver verifier (for complete directions see our wiki here)


    If verifier does not find the issue we can move on to this.

    **2-Memtest. (**You can read more about running memtest here)


    If you cannot boot after enabling verifier reboot into safe mode

    In Vista & win & (F8)

    In win 8**http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-windows-8-the-easy-way/**


    Co-Authored by  JMH3143

    .

    0 comments No comments