Windows 7 3 BSOD Problems - please help

N

NicholasH

New Member
Joined
Apr 2, 2016
Messages
14
Here are my computer specs:

ASRock z170 PRO4S Motherboard
Nvidia Gefore GTX 970 Graphics Card
Intel i7-6700 processor
16GB DDR4 Ram (2x8GB)
240GB SanDisk SSD & 1TB HDD (forget brand)
RetailPlus 700w PSU


Windows 7 professional (version 6.1.7601 service pack 1 build 7601)
Kaspersky Anti-virus Software
BIOS Version/Date: American Megatrends Inc. P1.40, 13/08/2015
SMBIOS VERSION: 2.8

PROBLEMS: 0x00000024 (NTFS)
0x0000001a (Memory Management)
0x00000050 (Page Fault)


I bought a brand new computer 3 days ago now and have been getting blue screens at (what seems to be) random times.

I keep taking it back to the privately owned gaming system store in the small city where I live but it will never seem to blue screen when I'm trying to make it happen for him. He SHOULD be able to tell me something about these error messages but he doesn't seem to be much help so I feel like this is my last chance.


I will attach a compressed folder of the 3 dmp files
 

Attachments

Solution
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 13646000, fffff70001100c20, 8f300001449fcc46}

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

Followup: MachineOwner
Hi,
all three dump files were different. You had a bugcheck 24 which can mean NTFS issues, bugcheck 50 which causes...
Sort by date Sort by votes
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.
 
Upvote 0 Downvote
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
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
You must log in or register to reply here.