unexus Posted January 8, 2016 Posted January 8, 2016 Hi All, I've had a major problem this week following a WSUS deployment of KB3102429 (Azerbaijani Manat and Georgian Lari currency symbols). The update has resulted in continual reboot/BSOD. On Win7 64 bit, this is a 0x50 (STOP) error (win32k.dll). On Win7 32bit, I have seen 0x19 BAD POOL HEADER errors. I can't find any reports of this on google, however, there is a DELL Support KB article reporting this patch causes the same problem on Server 2012 https://support.software.dell.com/kb/184032 Has anyone else hit this problem? Thanks, Keith.
unexus Posted January 8, 2016 Author Posted January 8, 2016 Sorry - Title should say BSOD not BYOD - could a moderator edit this please. Thanks.
DJ-1701 Posted January 8, 2016 Posted January 8, 2016 Sorry - Title should say BSOD not BYOD - could a moderator edit this please. Thanks. Was going to say that was impressive. Seriously though no BSOD since the update was installed on our machines last month. Have you set WSUS to revoke it for the time being? 1
unexus Posted January 8, 2016 Author Posted January 8, 2016 Yes. I have declined it for all platforms in WSUS, unfortunately, it got out to quite a few machines before I was able to do that. We have ~700 desktops. It has Blue screened 50+ machines and on different hardware too (some HP and some Stone). I have reproduced the problem so I know it it that update. It's obviously not a widespread problem as there is veryt little on google other than that Dell KB article. I guess I've just been unlucky.
DJ-1701 Posted January 8, 2016 Posted January 8, 2016 Yes. I have declined it for all platforms in WSUS, unfortunately, it got out to quite a few machines before I was able to do that. We have ~700 desktops. It has Blue screened 50+ machines and on different hardware too (some HP and some Stone). I have reproduced the problem so I know it it that update. It's obviously not a widespread problem as there is veryt little on google other than that Dell KB article. I guess I've just been unlucky. I noticed you meantioned you declined it, but just checking, did you right click it and select the 'Approved for Removal' option? As that could save a lot of manual work. 1
unexus Posted January 8, 2016 Author Posted January 8, 2016 I noticed you meantioned you declined it, but just checking, did you right click it and select the 'Approved for Removal' option? As that could save a lot of manual work. I have now Thanks.
john Posted January 8, 2016 Posted January 8, 2016 Sorry - Title should say BSOD not BYOD - could a moderator edit this please. Thanks. Done, please report your own post in future to ensure a mod notices the thread to sort this out as we may miss posts like this as we all get an email alert then and one of the team will do it
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now