Solved BSOD after brand-new Windows re-installation

[Eminence]

Hello Sevenforums and BSOD team, I have recreated another BSOD thread, last time I was having 0-10+ BSODs a day, and thinking it was a software problem I had re-installed Windows as a fresh new copy. Unfortunately I am still getting blue screens so this time I am inclined to think that it is perhaps a hardware issue. I have already tested my CPU, GPU, RAM, so I'm thinking it may be my Motherboard or Hard drives, although I do have a feeling it could still be the RAM as well.

I actually re-installed Windows twice, the first time I got a couple blue screens and had the install disk inside so it ran the repair tool twice (crashed twice.) The computer is about a year old now, the RAM was not on the Motherboard Manufacturer's list, however it was working fine. When I was installing Windows updates it did blue screen a couple times on Stage 2 (While it's shutting down.) It also ran Chkdsk once by itself and moved a few sectors of my SSD. The drive is formatted and partitioned new and Windows 7 Home Premium is installed, the other HDD drive still has my other files in it.

I've done a RAM test and it passed, but when I did an Extended test it got stuck on 21%, so I'm wondering if I should've left it to finish or not (I got impatient even though Windows says it gets stuck but it's still working.)

As I was moving some blu-ray movies from my HDD to my External Drive (Around 400GB) the PC Blue screened. This happened twice. Once while using the computer, another time just AFK'ing with it on.

If I think of anything I'll post it here, I don't think it's a PSU issue, I really hope it's not a hardware issue, but just in case I would like to know if it is so I can purchase some new RAM or another hard drive during Black Friday if it is.

I will include my PC specs and BSOD report here, the dump is recorded in Kernel mode, let me know if you want another mode.

SSD: Intel 330 Series SSDSC2CT240A3K5 240GB SSD - 2.5" Form Factor, SATA 6Gb/s, Up To 500 MB/s Read Speed, Up To 450 MB/s Write Speed

Note: Windows is installed on the SSD.

HDD: Seagate Barracuda ST2000DM001 2TB Serial ATA Hard Drive - 7200RPM, 64MB, SATA 6Gb/s
GPU: EVGA Geforce GTX 660 Ti 02G-P4-3662-KR Video Card - 2GB, GDDR5, PCI-Express 3.0(x16), 1x Dual-link DVI-I, 1x Dual-link DVI-D, 1x DisplayPort, 1x HDMI, DirectX 11, SLI Ready, Superclocked

CPU: Intel Core i5-2500K BX8063I52500 Unlocked Processor - Quad Core, 6MB L3 Cache, 1MB L2 Cache, 3.30 GHz (3.70 GHz Max Turbo), Socket H2 (LGA1155), 95W, Fan, Retail

Motherboard: MSI Z77A-G41 LGA 1155 Intel Z77 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard with UEFI BIOS

PSU: CORSAIR TX Series CMPSU-650TX 650W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS BRONZE Certified Active PFC Compatible with Core i7 Power Supply & New 4th Gen CPU Certified Haswell Ready

RAM: Kingston HyperX Black 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model

Let me know if you need clickable links...

 

[Arc]

First of all, make it sure that SSD's firmware is up-to-date.
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18363

Next, uninstall Auslogics Disc Defrag.

Do it, too. => http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

How you have tested RAM? 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.
_______________________________________________________________________________

BugCheck 1A, {41790, fffffa8003e67c30, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
----------------------------------------------------------------------
BugCheck A, {47, 2, 1, fffff80002caa929}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+109 )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80002cafff3, fffff880091ba8e0, 0}

Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+223 )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 50, {fffffa830480316b, 0, fffff80002c658b5, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck 1A, {5003, fffff70001080000, 6992, 2873009}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+38936 )

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

 

[Eminence]

First of all, make it sure that SSD's firmware is up-to-date.
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18363

Next, uninstall Auslogics Disc Defrag.

Do it, too. => http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

How you have tested RAM? 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.
_______________________________________________________________________________

BugCheck 1A, {41790, fffffa8003e67c30, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
----------------------------------------------------------------------
BugCheck A, {47, 2, 1, fffff80002caa929}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+109 )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80002cafff3, fffff880091ba8e0, 0}

Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+223 )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 50, {fffffa830480316b, 0, fffff80002c658b5, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck 1A, {5003, fffff70001080000, 6992, 2873009}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+38936 )

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

