Lots of BSOD's with new build

Afran

Afran

Afran

Associate
Joined
6 Oct 2008
Posts
757
When the first BSOD occurred apparently I had a bad page area (see below BSOD), no memory dump and automatic restarts were enabled (I've since disabled) so I couldn't read the blue screen.

The second BSOD indicated the above with the message "PAGE_FAULT_IN_NONPAGED_AREA", I've hopefully fixed this by setting SSD to not have a page file and D drive (my HDD) to be system managed

Following this I installed windows updates and as soon as I hit "Restart Now" I got another BSOD with no text but an error string; 0x0000007E
So I rebooted and got this error INSTANTLY upon loading windows: "SYSTEM_SERVICE_EXCEPTION"
Rebooted again and started writing this thread as this is now the 4-5th BSOD each time with a different error so I'm very confused and unsure how to approach troubleshooting
While typing this thread out, I got yet another BSOD, just an error number thing again; 0x000000BE

This is what's happened so far and I've typed this all out in Safe Mode and done a few things in Safe Mode and it's not crashing so that's a good sign at least right?

Anyway, find it odd 3-4 hours using new system and then this series of constant different BSODS

As said, any help to get to the bottom of this would be much appreciated

Below are the reports from WhoCrashed in spoiler tags...

On Sat 04/01/2014 02:20:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-18049-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xBE (0xFFFFF8A00560E778, 0x80000001E1AB0121, 0xFFFFF88002A2E170, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 04/01/2014 02:20:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFF8A00560E778, 0x80000001E1AB0121, 0xFFFFF88002A2E170, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 04/01/2014 02:12:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-20186-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003400147, 0xFFFFF88008950AC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 04/01/2014 02:10:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-26504-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xC1702)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFF880049EAD28, 0xFFFFF880049EA580)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 04/01/2014 02:00:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-32089-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x20, 0xFFFFF900C1FA88C0, 0xFFFFF900C1FA89C0, 0x2510000F)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Computer ran fine for a while (playing Wildstar beta for a few hours), but now programs constantly crash and have to be ended (skype, firefox etc). Temps are fine. I'm thinking it could be bad memory? I tried to format and reinstall windows 7 but even that BSOD'd with "ntfs.sy PAGE FAULT IN NON PAGED AREA" when in the process of installing.

I'm now trying to reinstall Windows 7 with just 1 stick of memory installed
 
What hardware? the BSOD all seem to revolve around memory and/or file IO so either a faulty/msconfigured HDD/SSD, faulty/misconfigured storage controller or problems between the memory controller and the RAM itself.

Have you checked the system with MemTest to see if its reporting any errors?

The other possibility, though less likely due to the other errors is that its a problem with 2D hardware accelerated surfaces in desktop applications.
 
Thanks for your reply :)

The build is:

Intel Core i5-4670K 3.40GHz (Haswell) Socket LGA1150 Processor
Gigabyte Z87-HD3 Intel Z87 (Socket 1150) DDR3 ATX Motherboard
Seasonic G series 550w '80 Plus Gold' Modular Power Supply
TeamGroup Elite Black 8GB (2x4GB) DDR3 PC3-12800C11 1600MHz Dual Channel Kit (TED38GM1600HC11DC01)
Corsair Carbide 200R Compact ATX Case - Black (CC-9011023-WW)
CoolerCooler Master Hyper 212 Evo CPU Cooler
MSI Radeon R9 280X Gaming Edition OC 3072MB GDDR5 PCI-Express Graphics Card

I was trying to use the SSD with my old installation of Windows 7 from my previous computer. I was thinking it may have been that which was causing the problem but seeing how I still crashed when formatting and reinstalling Windows...

The SSD was working fine before on my previous system so I don't believe that's faulty.
 
If it doesn't crash in safe mode that does tend to point fairly strongly towards device drivers - the most likely being the storage controller (try updating whichever chipset you have the drive(s) plugged into - usually intel or marvell) and one error was in the GPU drivers but thats possibly just due to them being so sensitive to instability in other areas of the system.

I wouldn't rule out memory issues or even a loose SATA lead though - definitely test that RAM and make sure BIOS settings for it are correct.
 
Last edited:
A quick update before I head to bed

After my last post I had constant crashes and BSOD's, to the point that every time I opened Firefox it'd crash, every time I opened Skype it'd crash, nothing would load a second time without rebooting and I was getting a BSOD every 2-3 minutes, as said I even encountered a BSOD (PAGE_FAULT_IN_NONPAGED_AREA again) when I was installing windows which lead me to indeed believe it is a hardware issue, as that's effectively the same as Safe Mode I believe - must have just been lucky to not crash in Safe Mode the 30 odd minutes I spent using it beforehand.

Anyhow, following this I've taken one stick of RAM out so I'm running a single 4GB at this point to rule that out, since setting it up with just the 1 RAM stick I've been able to stay booted for atleast two hours now which let me install Windows 7 so at least now if it happens again I can rule out previous driver conflictions and whatnot relating to not doing a fresh install beforehand.

