I have a 2012 server that will bsod when I try to copy data over the network. It will drop anywhere from 10 minutes to an hour of copying data. it has never done this before and I've copied a lot of data off of it before. I could sure use some help figuring this one out.
The most recent .dmp files seem to show Probably caused by : ntkrnlmp.exe, but that's not very helpful from what I have seen around the web. I have made sure that the RAID and network drivers and firmware are up to date.
Diag file is attached.
Hi BoomSchtick,
Welcome to the 10blog
Please run the DM Log Collector again and upload a new zip file, the current attached zip file misses some important files including the most important onces: dump files.
SBUAADRAPER-Sat_05_28_2016_124821_40.zip
I was wondering why it was so small. I checked this one and it has the log files.
The size varies a lot from a few MB's to a few hundred KB, the size of 992.4KB is kinda average with the recent uploaded zip files.
An interesting event log that fits with your problem description, it started to occur 2 months ago.
Please run chkdsk in an admin command prompt on the hard disk and upload the log file as a text file
Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 blog
Run following command:Code:chkdsk C: /rCode:Event[52476]: Log Name: System disk Date: 2016-05-27T17:18:23.506 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: SBUAADRAPER.Handstands.local Description: An error was detected on device DeviceHarddisk0DR0 during a paging operation. Event[10366]: Log Name: System disk Date: 2016-03-04T17:23:05.131 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: SBUAADRAPER.Handstands.local Description: An error was detected on device DeviceHarddisk0DR0 during a paging operation.
Here's the result of the log entry for the c: scan:
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
378368 file records processed. File verification completed.
6872 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
447446 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered.
Stage 3: Examining security descriptors ...
Cleaning up 472 unused index entries from index $SII of file 0x9.
Cleaning up 472 unused index entries from index $SDH of file 0x9.
Cleaning up 472 unused security descriptors.
Security descriptor verification completed.
34540 data files processed. CHKDSK is verifying Usn Journal...
542565952 USN bytes processed. Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
378352 files processed. File data verification completed.
Stage 5: Looking for bad, free clusters ...
15590812 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
No further action is required.
94011391 KB total disk space.
30497632 KB in 321564 files.
171388 KB in 34541 indexes.
0 KB in bad sectors.
979119 KB in use by the system.
65536 KB occupied by the log file.
62363252 KB available on disk.
4096 bytes in each allocation unit.
23502847 total allocation units on disk.
15590813 allocation units available on disk.
Internal Info:
00 c6 05 00 15 6f 05 00 70 eb 0a 00 00 00 00 00 .....o..p.......
f4 00 00 00 41 01 00 00 00 00 00 00 00 00 00 00 ....A...........
Windows has finished checking your disk.
Please wait while your computer restarts.
It took a long time to run and finish.
That looks good
I would suggest that you run the command again when you have time for it, for now please try to copy files again to see if the same problem occurs.
