BSOD After exiting LoTRO

Hi lastiel.

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.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
________________________________________________________

Code:

BugCheck 24, {1904fb, cad7d8cc, cad7d4b0, e3ba7bb8}

Probably caused by : memory_corruption

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

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (e3ba740a-e3ba7b0a)
e3ba7400  f7  ff  89  45  14  3b  c3  75  0c  c7 *44  10  17  00  00  c0 ...E.;.u..D.....
...
e3ba7b00  3c  ff  75  38  ff  75  34  ff  75  30 *7f  75  2c  ff  75  28 <.u8.u4.u0.u,.u(

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xffffffffcad7d4b0 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_stride

FAILURE_ID_HASH:  {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

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

lastiel said:

Okay so I ran Memtest86+ and I have one bad stick of RAM. I have removed the bad one and ran the Memtest86+ once again and it came back good, no errors. I'll be getting the Driver Verifier installed and see what that tells me.

Driver verifier is not to be installed. It is already present there, you have to activate it.

But as you have pointed out a RAM stick as faulty, and removed it rightly, you should give it a time before going for driver verifier.

If it does not BSOD any more, there will be no need for Driver Verifier.