Windows 8 BSOD Issue

AdamL

Member
Member
Messages
13
Hi everyone! :D

I'm hoping that the very knowledgeable and helpful people on this forum can help me because, honestly, I am way out of my league here!

My system contains the following:
- i7 2600
- Asrock Extreme 3 Gen 3
- G.Skill Ripjaws X F3-12800CL9Q-16GBXL
- Asus GTX550Ti
- Intel 520 SSD

I had a very old HDD fail, so decided to upgrade to the SSD listed above. After installing that I was getting random freezes and lock ups requiring a reset.
I tried lots of things from tests, drivers, new PSU, new SATA cables and eventually RMA'd the SSD.

Windows 8 was released and I thought rather than go through all the updates to Win7 I'd buy Win8 and start fresh with the new SSD.

All has been going well until I started getting the odd freeze and then the system restarted with an on screen message that the system has recovered from and error and created a memory dump file.

I really have no idea what I'm looking at and I'm at my wits end with this system.

Could someone please take a look at the dump file and offer any advice on what to do from here?

Much appreciated!

Adam.

(I've followed the BSOD posting instructions thread and attached the ZIP file below)
 

My Computer

System One

  • OS
    Windows 8 64-bit
Just happened 3 more times while I was sitting here. Each time I see a DCP_WATCHDOG_VIOLATION.

Dump's attached...

Any help is greatly appreciated!:)
 

My Computer

System One

  • OS
    Windows 8 64-bit
I've done another clean install and the same thing is still happening.

The common error seems to be hal.dll with a code of 0x133 whatever that means?

Here's more dumps...
 

My Computer

System One

  • OS
    Windows 8 64-bit
Verifier is still running and there's been a few more events since, so here's the dumps for that.

I'll post the final batch after the 36 hours as suggested.
 

My Computer

System One

  • OS
    Windows 8 64-bit
MAYBE
Luck
Verifier suggests that it may by your Symantec
Make a system restore point, uninstall Symantec
Then install the built in Windows Defender
Before starting anything create a system restore point.
 

My Computer

System One

  • OS
    Windows 7 SP1
    System Manufacturer/Model
    Dell XPS 420
    Memory
    6 GB
All done.

I'll continue to run verifier and report any problems when/if they occur.

Thanks again for your help!
 

My Computer

System One

  • OS
    Windows 8 64-bit
Ok, Verifier has been running for 36 hours now.
In that time I've only had 1 more BSOD, but this time it was a different one to all the others.

Could you please tell me which Symantec driver the reports said was suspect. The Symantec people would like to know.
Strange thing is I have a laptop running the same version of Norton 360 and it works fine. Is it just a case of driver conflicts rather than driver faults?

I've attached the dumps of the verifier session including the last BSOD.

Thanks again for your help!
 

My Computer

System One

  • OS
    Windows 8 64-bit
Code:
 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\Temp2_SF_06-11-2012.zip\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*http://msdl.microsoft.com/download/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 [B]IDSvia64.sys[/B]*** 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                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
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:
------------------


DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x133

PROCESS_NAME:  uTorrent.exe

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff8005984b8eb to fffff800596f1d40

STACK_TEXT:  
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


STACK_COMMAND:  kb

FOLLOWUP_IP: 
IDSvia64+339a5
fffff880`04ce89a5 ??              ???

SYMBOL_STACK_INDEX:  f

SYMBOL_NAME:  IDSvia64+339a5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: IDSvia64

IMAGE_NAME:  IDSvia64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  503d8308

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
Productname:
Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
Description:
Atheros Extensible Wireless LAN device driver
Company:
Atheros Communications, Inc.

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

My Computer

System One

  • OS
    Windows 7 SP1
    System Manufacturer/Model
    Dell XPS 420
    Memory
    6 GB
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:

My Computer

System One

  • OS
    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! :thumbsup:
 

My Computer

System One

  • OS
    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 Computer

System One

  • OS
    Windows 8 64-bit
Again IDSvia64.sys
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
Back
Top