Win7 x64 Ultimate, BSODs constant in last few weeks

Page 1 of 2 12 LastLast

  1. Posts : 21
    Windows 7 Ultimate x64
       #1

    Win7 x64 Ultimate, BSODs constant in last few weeks


    Howdy!
    I have had a few BSOD's lately, had not had one for a week and believed the problem solved with doing a clean install of the nvidia current video driver. However today upon booting the computer for the first time today I got a 0x050 PAGE_FAULT_IN_NONPAGED_AREA, I rebooted and everything was fine, shut down the machine and then after 4 hrs came back, turned on and got a BSOD on windows booting into the user 0x01e KMODE_EXCEPTION_NOT_HANDLED

    I am actually getting agrivated and not sure where to go from here. I have attached the zip, hopefully someone can help me out. Thank you
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hello Grunter.

    Avast is causing the BSODs here.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41790, fffffa8015a20d20, ffff, 0}
    
    *** WARNING: Unable to verify timestamp for aswSnx.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
    Probably caused by : aswSnx.SYS ( aswSnx+2eebf )
    
    Followup: MachineOwner
    ---------
    Description here: Driver Reference Table - aswSnx.SYS

    And again .....
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff8800bdb3d53, fffff880096a5c70, 0}
    
    Probably caused by : aswMonFlt.sys ( aswMonFlt+5d53 )
    
    Followup: MachineOwner
    ---------
    Description here: http://www.carrona.org/drivers/drive...=aswMonFlt.sys

    Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    Let us know the results.
      My Computer


  3. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Removed avast and when booting after the safe mode boot for removal logged in and as everything was loading got BSOD APC_INDEX_MISMATCH 0x00000001
    Ive included the files after the BSOD, I had added avast because in the past MSE let something in and I had to remove the virus, is AVG any better?
    Thanks!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  5. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Howdy!
    Thanks for your time, before I got to do this next part I got a BSOD again 0x01a MEMORY_MANEGMENT
    I have the file for this one see if it shows anything
    Thanks sooooo much for your help, I really appreciate it.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Better you take the suggestion as given earlier. Update the DV enabled crash dumps next time.
      My Computer


  7. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Will do so, upon boot at the moment its crashing the application constantly
      My Computer


  8. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #8

    Ok, I am there and followed the instructions but it only lists 2 drivers and both are Microsoft, it is not giving me a long list. Is there anything I am doing wrong?

    Ok at this time was able to get more than 2 drivers in the list but they all show as a microsoft corp.
    Also had another BSOD for ntfs.sys when trying to run this.

    I am including the dump after this BSOD and the pervious one. Tried running the driver verifier again, only get windows drivers.

    One question, would VMWare be causing these problems? Sorry I have not been able to driver verify, the list is just not pulling up as you requested
    Last edited by Grunter; 23 Jul 2013 at 19:39. Reason: New info
      My Computer


  9. Posts : 21
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Finally was able to run the verifier and get a huge list, rebooting the machine resulted in constant BSOD which would prompt into windows repair startup. Eventually got into safe mode to disable verifier and the one item that was the cause, or rather what was reported, was pdiports.sys
    Im enclosing the new files after the 2 BSOD's with the Verifier running
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    The BSOD is caused by pdiports.sys; Portrait Displays low level device driver (c:\windows\system32\drivers\pdiports.sys)
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {21f, fffff88007df6970, fffff9800512ce10, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\PdiPorts.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PdiPorts.sys
    *** ERROR: Module load completed but symbols could not be loaded for PdiPorts.sys
    Probably caused by : PdiPorts.sys ( PdiPorts+1970 )
    
    Followup: MachineOwner
    ---------
    And the driver is historically old.
    Code:
    fffff880`07df5000 fffff880`07dfd000   PdiPorts T (no symbols)           
        Loaded symbol image file: PdiPorts.sys
        Image path: \SystemRoot\system32\DRIVERS\PdiPorts.sys
        Image name: PdiPorts.sys
        Timestamp:        Fri Nov 17 06:01:16 2006 (455D02D4)
        CheckSum:         0000E8C4
        ImageSize:        00008000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Try to update it from Portrait Displays | Support | Technical Support For Branded Products . If any latest update is not available, uninstall that thing.

    Let us know the results.
      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:39.
Find Us