Multiple BSOD 0x0a, 0x1a, 0x4e, 0x50, 0x3b (IRQL, SYS_SERV_EXC, etc)

skywalker89 · 28 Jan 2015

Hi,

I have a Dell Optiplex 9020 Lab with about 30 computers in there. The computers are running Windows 7 64 bit. There is one computer that has about 5 different types of bluescreens happening over the last few months. I attached a SF Diag Tool Zip. Any help on what could be the problem? I have run a system diagnostic test by Dell and it has passed perfectly.

koolkat77 · 29 Jan 2015

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\skywalker89\SF_28-01-2015\012715-14851-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`0325a890
Debug session time: Wed Jan 28 01:06:13.285 2015 (UTC + 6:00)
System Uptime: 0 days 0:00:30.081
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {1236, fffffa800b232ed0, fffffa800b232f60, 188c0d}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )

Followup: MachineOwner
---------

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000001236, The subtype of the bugcheck.
Arg2: fffffa800b232ed0
Arg3: fffffa800b232f60
Arg4: 0000000000188c0d

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


BUGCHECK_STR:  0x1a_1236

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff80003185d2b to fffff8000308de80

STACK_TEXT:  
fffff880`03d78948 fffff800`03185d2b : 00000000`0000001a 00000000`00001236 fffffa80`0b232ed0 fffffa80`0b232f60 : nt!KeBugCheckEx
fffff880`03d78950 fffff880`0178eeb2 : 00000000`00001000 fffffa80`0b232ed0 fffffa80`09a45118 00000000`0000055e : nt!MmFreePagesFromMdl+0x31b
fffff880`03d789b0 fffff880`017908a8 : 00000000`00000000 fffffa80`0b23d628 fffffa80`0b20ec10 fffffa80`0b23d000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e
fffff880`03d78a10 fffff880`01799623 : 00000000`0000000a 00000000`00000002 fffffa80`0b20ec10 fffffa80`09a450b0 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageRemove+0x398
fffff880`03d78b40 fffff880`0179841a : fffffa80`0b20ec10 00000000`00000080 00000000`00000080 fffffa80`09a45f88 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x22f
fffff880`03d78ba0 fffff800`0332a0ca : 00000000`00000000 fffff880`00000000 fffffa80`074c2b50 fffffa80`0670b040 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`03d78c00 fffff800`0307ebe6 : fffff880`009cf180 fffffa80`074c2b50 fffff880`009da0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03d78c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e
fffff880`0178eeb2 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

IMAGE_VERSION:  6.1.7601.17514

FAILURE_BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_1236_rdyboost!st_store_smd_traits_::streleaseregion+4e

FAILURE_ID_HASH:  {81cb8e48-f1c5-925d-d95a-c02ba121cec3}

Followup: MachineOwner
---------

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Memtest should be done overnight.

skywalker89 · 30 Jan 2015

I ran the Memtest86+ and it found errors immediately, literally thousands of errors were shown. So to narrow down the issue, I removed one of the two 4GB ram sticks and just tested one single stick. The first one returned no errors after about 8 or 9 passes. Then I tested the second ram stick by itself and thousands of errors came up almost immediately. So I'm very positive it's a bad stick. Then I decided to use Windows Memory Diagnostic Tool and it found errors very quickly too.

Just to cover all options, I even ran Dell Diagnostic test tool and during the memory test a warning message popped up and said the warnings or errors were corrected. The test continued with no further warnings or faults. All these tests were being done with just the suspected stick that threw thousands of errors. Then I tried testing the single stick with MemTest86+ again, this time the testing didn't throw thousands of errors. Instead, has run smoothly without any errors, until pass 2 Test #9, there was one error. I still believe this stick is bad, but it does confuse me why the first couple tests with Memtest86+ would throw so many errors then on an additional test, only throw maybe 1 or 2.

essenbe · 31 Jan 2015

skywalker89, There could be several explanations, but even 1 error is a fail. In the end it does not matter. Call technical support and request an RMA for both sticks and get a set in return. Sets are tested to run well together and individual sticks are not. So, you want a kit. Ask them about an advanced RMA. That way you get the new sticks before returning the old ones. You just have to give them a credit card number, in case you don't return the bad sticks. There will be no charges if you return them on time.