Windows 8 and 8.1 Forums

Windows 8 BSOD Issue

  1. #11

    Fairfield County, CT
    Posts : 348
    Windows 7 SP1

     Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Richard\AppData\Local\Temp\\SF_06-11-2012\110612-150640-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*
    Executable search path is: 
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
    Machine Name:
    Kernel base = 0xfffff800`59677000 PsLoadedModuleList = 0xfffff800`59941a60
    Debug session time: Mon Nov  5 18:40:57.934 2012 (UTC - 5:00)
    System Uptime: 0 days 3:07:07.750
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 133, {1, 780, 0, 0}
    *** WARNING: Unable to verify timestamp for IDSvia64.sys*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
    Probably caused by : IDSvia64.sys ( IDSvia64+339a5 )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    	DISPATCH_LEVEL or above. The offending component can usually be
    	identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    Debugging Details:
    BUGCHECK_STR:  0x133
    PROCESS_NAME:  uTorrent.exe
    LAST_CONTROL_TRANSFER:  from fffff8005984b8eb to fffff800596f1d40
    fffff880`1c9a2f28 fffff800`5984b8eb : 00000000`00000133 00000000`00000001 00000000`00000780 00000000`00000000 : nt!KeBugCheckEx
    fffff880`1c9a2f30 fffff800`5971cd91 : fffff800`59cc4713 fffff800`5996d180 fffff880`1c9a30e0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13ca8
    fffff880`1c9a2fb0 fffff800`5971dc18 : ffffffff`ffd0d9a0 fffff800`59657502 fffff880`1c9a30e0 fffffa80`11c00000 : nt!KeUpdateRunTime+0x51
    fffff880`1c9a2fe0 fffff800`5962deca : ffffffff`ffd0d9a0 fffff800`59657502 00000000`00000000 00000000`00000004 : nt!KeUpdateTime+0x3f9
    fffff880`1c9a31d0 fffff800`596eb1ae : 0000001a`2442cf3a fffff800`59982000 fffff800`59657580 00000008`a90cbc75 : hal!HalpTimerClockInterrupt+0x86
    fffff880`1c9a3200 fffff800`596b4186 : fffff800`596b4075 fffff880`1c9a3550 fffff880`04ced509 fffff880`1c9a3550 : nt!KiInterruptDispatchLBControl+0x1ce
    fffff880`1c9a3398 fffff800`596b4075 : fffff880`1c9a3550 fffff880`04ced509 fffff880`1c9a3550 fffff800`597540a4 : nt!RtlpSearchFunctionTable+0x6a
    fffff880`1c9a33a0 fffff800`59687643 : fffff880`00005562 fffff880`1c9a3550 fffff880`1c9a3530 fffff880`1c9a3b40 : nt!RtlpLookupFunctionEntryForStackWalks+0x95
    fffff880`1c9a3400 fffff800`59684736 : fffff880`1c9a0000 fffff880`1c9a6000 00000000`00000000 fffff800`59684736 : nt!RtlpWalkFrameChain+0x6eb
    fffff880`1c9a3ae0 fffff800`596847ec : 00000000`00000003 fffffa80`0d42fc18 00000000`00000000 00000000`00000001 : nt!RtlWalkFrameChain+0x5e
    fffff880`1c9a3b10 fffff800`59cc4713 : fffffa80`0d42fc00 fffff880`1c9a3c59 fffff880`1c9a3df8 00000000`00000032 : nt!RtlCaptureStackBackTrace+0x44
    fffff880`1c9a3b40 fffff800`59cc47bf : fffff980`ff71ec00 fffff880`1c9a3df8 fffff980`ff71ec00 fffff800`5983611d : nt!ViPoolLogStackCallout+0x2f
    fffff880`1c9a3b70 fffff800`59cc4a32 : fffff880`1c9a3ed0 00000000`00000032 00000000`00000003 fffff980`ff71ec00 : nt!ViPoolLogStackTrace+0x8f
    fffff880`1c9a3bb0 fffff800`598e76c1 : 00000000`00000400 fffff880`1c9a3c59 fffff880`1c9a3df8 00000000`00000000 : nt!VfFreePoolNotification+0x4a
    fffff880`1c9a3be0 fffff880`04ce89a5 : fffff980`ff71ec00 00000000`0000003e fffff880`04d1e750 00000000`00000040 : nt!ExDeferredFreePool+0xa9f
    fffff880`1c9a3cc0 fffff980`ff71ec00 : 00000000`0000003e fffff880`04d1e750 00000000`00000040 00000000`00000069 : IDSvia64+0x339a5
    fffff880`1c9a3cc8 00000000`0000003e : fffff880`04d1e750 00000000`00000040 00000000`00000069 fffff880`04d15616 : 0xfffff980`ff71ec00
    fffff880`1c9a3cd0 fffff880`04d1e750 : 00000000`00000040 00000000`00000069 fffff880`04d15616 fffff980`ff71ec00 : 0x3e
    fffff880`1c9a3cd8 00000000`00000040 : 00000000`00000069 fffff880`04d15616 fffff980`ff71ec00 00000000`438ec33a : IDSvia64+0x69750
    fffff880`1c9a3ce0 00000000`00000069 : fffff880`04d15616 fffff980`ff71ec00 00000000`438ec33a fffff880`1c9a3df8 : 0x40
    fffff880`1c9a3ce8 fffff880`04d15616 : fffff980`ff71ec00 00000000`438ec33a fffff880`1c9a3df8 00000000`00000069 : 0x69
    fffff880`1c9a3cf0 fffff980`ff71ec00 : 00000000`438ec33a fffff880`1c9a3df8 00000000`00000069 00000000`00000000 : IDSvia64+0x60616
    fffff880`1c9a3cf8 00000000`438ec33a : fffff880`1c9a3df8 00000000`00000069 00000000`00000000 afc4c2fc`893959cd : 0xfffff980`ff71ec00
    fffff880`1c9a3d00 fffff880`1c9a3df8 : 00000000`00000069 00000000`00000000 afc4c2fc`893959cd f1c38030`d324a33b : 0x438ec33a
    fffff880`1c9a3d08 00000000`00000069 : 00000000`00000000 afc4c2fc`893959cd f1c38030`d324a33b efab56a7`e4e775fb : 0xfffff880`1c9a3df8
    fffff880`1c9a3d10 00000000`00000000 : afc4c2fc`893959cd f1c38030`d324a33b efab56a7`e4e775fb 48030000`00000000 : 0x69
    fffff880`04ce89a5 ??              ???
    SYMBOL_NAME:  IDSvia64+339a5
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  IDSvia64.sys
    FAILURE_BUCKET_ID:  0x133_VRFK_ISR_IDSvia64+339a5
    BUCKET_ID:  0x133_VRFK_ISR_IDSvia64+339a5
    Followup: MachineOwner
    This is part of what I saw on your reports. I have bolded the Symantec Driver. These reports give clues and not answers. Symantec may have been the culprit that one time and may have been caused by a conflict with another software driver or a slow down with your system. It takes several attempts to discover the true cause. Already we have found another driver. We should wait until we solve the BSODs before we positively identify the potential cause. In your situation, you have already experienced another BSOD and Symantec was not involved.

    Your verifier results show that another driver may be the potential cause.

    Athrx.sys file description
    Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
    Atheros Extensible Wireless LAN device driver
    Atheros Communications, Inc.

    Go to the website and update driver. Do not update from the Windows updater.

      My System SpecsSystem Spec

  2. #12

    Posts : 13
    Windows 8 64-bit

    Thank you. You've been a huge help!

    I can't located a driver newer than what I already have

    I've disabled Verifier. Should I continue to run it?
    Last edited by AdamL; 07 Nov 2012 at 04:01.
      My System SpecsSystem Spec

  3. #13

    Fairfield County, CT
    Posts : 348
    Windows 7 SP1

    If you ran it 36 hours, you can turn it off. See if you can roll back the driver.
      My System SpecsSystem Spec

  4. #14

    Posts : 13
    Windows 8 64-bit

    The roll back option is grayed out.

    Still no sign of problems though.
      My System SpecsSystem Spec

  5. #15

    Fairfield County, CT
    Posts : 348
    Windows 7 SP1

    Just run it without the verifier off and lets see what happens.
      My System SpecsSystem Spec

  6. #16

    Posts : 13
    Windows 8 64-bit

    Will do. I'll let you know if any more problems occur.

    Thanks again!
      My System SpecsSystem Spec

  7. #17

    Posts : 13
    Windows 8 64-bit

    System has run fine without an issue since Norton 360 was removed.

    I cleaned out the Norton downloaded files and reinstalled Norton 360 with freshly downloaded files in case something in the original package was corrupt. 3 minute after Norton 360 was back up and running I noticed a slight stutter in the mouse and shortly after that the same BSOD occurred.

    Uninstalled Norton 360 and now using Windows Defender.

    I think it's safe to say that in my case Norton 360 is the problem.

    Thank you Richc46 for all of you're help. I never would've solved this without your advice!
      My System SpecsSystem Spec

  8. #18

    Posts : 13
    Windows 8 64-bit

    Strange one here... The Norton people asked me to install V6 to see if that still caused dramas. It didn't, and the system has been running fine for a week now.

    Yesterday Windows attempted to install KB2769165 and KB2770917. Both of these updates failed numerous times. A Google search showed that it was common and stopping the nlsx86cc service and then installing the updates would solve the problem and it did just that.

    The BSOD's have returned after those updates. I uninstalled the updates, which again required that service to be stopped or else it failed. Problem is now I've still gotten 2 BSOD after uninstalling those updates. No other changes were made to my system prior to those updates.

    Could someone please have a look at the reports and advise me as to what's causing this round of errors?
      My System SpecsSystem Spec

  9. #19

    Posts : 197
    Win 8 Enterprise RTM

    Again IDSvia64.sys
      My System SpecsSystem Spec

Page 2 of 2 FirstFirst 12
Windows 8 BSOD Issue
Related Threads
Please help BSOD issue in BSOD Crashes and Debugging
My laptop just isn't cooporating. I recently updated to windows 8.1 and I had an issue where I couldn't pick up any wireless networks at all. I saw this was a common issue amongst others and I read somewhere that you need to disable wifi and then re enable it. So I tried to do that and half way...
BSOD Issue Windows 8 in BSOD Crashes and Debugging
Hi guys recently my laptop gave the BSOD and just gave up on me. Already formatted the laptop but still no luck. Attached the DUMP file and hope someone can help me to solve the issue:geek: System Specs: Samsung Intel i5-2410m cpu@2.30ghz 2.29Ghz 6gbram 64bit
Solved BSOD Graphics card issue/Avast Issue? in BSOD Crashes and Debugging
Hello forum, So I just updated my Nvidea graphics card, and for some reason after restarting my laptop, in order to install these files to the system, the "System Thread Exception Not Handled" Blue screen error flashed on my screen, and later redirected me to an automatic repair screen, which...
I built my current system about a month ago. Since then, I've had numerous BSODs, some caused by my graphics card driver. I updated the driver and the BSODs became less frequent. However, I still get them regularly, usually when waking the computer from sleep mode. I've had a couple at random times...
BSOD Issue in BSOD Crashes and Debugging
Hi, I found this resourceful forum while trying to solve my BSOD issue. I recently switched my PC from Windows 7 to Windows 8. Since completing the installation of 8, I have had the random BSOD resets that others have had. However, in Windows 7 I would also have strange random lock-ups without...
BSOD Issue in BSOD Crashes and Debugging
Hi Today I'm having this BSOD screens, first time since I have windows 8, first happen when I was playing, and the second was in windows. I don't know the causes, maybe firmware of my SSD, but first I want to ask here. Sorry for my bad english, isn't my native language. Thanks for help
BSOD in Windows 8, suspected RAM issue in BSOD Crashes and Debugging
Hi all, Last night I experienced multiple BSOD errors when running CS:GO and Hitman Absolution. It has also happened at the desktop and when in Firefox, so there appears to be no pattern to these errors. I left Windows Memory Diagnostic running overnight and this is what the report came back...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook