Massive amounts of BSODs on boot, multiple errors; BE, 18, 7E, 0A

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 7 Professional x64
       #1

    Massive amounts of BSODs on boot, multiple errors; BE, 18, 7E, 0A


    Hello Windows 7 Forum,

    I work at the IT department of a school where we have around 600 PC's that need to be maintained. Most things break by the kids and most is fixed my replacing, or simply imaging said computers again.
    However, after having switched over from Windows XP to Windows 7 we've been having masses of BSODs when loading Windows. Not just the normal PC's, not just linked to one type (although pretty much everything is from HP). But it keeps happening.

    The most common errors that we've been able to discover are:
    0x00000018, 0x0000000A, 0x0000007E, 0x000000BE
    After having researched these things, they all turned out to have something to do with drivers, not only that, but when trying to boot into safe mode the PC's would all freeze at "classpnp.sys" and sometimes reboot shortly after.

    Our current solution is simply putting a new Windows 7 image over the computer and it'll work another day or two. It's great that it works again then, but we spend too much time on it.

    As thus I come here, I want to avoid this problem. It can't possibly be the hardware, there are too many different kinds of computers for it to be that. I'm quite sure the problem is somewhere originating from the drivers we install, but then he question comes as to what ruins the drivers? Not to mention that there are also different drivers for the different kinds of PC's.

    If I'm lacking any information please tell me. Thank you for your time.
      My Computer


  2. Posts : 306
    Windows 7 Ultimate x64
       #2

    Hello Alpha, welcome to SevenForums! :)

    This is going to be relatively tricky for us to help you with since it's on such a massive scale of computers. Is there any possible way you can grab a few dump files from any computer? Regardless, would it be possible for you to get one of the school PCs to boot into safe mode? If you can, see if it stops at CLASSPNP.SYS when it's loading all of the drivers.

    Since you've mentioned ever since your school moved over to Windows 7, the issues started happening, I doubt it's a massive hardware related issue, but probably a bad image that you guys are using to install. Have you guys tried a BRAND new image / disc to see if its the current that is at fault?
      My Computer


  3. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #3

    It indeed locks up on classpnp.sys when booting in safe mode, I should have been more specific, my bad.

    Otherwise, I'm not entirely sure how to make/get a minidump or do anything that's described in the instructions topic seeing I don't get into windows at all. I suppose I could get the HDD of the BSODing computer, I shall do that now.

    As further information, I've also had a few computers, 4 so far, where the date reset to 2099. This is an issue that has come over the last week while this issue has been going for at least 3 months now. I'm not sure if this is related, but I figure any additional information is helpful.

    I'll post again once I retrieved the dump file.
      My Computer


  4. Posts : 306
    Windows 7 Ultimate x64
       #4

    Sounds great :)

    The date issue you mentioned, does the time switch as well? Those can just be a dying CMOS battery, simple and cheap fix.
      My Computer


  5. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #5

    Great, the forum just ate the reply I put in Quick reply, let's do this again, but shorter.

    I was able to connect the HDD to my computer and had to turn it online, after that I was able to locate the MEMORY.DMP file, but it's a whopping 150mb. I'm quite sure that I shouldn't upload that much. I saw that I could adjust the memory dump file size to 256kb, but alas, I can't boot into windows to change this. Is there some configuration I could edit for it to change to that?

    As for the date thing, the time was indeed off on 3 out of 4, I'm guessing the 4th got lucky with being turned back on at the right time or something. Either way, if it's indeed just the CMOS battery the solution would be nice. The sudden 4 in one week is what concerned me though. I thought it might have been related.

    Anyway, my working day has come to an end, I'll return tomorrow, with hopefully a smaller memory dump, or a way to get the small out of the bigger dump.
      My Computer


  6. Posts : 306
    Windows 7 Ultimate x64
       #6

    The reasoning for it being that large is it is likely a full memory dump rather than a small, it contains much more information, thus the increase in size.

    Sounds good man, keep us updated with any further information :)
      My Computer


  7. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #7

    Well, after a lot of hassle I found out that windows automatically saves minidumps as well. Yay for not readings things properly. After that I tried finding a program that would let me read the thing, but it redirected me to some windows thing that wouldn't let me download anything and I needed to get some subscription.
    Then I also figured that I wouldn't know what to do with said decoded minidump file anyway, seeing I already know which codes it got.

    So either way, uploaded it to dropbox, and here it is, please tell me you can figure out more than me.

    http://dl.dropbox.com/u/5181268/021612-75671-01.dmp

    EDIT: Well I finally got something through google, here's the debug report thing.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    REFERENCE_BY_POINTER (18)
    Arguments:
    Arg1: 00000000, Object type of the object whose reference count is being lowered
    Arg2: 85c81a88, Object whose reference count is being lowered
    Arg3: 00000002, Reserved
    Arg4: 89a6df88, Reserved
        The reference count of an object is illegal for the current state of the object.
        Each time a driver uses a pointer to an object the driver calls a kernel routine
        to increment the reference count of the object. When the driver is done with the
        pointer the driver calls another kernel routine to decrement the reference count.
        Drivers must match calls to the increment and decrement routines. This bugcheck
        can occur because an object's reference count goes to zero while there are still
        open handles to the object, in which case the fourth parameter indicates the number
        of opened handles. It may also occur when the object’s reference count drops below zero
        whether or not there are open handles to the object, and in that case the fourth parameter
        contains the actual value of the pointer references count.
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x18
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 8327fd22 to 832e5f2c
    
    STACK_TEXT:  
    8ac53cc8 8327fd22 00000018 00000000 85c81a88 nt!KeBugCheckEx+0x1e
    8ac53cec 8327fcd0 85c81a88 8341b477 84fd3a70 nt!ObfDereferenceObjectWithTag+0x4b
    8ac53cf4 8341b477 84fd3a70 8ac53d50 83284aab nt!ObfDereferenceObject+0xd
    8ac53d00 83284aab 85fd70b0 00000000 84fd3a70 nt!IopProcessWorkItem+0x34
    8ac53d50 8340ff64 00000001 94fb1975 00000000 nt!ExpWorkerThread+0x10d
    8ac53d90 832b8219 8328499e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ObfDereferenceObjectWithTag+4b
    8327fd22 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!ObfDereferenceObjectWithTag+4b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd753
    
    FAILURE_BUCKET_ID:  0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag+4b
    
    BUCKET_ID:  0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag+4b
    
    Followup: MachineOwner
    ---------
    Last edited by Alphasoldier; 24 Feb 2012 at 03:41.
      My Computer


  8. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #8

    More than a week has passed, has anyone gotten the chance to look at this?
    The problem still occurs on many computers.
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    Sorry your thread was lost in the mix...

    Please follow the https://www.sevenforums.com/crashes-d...tructions.html to give us the best information possible so we can give specific troubleshooting steps.

    Thank you.
      My Computer


  10. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #10

    I'm not quite sure how to follow a guide that tell me to do things on the computer when I can't even boot the computer into windows, which is the whole problem here.
    And I'm quite sure that doing all those steps on a functioning PC is not going to help.

    I already uploaded the minidump file and the added information. Is there anything else I can obtain?

    Everything is being run on a Windows 7 Enterprise x86, there's several different machines. Ones that were designed for windows 7 and others that aren't supported by HP itself anymore seeing they were made for XP, we did however at least put in the minimum required hardware in the older machines.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:49.
Find Us