It is currently Sun Jun 16, 2019 1:53 pm

All times are UTC - 7 hours [ DST ]

Recent News:



Post new topic Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Mon Sep 30, 2013 9:21 am 
Offline
Top Contributor
Top Contributor
User avatar

Joined: Sun Jan 10, 2010 9:25 pm
Posts: 626
Location: Shelby Township, MI
Thanks: 74
Thanked: 145 times in 106 posts
My wife let me "borrow" her HP Envy desktop that I bought for her earlier this year. Having an MSDN subscription I wanted to try out the Windows 8.1 bits so I bought her a new iPad, and she let me take the desktop. It's been running Windows 8 since the day we got it.

I installed Windows 8.1 on a Kingston HyperX 128GB SSD, then reinstalled the original HDD. Windows OOB came with most drivers, while a few others were pulled down from Windows Update. The only one that needed some additional help was the AMD AHCI controller. Going out to HP's website for the h8-1534 model, I grabbed the latest AMD driver for the storage controller, which was released in February.

Everything ran great for several days, until this past Friday, when the PC was sitting at the Startup Repair screen. I rebooted it, and it ran fine for about a day, but then it blue screened again. And again yesterday, and once more this morning.

Each time I ran WinDbg x64, and each time the error is identical. The BSOD code is DPC_WATCHDOG_VIOLATION (0x133) and the four parameters are always the same (0x0, 0x500, 0x501, 0x0). The offending driver is storport.sys, in the storport!RaidAdapterAcquireInterruptLock+125e2 function. The problem is very consistent -- it always faults in the same function in the same spot.

Microsoft's explanation of the dump code is this: "The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. A single DPC or ISR exceeded its time allotment. The offending component can usually be identified with a stack trace"

Normally I'm pretty good at troubleshooting, and resolving, coredumps. But this one I cannot seem to pin down.

I haven't yet installed antivirus software, so I can't point the finger there.

I loaded WindowSMART 2013, and the health of both the SSD and HDD is flawless. The UEFI diagnostics run against both the SSD and HDD also said the disks are in perfect health. Nevertheless I replaced the SATA cables for good measure, and yet the coredumps persist.

For those who salivate at the thought of coredumps, here's the contents from WinDbg.

Hopefully someone here has some insight.

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: symsrv*symsrv.dll*h:\WebSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff802`1fa72000 PsLoadedModuleList = 0xfffff802`1fd399b0
Debug session time: Sun Sep 29 23:56:33.642 2013 (UTC - 4:00)
System Uptime: 0 days 4:50:36.344
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols

Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, 0}

Probably caused by : storport.sys ( storport!RaidAdapterAcquireInterruptLock+125e2 )

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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
                component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000

Debugging Details:
------------------


DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff8021fbf1c82 to fffff8021fbc20a0

