BSOD Windows Home Premium 64bit

Page 1 of 2 12 LastLast

  1. Posts : 13
    Windows 7 Home Premium 64bit
       #1

    BSOD Windows Home Premium 64bit


    I've been getting a blue screen lately and I'm not 100% sure why. Any help would be greatly appreciated. Thanks a lot!

    OS: Windows Home Premium 64bit Retail
    Fresh install. The system is near brand new. Maybe only 2 months old.
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    While Im looking at your .dmp files, please fill in your system specs...
      My Computer


  3. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Updated. Thank you.
      My Computer


  4. Posts : 11,840
    64-bit Windows 8.1 Pro
       #4

    The dmp(s) point to ntkrnlmp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable driver verifier to help pinpoint the faulting driver..

    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

    Your Perfmon report is showing a system driver that is not installed... be sure to run Windows Update to insure that this is installed..

    Code:
    A driver has not been installed for this device preventing it from working properly.
    Details:	The device driver for Marvell 91xx Config ATA Device has not been installed. This device will not be available until the correct device driver is installed.
    Resolution:	1. Try installing the drivers using Windows Update.
    2. Install the drivers that are on the installation media that came with the device.
    3. Check with the manufacturer for an updated driver.
    For trouble shooting purposes, uninstall your current Anti Virus and install MSE ... once we get a stable system, you can reinstall it..

    Microsoft Security Essentials

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002ed71bc}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002e7ee59}
    
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    
    Followup: MachineOwner
    ---------
    
    MODULE_NAME: NETIO
    
    IMAGE_NAME:  NETIO.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bbe946f
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
    
    BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a
    
    Followup: MachineOwner
    ---------
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002ed01bc}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002e861bc}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002e801df}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002e8d1bc}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    These drivers are out of date and should be updated, or uninstall the associated program

    Code:
    fffff880`10beb000 fffff880`10bf8000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0) ... CD-ROM Class Filter Driver by Gear Software ... GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering
    fffff880`010cc000 fffff880`011f2000   sptd     sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632) ... Uninstall as suggested...
    fffff880`03ffd000 fffff880`03fffa00   wacomvhid wacomvhid.sys Mon Sep 21 19:29:14 2009 (4AB80C4A) ... Wacom(tablet) HID filter ... Wacom Hardware Drivers
      My Computer


  5. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    Ok. I did that and it wouldn't even boot up. It was get a blue screen before even loading windows. Each time it would say it was fileinfo.sys, IRQL_NOT_LESS_OR_EQUAL, or that it was IO Manager. I'm in safe mode right now. I'm not sure what I should be doing now. Any help?

    Also, I update Windows all the time. I did last night actually. I'm not sure why it would say I have files missing.
      My Computer


  6. Posts : 11,840
    64-bit Windows 8.1 Pro
       #6

    If the crash happened after starting driver verifier, then that is what we want... upload the new .dmp files and we'll go from there... Did you follow the other suggestions?
      My Computer


  7. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    They happened after, yes. I haven't tried the other things yet. I'll do them as you check out the new dump. Thanks again.
      My Computer


  8. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    Here's the new dump file. I just ran the dump .exe thing again. Let me know if that's what you need.
      My Computer


  9. Posts : 11,840
    64-bit Windows 8.1 Pro
       #9

    Its still showing the same errors... Please continue with driver verifier and follow the previous suggestions ( this part is important! )

    PS.. delete the contents of c/windows/minidump so you dont upload any old .dmp files..
      My Computer


  10. Posts : 13
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    Ok. Every time I try to boot I get:
    "The IO Manager has detected a violation by a driver that is being verified."

    It doesn't name a driver or anything though. What should I be doing about this?
    I already installed Daemon Tools and I can't run updates or install anything in safe mode.
      My Computer


 
Page 1 of 2 12 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 21:29.
Find Us