Server 2012 R2 - BSODing Every 10-30 Minutes

EDIT: Issue came back 02/17/15. New info in post on next page (I'd give a link directly to it, but I still can't post fricken' links...).

Hello all!

The server we are running here for our computer lab domain controller is repeatedly BSOD'ing (about ever 10-30 minutes). For a while I thought it was a hardware issue (it would just suddenly restart, no BSOD), so I've been swapping out parts one-by-one to figure out what is causing it. However, after another Googling session it turns out that there was a setting that suppressed the BSOD, and instead made the computer just restart. After changing the setting, the BSOD is coming up. I have Googled the codes for a while, but the best I can come up with is that it's a driver issue, and I need to go through the crash dumps, or put the crash dumps up on a forum for someone to look through.

As I have no idea what I am looking for, I am going with the latter option.

I ran "dm log collector" as was suggested in a how-to on another forum. The resulting .zip file can be found here:
[unfortunately, I only have two posts, so am unable to post links... So, I will break up the URL in order to post it... Just remove the spaces around the "[remove]" brackets]
www [remove] . [remove] dropbox [remove] . [remove] com/s/ootv3fggoqms24c/PMASRV1-Wed_02_04_2015_125409_26.zip?dl=0


Also, the various codes that come up on the BSOD screen are:
IRQL_NOT_LESS_OR_EQUAL
UNEXPECTED_KERNEL_MODE_TRAP
DRIVER_IRQL_NOT_LESS_OR_EQUAL

Also, the following are the two kinds of messages that show up in WhoCrashed are:

On Wed 2/4/2015 1:30:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSetEnvironmentVariableEx+0x988)
Bugcheck code: 0xD1 (0xFFFFF8431333CA78, 0xF, 0x8, 0xFFFFF8431333CA78)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

...and...

On Wed 2/4/2015 12:53:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020415-74109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFF80248047000, 0xF, 0x0, 0xFFFFF80246BED820)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.


Any suggestions?

Thanks!
ElectroPulse

 

Thank you for the reply!

Nope, only using onboard graphics. For future reference, what points toward graphics being the issue?

When looking in device manager, I did notice a device called "Coprocessor" with an exclamation mark... I looked this up, and it looks like it might have something to do with graphics. This is an old motherboard, so finding drivers is proving to be difficult, and what drivers I have found are for Windows XP. I'll keep looking, and perhaps try the XP drivers on there as well.

What I find strange is that I installed this a year and a half ago, then it started having these issues out of the blue with no modifications... That's one reason that I was initially thinking it was hardware failure.

 

Thank you for the reply!

Just 0xD1 and 0xA. I haven't seen any other ones so far.

Overheating was one of the first things I checked; the CPU is usually sitting around 36C-38C. When I checked this, I believe I ran Prime95 on it to test it as well without issue (I was testing a couple of computers for overheating issues around the same time... I may run it again just to be sure).

I also ran Memtest86+ for a couple of passes, no errors found.

 

Unfortunately, no... I don't believe we have any other CPUs that are compatible in other computers here. And due to our location (Palau) getting a second one to just test out whether it works would take a rather long time.

I'm in the process of downloading the video drivers... I'll probably have them downloaded by tomorrow (our internet is uber-slow).

 

Thank you for the replies!

Well, after having messed around with a bunch of things, the problem appeared to fix itself... I decided not to upgrade the video drivers at the time, as I was afraid of bringing the problem back.

Then, last night it started happening again following a power failure. No other changes had been made.

Today I installed the Nvidia drivers (both video card and NIC) that had been previously downloaded, but that hasn't helped. The "Co-processor" device no longer has an exclamation mark next to it.

I have also tried swapping the power supply... Didn't fix it.

As requested, here are the ten most recent minidump files (same drill as the OP, remove the [remove] brackets to get the URL): www [remove] . [remove] dropbox [remove] . [remove]/s/ab6zt7qjj14z7pa/Minidump.zip?dl=0

We will hopefully be receiving some new servers in the next month or so, so at this point I am just trying to keep this one running and usable until then.

One thing that I don't remember whether I mentioned, is it stays up just fine in safe mode... It's just when I start it up normally that it has problems. If there's a way that I can selectively enable the services to run for just DNS, active directory, group policy, and file sharing in "Safe Mode with Networking," then I think we could get by until the servers get here. At this point, I'm about to just grab one of the computer lab computers and use it as the server...

Also, as requested, the system specs:
Intel Pentium D 3.2ghz
Mobo: MSI P6NGM2 (MSI-7518 Rev. 1.0)
BIOS Version: v2.61, drives set to IDE (one drive is connected with IDE, the other with SATA)
Memory: 2x2GB PC2 6400, OCZ2N800SR4GK (memtest86+ shows no errors)
HDD: WD Caviar WD400BB 40.0 (OS), WD WD1600AAJS 160GB (Data)
PSU: GTR LC-8500BTX (PTX-500M)
Optical drive: Compaq DVD-116ME


Thanks!

 

Thank you for the reply!

No, actually I'm in Palau... It's a small island country east of the Philippines

I'll give that a try... If that doesn't work, I'm just at the point of taking one of the computer lab computers and installing it on there, then figuring out how to migrate all of my settings over.

As for system specs, check my previous post (last one before yours). Video card and NIC are onboard.

 

Thank you for the reply!

I just checked the timestamps on nvmf6264.sys and nvlddmkm.sys, and they were the drivers that were updated yesterday morning with no effect (BSODing happened before I updated those, and was still happening after). I also tried sfc scanfile, and sfc verifyfile, and it "did not find any integrity violations."

So, that's baffling... I am beginning to wonder if it is indeed a hardware issue (video/NIC related messages would point to perhaps the motherboard).

However, as mysteriously as the BSODs came, they went. Checking the crash dumps, it looks like yesterday a couple hours after I stopped working on it, the BSODs subsided. The server is currently stable. Now that the server is up consistently enough, I am going to look into trying to migrate all the settings over to another computer we have here, to avoid having this issue crop up again... The other computer is less powerful, but should fulfill our needs until we can get some actual server hardware in here.

Thank you everyone for the time and replies!