STACK_TEXT: 
fffff802`21c01c98 fffff802`1fbf1c82 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff802`21c01ca0 fffff802`1faeeaec : 00000000`00000000 00000000`00000000 fffff802`21c01d90 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x1f6f2
fffff802`21c01d30 fffff802`1fa09e5f : 00000000`00000000 00000000`00000001 00003c23`0c9bb348 00000000`00008101 : nt!KeClockInterruptNotify+0x77c
fffff802`21c01f40 fffff802`1fb07703 : fffff802`1fa56900 00000000`00000008 fffff802`21c01f50 00000000`00000010 : hal!HalpTimerClockInterrupt+0x4f
fffff802`21c01f70 fffff802`1fbc352a : fffff802`1fa56900 ffffe000`01e41db0 00000000`00000001 ffffe000`01e4c730 : nt!KiCallInterruptServiceRoutine+0xa3
fffff802`21c01fb0 fffff802`1fbc3e9b : fffff802`1fd14100 00000000`00000000 ffffe000`00000000 00001f80`00a00b0f : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff802`21bf2750 fffff802`1fb072e0 : 00000000`00000000 00000000`00010008 00000000`00000000 ffffe000`02e770f0 : nt!KiInterruptDispatchNoLockNoEtw+0xfb
fffff802`21bf28e0 fffff802`1fb07656 : 00000000`00000002 fffff802`1faf0eda fffff802`1fd63180 fffff802`1fd63180 : nt!KxWaitForSpinLockAndAcquire+0x20
fffff802`21bf2910 fffff800`00bb24a2 : fffff802`21bf2b10 00000028`8cf2100d 00000001`00000100 00000000`ffffffff : nt!KeAcquireInterruptSpinLock+0x3e
fffff802`21bf2950 fffff800`00ba311a : ffffe000`01e4c1a0 ffffe000`01e4c770 fffff802`1fd68580 00000000`00000002 : storport!RaidAdapterAcquireInterruptLock+0x125e2
fffff802`21bf2980 fffff802`1faf56e2 : fffff802`21bf2b20 fffff802`21bf2ae0 ffffe000`01e4c770 fffff802`1fd63180 : storport!RaidpAdapterTimerDpcRoutine+0xa2
fffff802`21bf29e0 fffff802`1fbc5bea : fffff802`1fd63180 fffff802`1fd63180 fffff802`1fdbba80 ffffe000`0199a080 : nt!KiRetireDpcList+0x6b2
fffff802`21bf2c60 00000000`00000000 : fffff802`21bf3000 fffff802`21bec000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP:
storport!RaidAdapterAcquireInterruptLock+125e2
fffff800`00bb24a2 8ad8            mov     bl,al

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  storport!RaidAdapterAcquireInterruptLock+125e2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: storport

IMAGE_NAME:  storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5215f857

BUCKET_ID_FUNC_OFFSET:  125e2

FAILURE_BUCKET_ID:  0x133_DPC_storport!RaidAdapterAcquireInterruptLock

BUCKET_ID:  0x133_DPC_storport!RaidAdapterAcquireInterruptLock

Followup: MachineOwner
---------

_________________
Matt Sawyer
Owner, Dojo North Software, LLC

HP EX490, 4GB, E5300, 15TB - Server 2012 - Sharing and Streaming
HP EX487, 4GB, E5300, 13TB - Server 2012 Essentials - Backups


Top
 Profile  
Thanks  

Attention Guest: Remove this ad by Registering with the MediaSmartServer.net Forums. It's Free!
PostPosted: Wed Oct 02, 2013 5:46 am 
Offline
Max Contributor
Max Contributor
User avatar

Joined: Sat Apr 12, 2008 12:49 pm
Posts: 2215
Location: Casper Wyoming
Thanks: 76
Thanked: 249 times in 246 posts
While not a solution,
I have heard over at homesevershow that 8.1 is still pretty buggy and my guess is you will be able to google it and find more people will be having the same problem.
You already know it could be the driver and/or the hardware combo.
Goodluck
If you had another brand ssd I would try that, I dual boot win7 64 1 spinner and 1 ssd on the same box, just in case something gets balled up. The registration is the same on both as I can only use one at a time and the only difference is the drives swap places...
I hate it when things don't go the way they are supposed to. I have 1 free win8 upgrade that I haven't used yet, I don't like to be out on the edge, I'll wait a year or two, heck I just got everything to win7.
I do have win2012E on a diy and like most, don't like the metro, but I will be getting a windows phone coming up soon, so I for sure can't be trusted :crazy:
Hope things get behaving for ya...

_________________
[X510 CPU/RAM/All 2 TB Red's] [X510 CPU/Sync'ed Backup/All 2 TB Hitachi's]
[X510 /2 in box]
[X710 LIAN LI DIY W2012E] Stablebit Drivepool [EX-503 LIAN LI 5-bay USB3 External]
:twisted: Fear the Cloud :twisted:


Top
 Profile  
Thanks  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC - 7 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group