BSOD when uploading file to new NAS

B

bayard

New member
Joined
Mar 19, 2013
Posts
4
Hi guys, I've been having trouble with BSOD with DPS_Watchdog_violation errors last 2 nights. was uploading files to my new NAS from my main computer and I get the BSOD after the file start upload but hangs in the middle of the upload. This started happening after I registered for a domain using synology's application which changed some of my network firewall settings. The NAS is totally fine without any hitch (no reboots/errors). my main comp using window 8 64x. NAS is a synology ds212j with 2 wd red 3tb running raid 1. Haven't seen the BSOD before this on the main computer which has been operational since building about 5 months ago. it does have a samsung ssd 830 - but I double checked to see that the drivers are all updated.

Thanks for any help you guys can provide.
Bayard

View attachment SF_19-03-2013.zip
 
Hi -

Update Intel 82579V Gigabit Network Connection driver - named in 4 of the 5 BSODs -
Code: 
 2: kd> [B]lmvm e1i63x64[/B]
start             end                 module name
fffff880`04c4b000 fffff880`04ca1000   e1i63x64 T (no symbols)           
    Loaded symbol image file: [COLOR=#ff0000]e1i63x64.sys
[/COLOR]    Image path: \SystemRoot\system32\DRIVERS\e1i63x64.sys
    Image name: e1i63x64.sys
    Timestamp:        Wed [COLOR=#ff0000]Feb 29 [/COLOR]22:25:14 [COLOR=#ff0000]2012 [/COLOR](4F4EEC1A)
http://www.sysnative.com/drivers/driver.php?id=e1i63x64.sys


Update NVIDIA HDMI audio if BSODs continue after Intel update. NVIDIA was named in one BSOD -
Code: 
2: kd>[B] lmvm nvhda64v[/B]
start             end                 module name
fffff880`04fc5000 fffff880`04ff7000   nvhda64v T (no symbols)           
    Loaded symbol image file: nvhda64v.sys
    Image path: \SystemRoot\system32\drivers\[COLOR=#FF0000]nv[/COLOR][COLOR=#ff0000]hda64v.sys[/COLOR]
    Image name: nvhda64v.sys
    Timestamp:        Tue [COLOR=#ff0000]Jul 03 [/color]11:25:04 [COLOR=#ff0000]2012 [/COLOR](4FF30ED0)
    CheckSum:         00035E14
    ImageSize:        00032000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
http://www.sysnative.com/drivers/driver.php?id=nvhda64v.sys

Regards. . .

jcgriff2

`
 
Last edited:
Hi Jcgriff2,

Thanks for the help. Alias the BSOD still happening despite the 2 driver updates.

updated with this gigabyte driver from intel

File name:
PROWinx64.exe		Version:
18.1
blank.gif




Date:
03/08/2013		Status:
Latest
Size:
33.79 MB		Language:

English



and updated the nvidia driver with latest driver.




new dump file is here if you don't mind looking at it for me.

View attachment SF_19-03-2013.zip


Thanks for any help!
bayard
 
Hi -

The updated Intel driver named as probable cause in both -
Code: 
[font=lucida console]e1c63x64.sys        Thu Feb 21 00:31:49 2013 (5125B145)[/font]
http://www.sysnative.com/drivers/driver.php?id=e1c63x64.sys

Both BSODs had bugcheck 0x133 = DPC_WATCHDOG_VIOLATION, which occurred because a single long-running DPC (Deferred Procedure Call) exceeded its alloted time.

This only occurs when uploading large files? How large?

Run - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Upon BSOD, run - https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html

^^^ output contains much more info than the prior zips & may yield a clue.

Regards. . .

jcgriff2


BSOD SUMMARY
Code: 
[font=lucida console]
Debug session time: Tue Mar 19 23:00:19.293 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031913-11078-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:05:48.921
*** WARNING: Unable to verify timestamp for e1c63x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c63x64.sys
Probably caused by : e1c63x64.sys ( e1c63x64+23d84 )
BugCheck 133, {0, 281, 280, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x133_DPC_e1c63x64+23d84
MaxSpeed:     3500
CurrentSpeed: 3510
BiosVersion = 1708
BiosReleaseDate = 11/09/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Tue Mar 19 22:54:02.340 2013 (UTC - 4:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031913-10734-01.dmp]
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
System Uptime: 0 days 0:03:09.969
*** WARNING: Unable to verify timestamp for e1c63x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c63x64.sys
Probably caused by : e1c63x64.sys ( e1c63x64+23d84 )
BugCheck 133, {0, 281, 280, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Bugcheck code 00000133
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x133_DPC_e1c63x64+23d84
MaxSpeed:     3500
CurrentSpeed: 3510
BiosVersion = 1708
BiosReleaseDate = 11/09/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


         
       J. C. Griffith, Microsoft MVP (jcgriff2)  
             
           [url]http://mvp.microsoft.com/profiles/Griffith[/url]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
 
Hi jcgriff2,

Thanks for the info. will try the drive verifier tonight after the houston NBA game.

The files i tried uploading are around 1-5gig. not super large files specially going via a home network. all previous files i uploaded were 300-500megs previous to the larger files.

Thanks for the help so far.
Bayard
 
No NAS here, but it does appear that a timeout of some sort is occurring with the larger files.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top