BSOD after brand-new Windows re-installation

Arc said:

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

Next, uninstall Auslogics Disc Defrag.

Do it, too. => Windows Update - Reset

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.
_______________________________________________________________________________

Code:

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.

[QUOTE=Arc;2607939]I am no magician. And nobody is. Suggestions are always based on symptoms. Nobody can point to a fix button.

Eminence said:

Arc said:

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:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
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.

No code has to be inserted here.
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.

[QUOTE=Eminence;2609485]

Arc said:

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

Eminence said:

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:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
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.

No code has to be inserted here.
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.

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