FileServer BSOD.... HELP!

[abillybob]

Ok so for a while now (Since I left) our FileServer has been playing up but now it's started to BSOD intermittently. I've ran BlueScreen Viewer and this is what is on there

 

Now I know that mrxsmb10.sys has something to do with SMB shares and I can't find anything that has been changed except for the person who was filling in for me while I left for my other job has created this strange registry update in GP, but I have no idea what it means...

 

I have also scanned through event viewer and found the following errors/warnings that might have some relevance

 

Any help would be most appreciated, I'm a bit stuck on what to do really, I've tried various hot fixes but nothing has seemed to resolve the issue and now the file server is becoming corrupt and I'm worried something drastic is about to happen.

 

Thanks

[X-13]

"Ntfsdisable8dot3namecreation"

 

Found it here: https://support.microsoft.com/en-us/kb/121007

 

It's old, but it supposedly speeds up your network... [network is probably the wrong word. I'm tired and don't care.]

 

HOWEVER I'm also seeing a lot of "this will wreck your network"

 

Out of curiosity, can you see when that was changed?

Edited April 29, 2015 by X-13

[abillybob]

"Ntfsdisable8dot3namecreation"

 

Found it here: https://support.microsoft.com/en-us/kb/121007

 

It's old, but it supposedly speeds up your network... [network is probably the wrong word. I'm tired and don't care.]

 

HOWEVER I'm also seeing a lot of "this will wreck your network"

 

Out of curiosity, can you see when that was changed?

 

Ahh cheers mate!

 

No I can't see when the GP was added but what I do know is everything was working fine up to the point I left and this GP was added within the two months I was gone. Sometime around October I think!?

[JRowley]

Well, I would disable that GPO for the time being as it's the only thing that appears to have changed. It may be causing unexpected results.

[abillybob]

Well, I would disable that GPO for the time being as it's the only thing that appears to have changed. It may be causing unexpected results.

 

But because it's a registry edit don't I have to apply another GPO that counteracts that GP so instead of setting it to "Enable" for example I set it do "Disable"? Sorry might be being stupid but wanted to check!

[JRowley]

But because it's a registry edit don't I have to apply another GPO that counteracts that GP so instead of setting it to "Enable" for example I set it do "Disable"? Sorry might be being stupid but wanted to check!

 

Actually, more research first!

Edited April 29, 2015 by JRowley

[abillybob]

Errr, yeah good point, you should change the value data to 0.

 

Fingers crossed this sorts it Thanks!

[JRowley]

Actually change it back, to 1, I need to do more research, the GPO may not have been doing anything and could have been created for no reason.

 

Edit: My DCs and PC has it set to 2, which is this - "2 - Set 8dot3 name creation on a per volume basis"

 

I don't know how you want to proceed. He shouldn't have changed it in the first place, the file system is not something you want to be screwing with.

Edited April 29, 2015 by JRowley