BSOD randomly with new computer - Last error code 3b

Page 4 of 5 FirstFirst ... 2345 LastLast

  1. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #31

    Unfortunately the last logs are completely empty, can your run the Log Collector again and post up the resulting logs.
      My Computer


  2. Posts : 34
    Windows 7 Home Premium 64bit
    Thread Starter
       #32

    Sorry about that Boozad.

    I tried to generate the logs again two more times which took forever and both times they came up empty. Turned off driver verifier and the log generated as usual. Apparently verifier blocks the log collector somehow. Verifier has been running for a week without an incident so hopefully I can leave it off. I also had real time protection turned off in security essentials for that week too, but have that on again as of yesterday. Windows update took over 8 hours when verifier was running which was very annoying.

    Anyway attached is the log.

    Sorry again. I should have looked at the log before posting.
      My Computer


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

    I had another BSOD incident over the weekend. Posting the new log collector data. Thanks for your help.
      My Computer


  4. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #34

    The last dump is partially corrupt and I can't dump the stack unfortunately, however this does show which may be relevant.
    Code:
    OVERLAPPED_MODULE: Address regions for 'hiber_dumpfve' and 'WUDFRd.sys' overlap
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003319100
    GetUlongFromAddress: unable to read from fffff800033191c0
     0000000004000000 Nonpaged pool
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt!KiProcessExpiredTimerList+72
    fffff800`030e7262 803818          cmp     byte ptr [rax],18h
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    Are you using hibernation at all?
      My Computer


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

    My power settings are set to sleep after three hours and hybernate is set to never. Allow to hybrid sleep is set to on. Does this answer your question?
      My Computer


  6. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #36

    It may be an idea to disable sleep while we're trying to work through this. It's a tough one and it would be best to eliminate any possible causes, no matter how remote they may seem.
      My Computer


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

    OK. I've disabled sleeping.
      My Computer


  8. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #38

    Good, upload new logs from any subsequent BSODs.
      My Computer


  9. Posts : 34
    Windows 7 Home Premium 64bit
    Thread Starter
       #39

    Boozad,

    All was working fine for sometime. Probably 10 days or so. I then changed the sleep settings for the system to sleep after 15 minutes (see screenshot jpg). Kind of to see if this was the issue. The system worked OK like this for about a week and then had a BSOD when going to sleep today.

    Thanks for all your help.

    Scott
      My Computer


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

    Had another BSOD so I have now gone back to not allowing the computer to go to sleep. Also attaching new log file.
      My Computer


 
Page 4 of 5 FirstFirst ... 2345 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 22:13.
Find Us