minidump windows 8 daily (Network Steve Forum)

minidump windows 8 daily

Hello! friends here my minidump, i don't know how fix

here details:

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff800bb9f2f4b to fffff800bb873440

STACK_TEXT:
fffff800`bb6ba508 fffff800`bb9f2f4b : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff800`bb6ba510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x145a4

STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+145a4
fffff800`bb9f2f4b cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+145a4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 51a966cd

FAILURE_BUCKET_ID: X64_0x133_nt!_??_::FNODOBFM::_string_+145a4

BUCKET_ID: X64_0x133_nt!_??_::FNODOBFM::_string_+145a4

Followup: MachineOwner

THANKS SO MUCH

July 16th, 2013 11:12pm

A bugcheck (BSOD) is a mechanism to protect your PC from damage.

You get this one:

Bug Check 0x133 DPC_WATCHDOG_VIOLATION

http://msdn.microsoft.com/en-us/library/jj154556%28v=vs.85%29.aspx

The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.

To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

If you can't see dmp files, make sure your Windows is configured correctly [2][3] to generate dumps.

If you want to analyze them your own, check those videos [4][5] and read this KB article [6].

Andr

[1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
[2] http://support.microsoft.com/kb/254649
[3] http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
[4] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-15-WinDbg-Bugchecks
[5] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-16-WinDbg-Driver-Verifier, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-17-WinDbg-Driver-Verifier-Part-2, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-18-WinDbg-Driver-Verifier-Part-3
[6] http://support.microsoft.com/kb/315263

Free Windows Admin Tool Kit Click here and download it now

July 17th, 2013 12:48am

A bugcheck (BSOD) is a mechanism to protect your PC from damage.

You get this one:

Bug Check 0x133 DPC_WATCHDOG_VIOLATION

http://msdn.microsoft.com/en-us/library/jj154556%28v=vs.85%29.aspx

The DPC_WATCHDOG_VIOLATION bug check has a value of 0x00000133. This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.

To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

If you can't see dmp files, make sure your Windows is configured correctly [2][3] to generate dumps.

If you want to analyze them your own, check those videos [4][5] and read this KB article [6].

Andr

[1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
[2] http://support.microsoft.com/kb/254649
[3] http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
[4] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-15-WinDbg-Bugchecks
[5] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-16-WinDbg-Driver-Verifier, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-17-WinDbg-Driver-Verifier-Part-2, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-18-WinDbg-Driver-Verifier-Part-3
[6] http://support.microsoft.com/kb/315263

July 17th, 2013 4:25pm

ok, your old nVIDIA storage driver (2009!!!) is causing it. Update the driver to fix the crashes:

*******************************************************************************
*                                                                             *
*                        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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

TAG_NOT_DEFINED_c000000f:  FFFFF800BB6C0FB0

LAST_CONTROL_TRANSFER:  from fffff800bb9f2f4b to fffff800bb873440

STACK_TEXT:  
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!KeUpdateTime
hal!HalpTimerClockInterrupt
nt!KiInterruptDispatchNoLockNoEtw
nt!KxWaitForLockOwnerShip
storport!RaidpAdapterTimerDpcRoutine
nt!KiProcessExpiredTimerList
nt!KiExpireTimerTable
nt!KiTimerExpiration
nt!KiRetireDpcList
nt!KiIdleLoop


t!KxWaitForLockOwnerShip+0x28
nt!KiInitialPCR+0x180
fffff800`bb6ba950  fffff880`0128b0b4*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
 nvstor64+0x30b4
fffff800`bb6ba958  fffff880`012c87d9 storport!RaidpAdapterTimerDpcRoutine+0x59
fffff800`bb6ba960  fffffa80`042a71a0
fffff800`bb6ba968  fffffa80`04a21c70
fffff800`bb6ba970  fffff800`bb6baa79
     
    Loaded symbol image file: nvstor64.sys
    Image path: nvstor64.sys
    Image name: nvstor64.sys
    Timestamp:        Wed Jul 01 02:21:51 2009 (4A4AAC1F)
    CheckSum:         0003C24D
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    Image name: storport.sys
    Timestamp:        Fri Mar 01 05:58:51 2013 (5130358B)
    CheckSum:         000567FC
    ImageSize:        00055000
    File version:     6.2.9200.16547
    Product version:  6.2.9200.16547
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     storport.sys
    OriginalFilename: storport.sys
    ProductVersion:   6.2.9200.16547
    FileVersion:      6.2.9200.16547 (win8_gdr.130228-1507)
    FileDescription:  Microsoft Storage Port Driver
    LegalCopyright:    Microsoft Corporation. All rights reserved.



n

Free Windows Admin Tool Kit Click here and download it now

July 18th, 2013 1:32am

ok, your old nVIDIA storage driver (2009!!!) is causing it. Update the driver to fix the crashes:

*******************************************************************************
*                                                                             *
*                        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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

TAG_NOT_DEFINED_c000000f:  FFFFF800BB6C0FB0

LAST_CONTROL_TRANSFER:  from fffff800bb9f2f4b to fffff800bb873440

STACK_TEXT:  
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!KeUpdateTime
hal!HalpTimerClockInterrupt
nt!KiInterruptDispatchNoLockNoEtw
nt!KxWaitForLockOwnerShip
storport!RaidpAdapterTimerDpcRoutine
nt!KiProcessExpiredTimerList
nt!KiExpireTimerTable
nt!KiTimerExpiration
nt!KiRetireDpcList
nt!KiIdleLoop


t!KxWaitForLockOwnerShip+0x28
nt!KiInitialPCR+0x180
fffff800`bb6ba950  fffff880`0128b0b4*** WARNING: Unable to verify timestamp for nvstor64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys
 nvstor64+0x30b4
fffff800`bb6ba958  fffff880`012c87d9 storport!RaidpAdapterTimerDpcRoutine+0x59
fffff800`bb6ba960  fffffa80`042a71a0
fffff800`bb6ba968  fffffa80`04a21c70
fffff800`bb6ba970  fffff800`bb6baa79
     
    Loaded symbol image file: nvstor64.sys
    Image path: nvstor64.sys
    Image name: nvstor64.sys
    Timestamp:        Wed Jul 01 02:21:51 2009 (4A4AAC1F)
    CheckSum:         0003C24D
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    Image name: storport.sys
    Timestamp:        Fri Mar 01 05:58:51 2013 (5130358B)
    CheckSum:         000567FC
    ImageSize:        00055000
    File version:     6.2.9200.16547
    Product version:  6.2.9200.16547
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     storport.sys
    OriginalFilename: storport.sys
    ProductVersion:   6.2.9200.16547
    FileVersion:      6.2.9200.16547 (win8_gdr.130228-1507)
    FileDescription:  Microsoft Storage Port Driver
    LegalCopyright:    Microsoft Corporation. All rights reserved.



n

July 18th, 2013 10:55am

looks like the latest driver is from 2009:

http://www.nvidia.com/object/nforce_vista_win7_64bit_15.49.html

so you should go back to Windows 7 or upgrade the PC (new CPU and motherboard).

Free Windows Admin Tool Kit Click here and download it now

July 18th, 2013 2:46pm

looks like the latest driver is from 2009:

so you should go back to Windows 7 or upgrade the PC (new CPU and motherb

July 18th, 2013 6:13pm

now the version is 10.6.0.22 from 12/09/2011

perhaps now work better

hopefully this new driver helps :)

Free Windows Admin Tool Kit Click here and download it now

July 19th, 2013 1:15am

I suggest a newer machine, your rig is pretty old and driver support may not be available

July 22nd, 2013 2:24pm

This topic is archived. No further replies will be accepted.