3 BSOD Problems - please help

kemical

Windows Forum Admin
Staff member
Premium Supporter
#21
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff680000bb950, e7c00001faf2f824, fffff6800006ab51}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6071 )

Followup: MachineOwner
Hi,
although it seems Defender was running at the time of BSOD I don't think it was the cause otherwise it would have appeared here :
Code:
FAILURE_ID_HASH_STRING:  km:x64_0x1a_411_nt!_??_::fnodobfm::_string_+6071
BiosVersion = P1.40
BiosReleaseDate = 08/13/2015
BaseBoardManufacturer = ASRock
BaseBoardProduct = Z170 Pro4S

I see your Bios is still at v1.40. Later versions have stability updates (especially version 1.90) and before you buy some more RAM I would update the bios. If your not too familiar with the process ask your engineer to update it for you.

The other dump file was for your gpu driver and it might be worth removing the gpu driver using the DDU or Display driver uninstaller. It does this in safe mode and makes sure everything is cleaned out thoroughly. Running it in safe mode if the best way to use it.
Display Driver Uninstaller (DDU) V15.7.5.4 Released. - Wagnardmobile Forum

Post any new dump files.
 


#22
I returned the whole system and went to a better gaming system store and got setup with an intel 6600k and a gtx 970. This one is liquid cooled though and I got better pricing. Everything is working out great. On the old system i was told I had very cheap PSU, RAM and a shitty ASrock version of the z170 board. I changed everything and finally the microsoft specialist said there was a computation error on the CPU and it couldnt do a simple computation. I asked him why he didnt do this in the first place and he said it wouldnt be possible with my old PSU cause it wasnt good enough. I think i smell some BS. Wish I had avoided the old purchase all together but there was no way of knowing it would turn out like this. Just letting you know things turned out for the better
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#23
Hi Nicholas,
I did wonder how you'd got on and I'm glad to hear you got better value for your money.. I think your right about the smell of BS too. ;) Thank you for the update, best of luck and if anything crops up again just post back.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top