BSOD several times bugcheck 0x00000050 in Event log every time

nmc001 · 24 Jan 2014

I bought a new computer a few weeks ago and installed the old copy of Windows 7 from my previous PC.

I set it up over the last few weeks, added more disk drives and started using it a few days ago.

After it crashed I opened the event viewer and I can see some bugcheck events.

This is what the bugcheck events contain, the first two happened today :

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffffffffffffd0, 0x0000000000000001, 0xfffff80002ed646c, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002e7a009, 0xfffff880089b63e0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff900d28f1db0, 0x0000000000000000, 0xfffff960000e9c5c, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff80002ca7be5, 0xfffff88007dbae10, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

I created the zip file as requested.

Any ideas as to what might be causing this ? I installed all the drivers that came with the system.

Thanks !

Edit :

This happened while I was using the computer running a whole bunch of programs and once while it was doing nothing overnight. There were still lots of programs open on it during the overnight crash including vmware which itself had a bunch of programs running inside it.

Arc · 24 Jan 2014

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

Also, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

nmc001 · 24 Jan 2014

Ok, thanks - waiting for the next BSOD now.

nmc001 · 05 Feb 2014

I've had a few issues with my PC since I made my last upload.

The minidumps have now been created and I've attached a new zip file using the batch file tool from 'Option 2'

I've uploaded it as an attachment to this post, hopefully this contains some information which will help to identify the issue.

I ran a memory test from a bootable USB drive and it didn't detect any errors. This BSOD only appears to happen every few days and I went several days without having one.

I might add that I don't use this PC like a normal computer. I generally only run a couple of programs, one of them being TrueCrypt and the other VMWare. Inside the Virtual Machine I do all my work on the rest of the programs I use.

Thanks !

Neil

Arc · 05 Feb 2014

A lot of drivers are failing (network, display, storage controller), but first of all test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

Will decide the next course of action seeing the results.
____________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1920250e, 2, 0, fffff88001970092}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000001920250e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001970092, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b60e8
GetUlongFromAddress: unable to read from fffff800030b6198
 000000001920250e Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!RtlGetNextExpiredTimerWheelEntry+83
fffff880`01970092 418b5104        mov     edx,dword ptr [r9+4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


STACK_COMMAND:  .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !NETIO
    fffff88001970020 - NETIO!RtlGetNextExpiredTimerWheelEntry+10
    [ 41:49 ]
1 error : !NETIO (fffff88001970020)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_one_bit

FAILURE_ID_HASH:  {2dbb898e-c425-bad1-90fe-71c78117521f}

Followup: memory_corruption
---------

nmc001 · 06 Feb 2014

I ran the memory scan for 9 hours and 6 minutes overnight and it found no errors during that time.

It appears to only have completed 2 full passes during this time.

Maybe that's because there's a lot of memory there ? 32 GB is quite a lot I guess.

I've attached a photo of what was on the screen when I woke up today, there were no errors reported.

The memory test page mentioned running the test for 7 passes - this is would take several days to complete.

Is it normal for a scan of 32GB to take this long ? Only 2 passes in 9 hours ?

Thanks

Arc · 06 Feb 2014

32 GBs are too big .... it will take a very long time to complete 8 passes. But memtest cannot interpreted at less then 8 passes unfortunately.

nmc001 · 06 Feb 2014

I still have my old computer which has never had a BSOD on it.

That has 16 GB of RAM in it now - 4x4GB.

I could take the 16 GB out of the old PC and put the newer 4x8GB dimms in there

If I run the full 8 pass memory test on the older computer for a few days until it completes do you think this will help ? I don't need to use this old computer for anything at the moment so I can run this for as long as it takes.

I guess if the memory tests out ok on the old PC then it should prove that it's ok and the problem must be something else ?

The Motherboard on my old PC is a Gigabyte ga-z68xp-ud5

Is this worth doing ?

Arc · 06 Feb 2014

May be it will do a partial job only; because a RAM error occurs not only due to a failing RAM stick, but also for a failing DIMM slot. If you test the RAMs in a different computer, the chance of testing the slots will not be there.

It is also seen that some boards fail to work properly when all the slots are occupied, and making one slot free keeps it stable.

I am asking for the RAM test at first, because it shows a memory corruption as prima facie .... but it may be caused by any failing driver too. But that tests should be taken later, after completing memtest and if it free from errors in all respects.

I hope now you understand why I am saying for the RAM tests.

nmc001 · 06 Feb 2014

Ok, I have an idea. I'm going to remove the 32 GB of RAM from my new PC and replace it with the 16 GB of RAM from the old PC. I never had any issues with this old PC and it worked perfectly for about 2 years. I'll then wait and see if I continue to get the BSOD's while it's using the old RAM.

I'll also run a test on the new 32 GB of RAM while it's installed in the old PC. I'm going to start this now as it could take a few days.

I'll update the status of this in a few days depending on what happens.

Thanks !