BSOD running Veeam backup copies on large files

I have a HP Proliant N36L running WIndows 2012 R2 currently with an intel proliant pro/1000 NIC, acting as a repository for Veeam Backup copies running at a remote site. Since Xmas as soon as it starts to process our large copies (500mb or more) it BSOD with a memory corruption. Smaller backup copies work absolutely fine.
When it started all investigation was pointing to the onboard Broadcomm NIC which has been disabled & replace with the Intel Pro. Driver are as up to date as I can get them
Microsoft (R) Windows Debugger Version 10.0.17074.1002 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\richard\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (2 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 9600.18821.amd64fre.winblue_ltsb.170914-0600
Machine Name:
Kernel base = 0xfffff800`b7c15000 PsLoadedModuleList = 0xfffff800`b7ee7650
Debug session time: Thu Feb  1 12:51:03.581 2018 (UTC + 0:00)
System Uptime: 0 days 1:38:47.698
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`78983018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {2b3855bfdbb3, 2, 0, fffff801ed0b421a}

Probably caused by : memory_corruption

Followup:     memory_corruption
---------

nt!KeBugCheckEx:
fffff800`b7d62ba0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd001`7ad8bd60=000000000000000a

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Richard GrayIT & QA ManagerAsked:
Who is Participating?
 
Richard GrayIT & QA ManagerAuthor Commented:
UPDATE
I ran HPE Diagnostics & 17 issues were found. Fixed then & updated the bios. Ran backup copies again. Ones up to 600gb ran ok, but when I ran either of the 2 BIG ones of 1.4 & 4tb respectively, they both again BSOD ! I reinstalled the transport & the accelorators for Veeam but still no joy.

After a bit more investigation, there is quite a bit around about Windows 2012 R2 having issues on the slightly older HP Micro server platforms, So decided to bite the bullet, & rebuild the box with WIndows 10. So far all backup copies I have tried have run. The larger ones are running now & have been for a few hours & have not crashed the machine, whereas before they would have done as soon as they got to the larger disks
0
 
Dariusz TykaICT Infrastructure Specialist Senior Commented:
Have you tried to reseat memory modules? Have you tested memory using for example MemTest86+ to check if all modules are OK?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Update all the firmware on the server, and run the HPE diagnostics.
0
 
Richard GrayIT & QA ManagerAuthor Commented:
Thank you gentlemen... I'm out for today & tomorrow will have a go Thursday & update you with the results
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
HP Proliant N36L is rather old, not sure it even supports Windows 10!

it was questionable at the time of release if it supported 2012 R2!
0
 
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: Richard Gray (https:#a42463617)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.