Unfortunately because the issues didn't start to occur before using the system for 4-5 hours before I can't go right ahead and say it's fixed with the removal of one RAM stick and that the one I removed is faulty; however fingers crossed that that is the case :)

Should it crash again I'll have my brother take a look at the BIOS settings as you've suggested (no idea about that stuff myself) and I've since checked the SATA leads (no issue there)

Edit: Some of BSOD's were repeats of the ones in the original post however a couple new ones appeared, google would indicate they also point to RAM (PFN_LIST_CORRUPT and MEMORY_MANAGEMENT)

One query I did have if someone knows an answer; could it of possibly been my HDD (Drive D, being the secondary drive to my SSD Drive C) causing issues even though I never boot from it? Just because it also has an old installation of windows/chipsets and whatnot from before I upgraded to the SSD; I just use the HDD as an extra drive for downloads/general storage and wonder if that could be causing issues. I've not yet plugged it in (I unplugged it to make sure I format the correct drive for the new windows 7 installation) so want to query that before I go ahead and whack it in again.
 
Last edited:
I suffered from exactly this with effectively a new build, seemingly all memory related but different errors each time. I eventually traced it to bad RAM (also Team Group).
 
Havana_UK said:
I suffered from exactly this with effectively a new build, seemingly all memory related but different errors each time. I eventually traced it to bad RAM (also Team Group).
Click to expand...

I had exact same with my Haswell build but Patriot ram so switched to Corsair all been fine now.See if ram settings are correct and try a BIOS update too though like Rroff mentioned.

Definitely sounds like a faulty stick though but could be wrong.
 
Afran said:
One query I did have if someone knows an answer; could it of possibly been my HDD (Drive D, being the secondary drive to my SSD Drive C) causing issues even though I never boot from it? Just because it also has an old installation of windows/chipsets and whatnot from before I upgraded to the SSD; I just use the HDD as an extra drive for downloads/general storage and wonder if that could be causing issues. I've not yet plugged it in (I unplugged it to make sure I format the correct drive for the new windows 7 installation) so want to query that before I go ahead and whack it in again.
Click to expand...

Unlikely but not impossible - Windows will access certain system files if they are present in the root folder of the HDD - if they are corrupt (or just not what was expected) Windows sometimes doesn't know how to handle it. In the unlikely event of that happening it will usually happen when Windows first becomes aware of the drive either at boot up or when plugged in.

Starting to look more like the RAM is the problem, it might be you just need a BIOS update* or you might need to manual enter the correct RAM settings (might just be as simple as selecting an XMP profile) or it could be one of the sticks is faulty - usually people use http://www.memtest.org/ to test RAM but its not the most straight forward to setup if you've not done it before.

* I wouldn't reccomend doing this while you have potentially faulty RAM in the system however as you could end up bricking the motherboard to.
 
Alright so, will be running with one RAM stick only until Sunday night/Monday morning which will be long enough to tell if this single stick is stable, at which point assuming there has been no BSOD by then I will install the second stick and run them both to see if it remains stable.

Naturally, if I get a BSOD running this single stick before Sunday night/Monday morning, I'll switch it out for the other.

My brother checked the bios settings for RAM and they were auto, which wouldn't show the details he has since corrected them manually according to this website.

All in all, I guess we'll know by next week what exactly the issue is and for now I at least haven't encountered a BSOD for 3 hours lastnight before I went to bed and 3 hours so far today; we'll see how it pans out ;o

(have also left the extra HDD out for now, to rule that out for sure, thanks Rroff)
 
what make/model ssd?

be sure to flash to latest bios for that motherboard,can also enable xmp memory profile for your memory,will help with stability
 
Still no BSOD's with the one memory stick, will take it out tomorrow and switch it for the other one to see if the one not currently installed is faulty; but thus far all good with current stick for about 12 hours of playing games now and 5-6 hours "idle", probably more.

wazza300 said:
what make/model ssd?
Click to expand...

It's the Samsung 840 Basic 240GB
 
could be either a faulty ram stick or simply needs more voltage for the memory controller

enabling xmp profile in the bios might help
 
I had this recently and I couldn't figure out what was wrong - until I changed all the Sata cables and power cables to the hard drives and no problems since could be something simple as that it was for me.
 
Sooo...

Tested one RAM stick for ~40-45 hours, at least half of which gaming and rest running multiple programs, zero issues.

Took that out knowing it's stable, put the other one in instead. BSOD within 5 minutes, reboot just to be sure, BSOD yet again. Looks like RMA time, thanks for the help guys :)
 
Bless you all for this thread... I just spent a week dealing with the same issues, reinstalling Windows, searching for and trying out fixes left, right and centre... until I found this thread and I tried a different pair of RAM sticks, and everything worked perfectly straightaway.

I see TeamGroup RAM was mentioned. Same in my case. However, the other pair that did work was also TeamGroup, same model (Vulcan Orange 2400MHz). So I guess it can happen.

I wouldn't have thought the issue was RAM. Kept thinking it must be Windows installation or Windows Update or drivers related.

Thank you so much. :)
 
You must log in or register to reply here.
Back
Top Bottom