Various BSOD

I thought my BSOD troubles were behind me. No BSOD for a few weeks and now out of the blue they are starting again.

The only new piece of hardware I installed was an add on USB expansion like 4 weeks ago and recently I used a multiport 5 in 1 USB reader.

I'll post the log, I appreciate any help.

Thanks.

I ran MemTest86 last night and it found errors on test 9 on the first pass with my memory (8gb x 4) in XMP profile.
I understand the XMP profile settings are advertised for 1 kit installed, I however have two installed so maybe that is the problem?

I disabled my XMP profile and ran for another 6 passes without any errors.

I suppose I'll just leave XMP disabled and come back if it occurs again.
Eventually I'll get around to testing every stick of ram individually.

Thanks!

John

I thought it was fixed but I got another BSOD while sorting a file collection by date imported in Jriver.

I am really hoping someone can point me to a hardware vs software problem as this is a fairly new build...
New file is attached. Thanks.

I also plan on running another 8 hours of memtest86 tonight.

I ran memtest86 another 8 hours on default settings (no XMP) with no errors found...makes me think there is some software problem.

If anyone can help confirm I would be gracious.

Thanks.

The latest dumpfile is

Code:

  *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41792, fffff680002b7100, 1000000000, 0}
Probably caused by : memory_corruption ( ONE_BIT )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
 the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff680002b7100
Arg3: 0000001000000000
Arg4: 0000000000000000

Run the memtest 86 for at least 8 complete passes.

Your memory is 2400 mhz but from the dumpfile it runs at 2133 mhz.

Code:

 [Memory Device (Type 17) - Length 40 - Handle 0043h]
  Physical Memory Array Handle  0042h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM0
  Bank Locator                  BANK 0
  Memory Type                   1ah - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         2133MHz
  Manufacturer                  0215
  Serial Number                         
  Asset Tag Number                        
  Part Number                   CMK16GX4M2A2400C14

Check this in your BIOS and also your other specs like CL 14 etc.

Please update your Easeus TODO backup program it has drivers from 2014
Also your Open Vpn driver/programs is outdated the drivers are from 2013

What does a corrupt PTE mean?

My memory is 2400 mhz with XMP enabled and 2133 if left to auto in BIOS.
I'll run more memory tests overnight.
I have run atleast 8 runs of memtest86 with XMP disabled without any errors but my latest BSOD was while running with XMP disabled too.

Thanks for checking it out.

John

Thanks for the help everyone. I know this is an old thread but I forgot to let everyone know that the problem has been solved.

IT WAS BAD RAM!!! I RMA'ed it and have not had a BSOD in 9 months!!!

Bad ram, unfu**in believable. 9 months later and I am still upset about it!!