Can you tell me why I should uninstall Auslogics Disk defrag? I use it for my HDD not the SSD and I move Windows files to the front for faster startup (although my computer is fast enough already it seems, and with my new install I guess I don't have to worry too much about defragging)

Also I have Microsoft Security Essentials and Malwarebytes' Pro running on a brand new windows install, I don't think I have a Virus on a brand new os (Yes I know I am a stubborn fellow)

However your next option check the ram seems to be the problem, I got instant red lines as soon as I started the boot test from my flash drive, so I will test the other stick of ram and other motherboard slots to see if it's the ram or the motherboard hopefully it's the ram so I can just buy a replacement.

 

[Arc]

I am no magician. And nobody is. Suggestions are always based on symptoms. Nobody can point to a fix button.

Can you tell me why I should uninstall Auslogics Disk defrag? I use it for my HDD not the SSD and I move Windows files to the front for faster startup (although my computer is fast enough already it seems, and with my new install I guess I don't have to worry too much about defragging)

Also I have Microsoft Security Essentials and Malwarebytes' Pro running on a brand new windows install, I don't think I have a Virus on a brand new os (Yes I know I am a stubborn fellow)

However your next option check the ram seems to be the problem, I got instant red lines as soon as I started the boot test from my flash drive, so I will test the other stick of ram and other motherboard slots to see if it's the ram or the motherboard hopefully it's the ram so I can just buy a replacement.

Windows 7 does not need any defragment program. It does not fragment the discs as XP used to do.
A secondary/ Data disc does not have any influence in startup. If you think defragmenting it makes your system first, it is your wrong perception only.
Finally, defragmenting programs always cause disk misbehavior, so I suggested to get rid of it.

I noticed ataport.sys failing there. If it is not a disc failure then it is an infection. So I had to suggest for virus checks. I know what I am doing. And thinking is not an enough ground to nullify a logical suggestion.

But, a failing memory can cause any type of errors. And as you are having memory errors, now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Some more people like you can make the situation for the other persons tough who are seeking help.

 

[Eminence]

I am no magician. And nobody is. Suggestions are always based on symptoms. Nobody can point to a fix button.

Can you tell me why I should uninstall Auslogics Disk defrag? I use it for my HDD not the SSD and I move Windows files to the front for faster startup (although my computer is fast enough already it seems, and with my new install I guess I don't have to worry too much about defragging)

Also I have Microsoft Security Essentials and Malwarebytes' Pro running on a brand new windows install, I don't think I have a Virus on a brand new os (Yes I know I am a stubborn fellow)

However your next option check the ram seems to be the problem, I got instant red lines as soon as I started the boot test from my flash drive, so I will test the other stick of ram and other motherboard slots to see if it's the ram or the motherboard hopefully it's the ram so I can just buy a replacement.

Windows 7 does not need any defragment program. It does not fragment the discs as XP used to do.
A secondary/ Data disc does not have any influence in startup. If you think defragmenting it makes your system first, it is your wrong perception only.
Finally, defragmenting programs always cause disk misbehavior, so I suggested to get rid of it.

I noticed ataport.sys failing there. If it is not a disc failure then it is an infection. So I had to suggest for virus checks. I know what I am doing. And thinking is not an enough ground to nullify a logical suggestion.

But, a failing memory can cause any type of errors. And as you are having memory errors, now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Some more people like you can make the situation for the other persons tough who are seeking help.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

The same as your chart except it's RAM2 not RAM1, I only tested in recommended dual-channel slots in Mobo which was slot 2 and 4, so no testing was done in 1 or 3 since I don't use those slots.

I tested and this was the results, I run my DRAM frequency on Auto (1.488v) but i've read that it is supposed to be 1.65v, also when I test RAM 1 (working stick) its latency is 9-9-9-24 and the bad stick is 6-6-6-20 (this is while only 1 stick is in so I wasn't running dual channel. When I was testing dual channel sticks I got instant errors, 2nd stick instant errors both slots, 1st stick no errors for 7-10 passes either slot.

 

[Eminence]

I am no magician. And nobody is. Suggestions are always based on symptoms. Nobody can point to a fix button.

Windows 7 does not need any defragment program. It does not fragment the discs as XP used to do.
A secondary/ Data disc does not have any influence in startup. If you think defragmenting it makes your system first, it is your wrong perception only.
Finally, defragmenting programs always cause disk misbehavior, so I suggested to get rid of it.

I noticed ataport.sys failing there. If it is not a disc failure then it is an infection. So I had to suggest for virus checks. I know what I am doing. And thinking is not an enough ground to nullify a logical suggestion.

But, a failing memory can cause any type of errors. And as you are having memory errors, now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

Some more people like you can make the situation for the other persons tough who are seeking help.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

The same as your chart except it's RAM2 not RAM1, I only tested in recommended dual-channel slots in Mobo which was slot 2 and 4, so no testing was done in 1 or 3 since I don't use those slots.

I tested and this was the results, I run my DRAM frequency on Auto (1.488v) but i've read that it is supposed to be 1.65v, also when I test RAM 1 (working stick) its latency is 9-9-9-24 and the bad stick is 6-6-6-20 (this is while only 1 stick is in so I wasn't running dual channel. When I was testing dual channel sticks I got instant errors, 2nd stick instant errors both slots, 1st stick no errors for 7-10 passes either slot.

I didn't test every slot on my motherboard, just the 2nd and 4th slot since they are the recommended slots for running Dual-channel RAM, anyway I did a rootkit scan and it was fine, I am going to update my SSD drivers and my motherboard drivers now, and I don't have a problem, I'll contact Kingston later, thank you for your patience and perseverance Arc, you truly helped me this time and even last time throughout my problems, thank you.

 

[Arc]

You are most welcome.

Before you contract Kingston for a replacement, dont use the RAM stick that is failing. It will cause more BSODs there.

 

[Eminence]

Yes, I have removed the RAM and not gotten a single bsod since.