BSOD after clean install of W8.1

Dirk Diggler · 6 Apr 2015 at 23:32

I've done a clean install of 8.1, and I got a couple of BSOD when launching Crysis 3 tonight. GPU's are mildly OC'd and CPU is 4.6 @ 1.25 vcore.

I run Memtest for a couple of hours with no errors.

Any ideas?

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 06/04/2015 19:21:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040615-5296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xDE (0x2, 0xFFFFC000B2C4E928, 0xFFFFC000B2C4E829, 0x1B6EE98C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
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 driver has corrupted pool memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 06/04/2015 19:21:40 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAF002)
Bugcheck code: 0xDE (0x2, 0xFFFFC000B2C4E928, 0xFFFFC000B2C4E829, 0x1B6EE98C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
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.

On Mon 06/04/2015 18:43:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040615-5218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1A (0x402, 0xFFFFC0006E4E9138, 0x1B6C198C0, 0xFFFFC000628BE4D9)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.

Quartz · 7 Apr 2015 at 00:00

The first thing to do is remove the overclocks. If the problem persists run a decent memory checking utility like Prime95. Memtest has repeatedly failed me.

Dirk Diggler · 7 Apr 2015 at 09:54

Can I rule out the GPU overclocks or should I stick them back to stock too?

Quartz · 7 Apr 2015 at 10:29

Put everything as stock to start with.

Undesirable · 7 Apr 2015 at 14:12

If it were a GPU overclocking issue, you would likely see graphical artifacts or blank screen before anything else. Memory tests aren't the be all and end all by any means for stability testing your entire system. You probably need slightly more volts to the CPU in one area or another.

Dirk Diggler · 7 Apr 2015 at 14:19

I've put the CPU to stock settings and so far so good. I might just leave it at stock as it boosts to 4.4 and I only had it set at 4.6. Not a great deal of difference really.

Dirk Diggler · 17 Apr 2015 at 10:14

So, I had it stock all this time with no problems, and I put it back to my 4.6 OC and within 24 hours I get a BSOD...

On Thu 16/04/2015 22:46:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041615-6562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x1A (0x401, 0xFFFFF6FB7DA00FC0, 0x6900000065533867, 0xFFFFF6FB7DA00EC0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe

Clearly it's the memory. I've went in to BIOS to suss my options and have changed the following setting.

I'm not sure what this does? :confused:

...

ED209 · 17 Apr 2015 at 12:00

I would run prime95 and see if it reports back any issues with the ram.

never seen them options before in the bios but just read the description on the top right.

maybe change it to normal and see if the problems still happen.

Dirk Diggler · 17 Apr 2015 at 12:26

ED209 said:
I would run prime95 and see if it reports back any issues with the ram.

never seen them options before in the bios but just read the description on the top right.

maybe change it to normal and see if the problems still happen.

The problem was happening in normal mode. I really don't want to run Prime95 as it totally cooks the CPU.

Dirk Diggler · 17 Apr 2015 at 21:23

I just got a Memory Management BSOD when I tried to do a reboot from idle desktop. I'm back on optimised defaults.

I'm not sure how to troubleshoot this, so unless one of you Guru's can offer a suggestion I'm afraid it's stock settings for me.

SamyBoy13 · 18 Apr 2015 at 11:36

I would run memtest86 for 30min (test one stick of ram at the time). I got that error and it turn up to be my ram being faulty. If this shows no errors maybe try to bump up ram voltage by 0.05 manualy so if your ram is rated at 1.5v go up to 1.55 but if its 1.60-1.65 dont turn it up. Hope this helps

Dirk Diggler · 18 Apr 2015 at 16:16

Cheers, will try that out.

Dirk Diggler · 18 Apr 2015 at 22:44

Well, I ran memtest on each stick for over 2 hours and no errors.

I'll up the voltage on the ram and see if that helps. It's set to "auto" right now so it wouldn't surprise me if the BIOS is doing something with it. As it's a Z87 mobo I've had to flash a beta BIOS to get support for Devils Canyon so that could certainly be the issue.

Dirk Diggler · 6 May 2015 at 21:35

I've upped the RAM volts to 1.55v. How high can I safely set this voltage?

I've also noticed that this MEMORY MANAGEMENT error happens mostly when I quit a game I've been playing for a little while. :confused:

Dirk Diggler · 25 May 2015 at 10:19

I'm still plugging away at this. I've done a basic 4.4Ghz overclock with 1.2v. I ran 50 passes of IBT on very high, with no errors. I was then running P95 for a few hours and had decided this OC was looking OK.

As soon as I hit the stop button on P95 I got the MEMORY_MANAGEMENT BSOD. It really does seem to be happening when the CPU goes from full load to idle. However, it never happens with BIOS defaults.

Should I chalk this up to having a beta BIOS on a Z87 board hosting a Z97 chip? Are there further tests I could do?

I think I'm stuck at stock with this CPU unless someone more knowledgeable than me can assist.

Quartz · 25 May 2015 at 13:40

Overclocks are never guaranteed.

Dirk Diggler · 25 May 2015 at 15:45

I'm running each RAM stick through memtest for a couple of hours just to double check, but I'm just about convinced it's an issue with Win 8.1. I'm not going to bother with a re-installation as I'll be upgrading to Win 10 soon enough.

Krazeyivan · 25 May 2015 at 16:57

Check the error log for WHEA errors.
They are considered a sign by some people that your overclock is unstable.

To get to the section that contacts the WHEA Errors. load up Event Viewer. On the left, under "Event Viewer (Local)" expand "Applications and Services", then "Microsoft", then "Windows", then "Kernel-WHEA", and then finally "Errors".

In the top center frame of the window, you should see your WHEA Errors.

Sometimes even if your machine is running OK - check this section it can let you know if your OC is unstable - I use it to check how low I can go for the CPU voltage.

Dirk Diggler · 25 May 2015 at 18:54

No WHEA errors.

I have just noticed that the XMP profile set in BIOS is changing some settings. With optimised defaults, it is disabled but with all my overclocks it is enabled on profile 1. I can't believe I didn't check this before.

Now retesting with XMP disabled...