BSOD multiple errors 0x000000d1 + more

[sanjirama]

Okay it has gotten to the point now where I have bloody knuckles from punching the wall due to BSOD frustration! Seriously in the middle of working on projects editing video/audio/graphics, the "machine" just cuts to BSOD. I have stalked a few sites before, trying to figure a solution, but I have finally come to grips with the conclusion "all bsod are not created equal." I don't even know where to begin fellas...but I'm here to and ready to take the first steps...

Errors include:

SYSTEM SERVICE EXCEPTION
SYSTEM THREAD EXCEPTION NOT HANDLED
DRIVER IRQL NOT LESS EQUAL
KMODE EXCEPTION NOT HANDLED

yeah i know...i've got problems.

yikes!

dump file + system info attch.

 

[koolkat77]

Please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[sanjirama]

UPDATE*** SF Diagnostic Tool information collected + included.
Thanks for the heads up @KOOLKAT77

Hopefully someone can help resolve this asap...I have some important projects to complete next month.

Sanji

 

[koolkat77]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, fffff88000e0eaf4}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
6: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000e0eaf4, address which referenced memory
Debugging Details:
------------------

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec70e8
GetUlongFromAddress: unable to read from fffff80002ec7198
 0000000000000000 Nonpaged pool
CURRENT_IRQL:  2
FAULTING_IP: 
Wdf01000!FxIoTarget::RequestCompletionRoutine+24
fffff880`00e0eaf4 4c8b5500        mov     r10,qword ptr [rbp]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
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 !Wdf01000
    fffff88000e0eae7 - Wdf01000!FxIoTarget::RequestCompletionRoutine+17
 [ 8d:85 ]
1 error : !Wdf01000 (fffff88000e0eae7)
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
Followup: memory_corruption
---------

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

Do this test overnight, before going to bed.

 

[sanjirama]

Will do when I return home...Out of town for a few days with family. Thanks for the quick response.