Page 1 of 3 123 Last
  1. #1

    Few BSODs - WIN 7 x64

    Hello there! Recently, I decided to change my PC to a newer one, since my old one got quite outdated to perform well in games, etc. After a while of enjoying my new machine Ive got a few BSODs, but they arent so frequent so at first I only tried to find the solutions by upgrading the drivers and it fixed the DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD, but then I started to get one I didnt fix - SYSTEM_SERVICE_EXCEPTION more frequently and a new one - KMODE_EXCEPTION_NOT_HANDLED.

    The only part I took from my old PC was the HDD ST350041 8AS SCSI Disk Device (500 GB, 7200 RPM, SATA-II) to work as a data storage, everything else is brand new.

    I also ran memtest with 7 passes and no errors were found and a chkdisc with same result.

    OS - Windows 7 Home Premium
    x64
    What was original installed OS on system? - Windows 7
    Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? I purchased it from a retailer.
    Age of system (hardware) - Everything brand new, besides the HDD. The HDD is 5 years old.
    Age of OS installation - have you re-installed the OS? Fresh one, about 2 weeks.
    CPU - Intel i5 4690k
    Video Card - ASUS Strix Geforce GTX970
    MotherBoard - MSI Z97 Gaming 5
    Power Supply - Corsair CX600M

    The list of BSODs so far:

    SYSTEM_SERVICE_EXCEPTION
    DRIVER_IRQL_NOT_LESS_OR_EQUAL
    IRQL_NOT_LESS_OR_EQUAL
    KMODE_EXCEPTION_NOT_HANDLED

    Providing the files:
    SysnativeFileCollectionApp.zip
    perfmon.zip


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    Re: Few BSODs - WIN 7 x64

    Before I debug the current crash dumps, can you enable verifier? I'm curious:


    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

    Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point
    Windows 7 - START | type create | select "Create a Restore Point"
    Windows 8/8.1 - Restore Point - Create in Windows 8

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    - Special Pool
    - Pool Tracking
    - Force IRQL Checking
    - Deadlock Detection
    - Security Checks (only on Windows 7 & 8/8.1)
    - DDI compliance checking (only on Windows 8/8.1)
    - Miscellaneous Checks
    4. Select - "Select driver names from a list"
    5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
    7. Click on Finish.
    8. Restart.

    Important information regarding Driver Verifier:

    - Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

    - If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

    - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > Search > type "cmd" without the quotes.

    - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

    - Restart and boot into normal Windows.

    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > type "system restore" without the quotes.

    - Choose the restore point you created earlier.

    -- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

    How long should I keep Driver Verifier enabled for?

    I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

    My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

    - If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

    - If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

    Any other questions can most likely be answered by this article:

    Using Driver Verifier to identify issues with Windows drivers for advanced users

  3. #3

    Re: Few BSODs - WIN 7 x64

    Done, no BSOD so far.

  4. #4

    Re: Few BSODs - WIN 7 x64

    Keep me updated.

  5. #5

    Re: Few BSODs - WIN 7 x64

    Been running for an hour so far and nothing happened. Do you require me to wait 24h?

  6. #6

    Re: Few BSODs - WIN 7 x64

    Yeah, keep it on. In your case, it'll probably show nothing since it's most likely a hardware problem as I first saw, but before I debug that like I said, let's just see what verifier shows.

  7. #7

    Re: Few BSODs - WIN 7 x64

    Oh yeah I forgot to add, those BSODs happen almost exclusively when I watch a vid on youtube or a stream on twitch. One happened only once when I was playing a game, but it was that driver one. Also, I didnt format the HDD, dont really think it might be the case tho.

  8. #8

    Re: Few BSODs - WIN 7 x64

    With that said, disable hardware acceleration in your browser.

  9. #9

    Re: Few BSODs - WIN 7 x64

    After disabling acceleration videos on youtube sometimes make BZZZZ sounds when they are playing. Sound card problems maybe?

  10. #10

    Re: Few BSODs - WIN 7 x64

    Hmm, no, that actually sounds like a high DPC side effect from verifier.

    Since we disabled HWA, your processor renders videos now and it's more of a software-side thing than it is your GPU rendering it based on its memory, so since your system is under a lot of stress from verifier, it should be normal that there's buzzing. If there's buzzing after disabling verifier later, I'd look into your sound card drivers.

  11. #11

    Re: Few BSODs - WIN 7 x64

    Ok, I woke up and I got a BSOD MEMORY_MANAGEMENT
    Heres the dump file:

    062915-8533-01.zip

  12. #12

    Re: Few BSODs - WIN 7 x64

    Hmm, did it generate a kernel-dump version of this bug check in C:\Windows (MEMORY.DMP)?

    If so, upload that to a drive site and paste the link here. It'll help a lot in debugging.

  13. #13

    Re: Few BSODs - WIN 7 x64

    Yeah, the memory.dmp date is updated, so it got saved there. By drive you mean like a google drive? Considering the file is 1gb - probably yes.

    Anyway, I have to go to work, so I will continue this in 9 hours when Im back home.

  14. #14

    Re: Few BSODs - WIN 7 x64

    Correct, make sure you zip it so it's compressed.

  15. #15

    Re: Few BSODs - WIN 7 x64

    Left the PC on at home and got it uploaded. Here is the link (notify me if it doesnt work for some reason):
    https://drive.google.com/open?id=0B1...MW8&authuser=0

  16. #16

    Re: Few BSODs - WIN 7 x64

    Back from work. No BSODs since the one early in the morning. PC been running on all the time.

  17. #17

    Re: Few BSODs - WIN 7 x64

    Code:
    2: kd> .bugcheck
    Bugcheck code 0000001A
    Arguments 00000000`00000411 fffff6fc`5001b7f8 87000003`5cd77882 fffff8a0`03708f61
    0x411 1st argument implies there was a corrupted page table entry (PTE).

    Code:
    2: kd> knL
     # Child-SP          RetAddr           Call Site
    00 fffff880`035fdeb8 fffff800`02ead2ad nt!KeBugCheckEx
    01 fffff880`035fdec0 fffff800`02f01c61 nt! ?? ::FNODOBFM::`string'+0x6051
    02 fffff880`035fdf10 fffff800`02eee61f nt!MiResolveTransitionFault+0x381
    03 fffff880`035fdfa0 fffff800`02ede5bb nt!MiDispatchFault+0x95f
    04 fffff880`035fe0b0 fffff800`02ece9ee nt!MmAccessFault+0xe1b
    05 fffff880`035fe210 fffff800`03167b67 nt!KiPageFault+0x16e
    06 fffff880`035fe3a0 fffff800`03182845 nt!CmpReportNotifyHelper+0x123
    07 fffff880`035fe430 fffff800`03182f4a nt!CmSetValueKey+0x445
    08 fffff880`035fe570 fffff800`02ecfb53 nt!NtSetValueKey+0x349
    09 fffff880`035fe6a0 fffff800`02ecc110 nt!KiSystemServiceCopyEnd+0x13
    0a fffff880`035fe8a8 fffff880`0199fa26 nt!KiServiceLinkage
    0b fffff880`035fe8b0 fffff880`01995ca3 NETIO!NsipWritePersistentData+0x327
    0c fffff880`035fe980 fffff880`019965cf NETIO!NsiSetAllParametersEx+0x203
    0d fffff880`035fea20 fffff880`01ad7298 NETIO!NsiSetAllParameters+0x6f
    0e fffff880`035feaa0 fffff880`0198d71b tcpip!TcpWsdWorkQueueRoutine+0xa8
    0f fffff880`035feaf0 fffff800`031c5c3d NETIO!NetiopIoWorkItemRoutine+0x3b
    10 fffff880`035feb40 fffff800`02eda4b5 nt!IopProcessWorkItem+0x3d
    11 fffff880`035feb70 fffff800`0316a456 nt!ExpWorkerThread+0x111
    12 fffff880`035fec00 fffff800`02ec22c6 nt!PspSystemThreadStartup+0x5a
    13 fffff880`035fec40 00000000`00000000 nt!KxStartSystemThread+0x16
    We start going off the rails on frame #0b, which is the Network I/O Subsystem's function writing data regarding the network store interface service. The service is generally in charge of sending network related notifications to user-mode apps.

    Code:
    2: kd> !running
    
    System Processors:  (000000000000000f)
      Idle Processors:  (000000000000000b) (0000000000000000) (0000000000000000) (0000000000000000)
    
           Prcbs             Current         (pri) Next            (pri) Idle
      2    fffff88003372180  fffffa800c793040 (13)                       fffff8800337cfc0  ................
    Processor #2 is the only non-idle processor, so we can't investigate the others.

    I'm leaning towards avast! possibly causing this, but I can't be sure. We can see it in the raw stack doing pool stuff before the bug check:

    Code:
    2: kd> dps fffff880035f9000 fffff880035ff000
    fffff880`035fc1e0  fffff800`0337fa1f nt!VerifierExFreePoolWithTag+0x2f
    fffff880`035fc208  00000000`00000001
    fffff880`035fc210  fffff880`04849e79 aswSP+0x49e79
    fffff880`035fc218  00000000`00000001
    fffff880`035fc250  fffff880`0486b582 aswSP+0x6b582
    fffff880`035fc258  00000000`00000000
    fffff880`035fc288  00000000`00000001
    fffff880`035fc290  fffff880`0486af6b aswSP+0x6af6b
    fffff880`035fc2a8  00000000`00000010
    fffff880`035fc2b0  fffff880`0486ae4c aswSP+0x6ae4c
    Let's get rid of avast! with MSE for now and see what happens.


    avast! removal - Avast Uninstall Utility | Download aswClear for Avast Removal

    MSE - Microsoft Security Essentials - Microsoft Windows

  18. #18

    Re: Few BSODs - WIN 7 x64

    Got rid of avast and installed MSE. The thing is, I had avast installed all the time, but since I got my first BSOD I kept the passive protection disabled at all times. Not sure if that changes anything.

  19. #19

    Re: Few BSODs - WIN 7 x64

    Nope, doesn't really change anything actually considering the active protection module(s) are entirely separate than its other kernel-suite modules, such as its firewall, etc.

    Anyway, keep me updated.

  20. #20

    Re: Few BSODs - WIN 7 x64

    Got another BSOD watching a twitch stream now. KMODE_EXCEPTION_NOT_HANDLED, its the 3rd time I got this one.


    Dump file:

    062915-5475-01.zip

Page 1 of 3 123 Last

Similar Threads

  1. Win 7 BSODs
    By Fred Garvin in forum BSOD, Crashes, Kernel Debugging
    Replies: 3
    Last Post: 10-09-2014, 07:09 PM
  2. Various BSODs
    By Nick in forum BSOD, Crashes, Kernel Debugging
    Replies: 22
    Last Post: 01-11-2014, 08:30 AM
  3. Various BSODs
    By lo16 in forum BSOD, Crashes, Kernel Debugging
    Replies: 3
    Last Post: 09-25-2013, 08:17 PM
  4. Still having BSODs
    By Kreebons in forum BSOD, Crashes, Kernel Debugging
    Replies: 20
    Last Post: 12-12-2012, 03:10 PM
  5. [SOLVED] Various BSODs
    By Cl0ttERS in forum BSOD, Crashes, Kernel Debugging
    Replies: 67
    Last Post: 05-29-2012, 05:44 PM

Log in

Log in