BSOD while playing approximately 15 minutes of Watch Dogs (Kernel 41)

Page 1 of 3 123 LastLast

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

    BSOD while playing approximately 15 minutes of Watch Dogs (Kernel 41)


    Hi, I've searched around to see if there are similar problems out there that can help out with my BSOD situation, but none of them seems to work/unresolved or unrelated.

    I've only had this problem lately while playing the new game Watch Dogs, I can play the game for around 15 minutes before the game crashes for a few seconds and then BSOD happens. My graphics drivers is updated to the current version, I changed the graphics settings in Watch Dogs to either low or off, tried playing the game in full screen and also windowed mode, but the problem still persists. I have the system requirements to play the game as well.

    Here are my specs:

    CPU: intel i7 3770k
    GPU: NVIDIA GeForce GTX 660 Ti
    PSU: Corsair AX850
    RAM: 4x Corsair Vengeance 4GB (16GB)
    MOBO: Sabertooth Z77

    I had a look at my event logs, the critical causing this crash is Kernel Power 41 and possibly along with the error: BugCheck 1001

    I've used SF Diagnostic Tool to attach the dump files and other information.
    Attachment 320449

    If there's anything else you need to know to help solve this, let me know.

    Any help with this situation is much appreciated!
    Thanks!
      My Computer

  2.    #2

    Code:
    Unable to load image \SystemRoot\system32\DRIVERS\avgidsdrivera.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgidsdrivera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
     avgidsdrivera+0x1bede
    Uninstall AVG using the removal tool.

    http://www.avg.com/gb-en/utilities

    Replace it with MSE and Malwarebytes.

    Microsoft Security Essentials - Microsoft Windows

    Malwarebytes | Free Anti-Malware & Internet Security Software

       Tip

    Make sure you don't enable the free trial of malwarebytes pro, deselect the option when prompted.


      My Computer


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

    Hi, thanks for the reply. I removed AVG using the link you provided and tried to play the game again, the same thing happens, it's still says kernel 41 on the event log along with:-

    BugcheckCode 26
    BugcheckParameter1 0x5003
    BugcheckParameter2 0xfffff70001080000
    BugcheckParameter3 0x80816
    BugcheckParameter4 0x808140010302c
    SleepInProgress false
    PowerButtonTimestamp 0

    If that helps at all?
    I can play any other game with high graphics without any problems, such as Battlefield 4.

    Thank you in advance.
      My Computer

  4.    #4

    Upload all new dump files.

    Run a Disk Check to scan for errors

       Note

    Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
    If it finds errors reboot and run the scan two more times


    Run SeaTools to see if your HDD or SSD is failing

    Post back the results.
      My Computer


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

    Hi, here's the recent dump file
    Attachment 320868

    I did the disk check, everything was fine, then did the sfc /scannow and three time it stopped at 67% complete and windows resource protection could not perfrom the requested operation. then back to C:\windows\system32>

    I've ran SeaTools and my HDD passed

    Thanks
      My Computer

  6.    #6

    Code:
    BugCheck 1A, {5003, fffff70001080000, 80816, 808140010302c}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2984f )
    Code:
    4: kd> !wsle 2
    
    Working Set @ fffff70001080000
        FirstFree    80816  FirstDynamic        c
        LastEntry    80ac0  NextSlot            5  LastInitialized    80b6e
        NonDirect        0  HashTable           0  HashTableSize          0
    
    Reading the WSLE data ......Unable to get Wsle table block - address fffff70001081088 - count 1024 - page 0x180
    The working set list entries are corrupt, this is mainly caused by bad RAM.

    Memtest86 will test your RAM

       Information

    Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing
      My Computer


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

    I ran the memtest up to 10 passes to make sure it hasn't missed anything, but wasn't sure if that's long enough? but after 26 hours it said no errors.

    I am also messaging the UPlay's technical support about the game and they have told me to do certain instructions, but still getting the same result, so here's the latest dump file
    Attachment 321327

    Many thanks
      My Computer

  8.    #8

    Your Nvidia display driver is causing issues...

    Roll it back to an earlier version (late 2013) to see if it helps the problem.

    Code:
    6: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f0fe000 fffff880`0fd62000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue May 20 00:08:44 2014 (537A8EFC)
        CheckSum:         00C1EA41
        ImageSize:        00C64000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    Hi, I rolled back the video card driver to an earlier date and tried the game again, but this time the game playing time only last around 5 minutes than the usual 15/20 minutes or so before the crash and BSOD happens. The event log still said it was Kernel 41, but the BSOD changed to "System Service Exception" so I'm guessing that the roll back might have caused this? Occasionally I see Memory Management on the BSOD. I looked around to find a solution to this and some people suggest a clean windows install, should I try that?

    But I've attached the latest minidump: Attachment 321515

    Thanks so much for your help already!
      My Computer

  10.    #10

    Right, changing the display version seemed to help.
    I suggest rolling back a few times to see if the issue persists.
      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 15:03.
Find Us