Random BSODs since installing new SSD

[Kapau]

Recently I upgraded my motherboard, cpu and after that my SSD.
I first reinstalled Win7 on a freshly formatted drive and had no problems for a week.
Last week I got a 250GB Samsung 840 EVO and promptly wiped the old HDD and reinstalled on the SSD.
I downloaded a fresh set of drivers from Asus to go with my motherboard until all devices were done in device manager.
Ever since the installation I got random BSODs, so I reinstalled again, did a (windows) memtest that passed without problems and flashed the latest firmware on the SSD.
Everything on my systems seems to be going well, except for the random BSODs.
Since the reinstall I got 2: 1 during playing EVE online and one this morning when I got to the computer after I left it to download a bunch of crap overnight.
Before the latest reinstall on the SSD it crashed randomly during listening to music and browsing the web, once while being idle.
Cant see it on WhoCrashed or in the logs, but the BSOD said Memory Management error.
I've googled around for symptoms similar to mine but none offer much help besides "reinstall windows" and "scan for virusses", which is kind of pointless on a fresh install.

SF zipped report:
View attachment 299474


WhoCrashed info:

System Information (local)
--------------------------------------------------------------------------------

computer name: xxxx-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z87-C
CPU: GenuineIntel Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8524603392 total
VM: 2147352576, free: 1923567616




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 29-12-2013 14:47:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122913-8938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xC0000268, 0x2, 0x0, 0xFFFFF80003695A7E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 29-12-2013 14:47:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xC0000268, 0x2, 0x0, 0xFFFFF80003695A7E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Arc]

Hi Kapau.

You have Samsung Magician installed. So I think you have updated the firmware to the SSD properly.

Do two things at first. Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

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 our next steps after that, seeing those.
_________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {c0000268, 2, 0, fffff80003695a7e}

Probably caused by : memory_corruption

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000c0000268, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003695a7e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038ca100
 00000000c0000268 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSwapContext+6e
fffff800`03695a7e 0fb68f66010000  movzx   ecx,byte ptr [rdi+166h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  ts3client_win6

TRAP_FRAME:  fffff880095e5670 -- (.trap 0xfffff880095e5670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007fffff68000 rbx=0000000000000000 rcx=00000000c0000102
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003695a7e rsp=fffff880095e5800 rbp=fffffa8006f14b6e
 r8=fffffa800aebb0e8  r9=0000000000000000 r10=fffffffffffffff7
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiSwapContext+0x6e:
fffff800`03695a7e 0fb68f66010000  movzx   ecx,byte ptr [rdi+166h] ds:0030:00000000`00000166=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003692169 to fffff80003692bc0

STACK_TEXT:  
fffff880`095e5528 fffff800`03692169 : 00000000`0000000a 00000000`c0000268 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`095e5530 fffff800`03690de0 : 00000000`00000000 fffff8a0`0c647930 00000000`00000000 fffff880`033b4180 : nt!KiBugCheckDispatch+0x69
fffff880`095e5670 fffff800`03695a7e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`039892de : nt!KiPageFault+0x260
fffff880`095e5800 fffff800`036885f2 : fffffa80`06f14b50 fffffa80`06f14b50 fffffa80`00000000 fffff800`00000003 : nt!KiSwapContext+0x6e
fffff880`095e5940 fffff800`0369999f : 00000000`0000092c fffffa80`0aebb060 fffffa80`00000009 fffff8a0`04666930 : nt!KiCommitThreadWait+0x1d2
fffff880`095e59d0 fffff800`03988c3e : 00000000`00000000 00000000`00000006 00000000`00000001 fffff880`095e5a00 : nt!KeWaitForSingleObject+0x19f
fffff880`095e5a70 fffff800`03691e53 : fffffa80`06f14b50 00000000`00000009 fffff880`095e5ab8 fffffa80`07395320 : nt!NtWaitForSingleObject+0xde
fffff880`095e5ae0 00000000`77c612fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`06a6fb28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c612fa


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80003695db2 - nt!SwapContext_PatchXSave+2
    [ 01:21 ]
    fffff80003695e96 - nt!SwapContext_PatchXRstor+2 (+0xe4)
    [ 09:29 ]
2 errors : !nt (fffff80003695db2-fffff80003695e96)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

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

 

[Kapau]

Hey thanks for the fast reply!
I'll get rid of the driver and let the memtest run overnight.
I just made the mistake of running the driver verifier.exe, which caused my system to be unable to start and I had to go do a system restore. I'll post the results of the memtest tomorrow.

 

[Arc]

We may need to run driver verifier later, depending on the situation. It needs some cautions before applying it.

Take your time and do the tests

 

[Kapau]

Got up to 6 passes overnight, no errors so far. Ill leave it going till I get back from work.

Is it possible the BSODs are caused somehow by the SSD? I've ran this same setup for a week or two with no problems until I reinstalled to the SSD. Is there a way to check for this?

 

[Kapau]

15 passes, no errors

 

[Arc]

Very good news. So we may conclude that the RAM is undoubtedly good.

Now use the computer normally. We will start troubleshooting again if any further issue occurs.

 

[Kapau]

Had a reboot yesterday while gaming, reboot but no BSOD. When I ran WhoCrashed it said the system hasnt experienced any BSOD's or couldnt find the dump files :sarc:

Is there a way to run the driver verifier in something like safe mode or from let say a Knoppix boot? Else I'll just post back here when it crashes again.

 

[Arc]

Sometimes games may cause reboots ... if the FPS drops for a certain time.

If everything else runs OK, it is not a big issue to think.

 

[Kapau]

Had another random reboot while watching a youtube vid..

 

[Britton30]

How did you install the SSD, a clone, image, or fresh install? If a fresh install was the SSD the only drive connected at the time?
If you enabled Rapid Mode, disable it and test.

 

[Kapau]

Yes it was a fresh install on the SSD
No all drives were connected at the time
Rapid mode was and is disabled.

 

[Britton30]

OK, lets have a look at DiskMngmnt,

http://www.sevenforums.com/tutorial...nt-post-screen-capture-image.html#post2261610

 

[Kapau]

View attachment 299731

 

[Britton30]

Odd, I don't see and Active nor System flag anywhere. Give this a try.
Use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows

This may work too. http://www.sevenforums.com/tutorials/681-startup-repair.html

 

[Kapau]

Hmm, interesting. It says the Windows 7 disk I used to install Windows 7 isnt compatible with my version of the OS. Could this be because I did the EMS Enabled EUFI installer thingy or updated to Service Pack 1? It made me use GPT or something instead of the normal MBR.

Anyway I'll try to find a CD to burn a recovery disk to from Windows itself.

 

[Kapau]

View attachment 299995
Welp, looks like Windows doesnt want me to try to fix it.

Running "sfc /scannow" now as suggested by a Microsoft Help article.

>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

 

[Kapau]

Ran startup repair from the boot menu; Could not detect a problem.
Detected 1 problem:
Root cause found:
Boot status indicates that the OS booted successfully.

I also flashed my BIOS from something like 1405 to 1707, I'll shout back here if something happens again.
I still think it has something to do with the SSD, seeing as how I had the exact same hardware/software setup before I installed on the SSD...