BSOD 10-20 min. after boot regularly. LocaleID: 1050, BCCode: a

[willow099]

Hi guys.
Hope that someone can give me a few tips.
It started yesterday and it's persistent as written in thread.

Blue Screen message:
irql_not_less_or_equal

Windows post boot error message:
LocaleID: 1050
BCCode: a

P.S. ANY help is much appreciated and I've uploaded SF file for analysis.

Thank you all in advance.

 

[koolkat77]

Welcome

What antivirus are you using? I don't see any.

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR 
Usual causes:  Memory, Paging file corruption, File system, Hard drive, 
Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing 
Service Pack
BugCheck 7A, {fffff6fc4000b390, ffffffffc00000c0, 12e6d6860, fffff88001672f60}
Probably caused by : memory_corruption
----------------
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL  
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, 
Backup tool, compatibilityBugCheck A, {fffffd8005e2d868, 2, 1, fffff80002f02580}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+150 )

Run this tool and delete anything it finds:
→ Anti-rootkit utility TDSSKiller

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

→ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
→ Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

 

[willow099]

Thank you for REALLY FAST response.

a) For protection last 15 years I use ESET Smart Security 5 with Malwarebytes (with mutual exclusions) and it was working pretty well so far...

b) I ran TDSSKiller and he found medium threat in SPTD.sys. I left it in quarantine at the moment because I have PowerISO and Daemon tools installed and one of my 2 VRT drives is SCSI (i believe it belongs to Daemon tools).

c) I haven't found time to check each memory module but just for the record i have:
2x2 TW3X4G1600C9D 1.8v ver.2.4 + 2x2 CM3X2G1600C9DHX 1.8v ver.3.2 at 1333/8/8/8/24, Performance Level 9

Thank you VERY MUCH so far, and I'll get back to you tomorrow after I finish testing modules with memtest and with prime95, small ftt's

Bye,
Robert.

 

[willow099]

Today I've finished testing all 4 modules (in all 4 slots) and afterwards I even tried with different combinations (permutations), and they all checked out fine. After running Prime95 stress test for 24+ hours it's all good... !?

And to my surprise, I didn't have any more BS errors after "reassembling" modules???

So, just to be sure should I maybe check my MFT and boot record, because I REALLY can't afford any more delays like this because I live from some heavy 3d rendering, and deadlines are A MUST!

Any tips, precautions, advices,...?

Much appreciated,
Robert

 

[koolkat77]

Lol, ESET 5 is not there for 15 years
Just delete Daemon tools and see if the situation is better or not

Not only STPD.sys, it also uses dtsoftbus01.sys which you're aware of, causes various problems.

remove daemon tools - Google Search

 

[willow099]

Well... I think that we're on the same page here regarding ESET products, because I've started using NOD32 from the start and I think they are somewhere around 12-15 years old (I'm 38 myself)

After I uninstalled DT and cleaned registry my system feels like more responsive. Maybe I'm a bit subjective in this case, but numbers aren't lying and we'll see after I put several passes to render in V-ray this night.

Thank you for all your help, and if you ever find yourself struggling with something regarding DTP, design (web|industrial|graphic), 2d/3d modeling and rendering...just send PM and I'll be there for you as you were for me.

Thank U 4 everything and C U arround

 

[koolkat77]

Oh well, 25 years actually
ESET NOD32 - Wikipedia, the free encyclopedia

"NOD32
The first version of NOD32 - called NOD-ICE - was created in 1987 by Miroslav Trnka and Peter Pasko when computer viruses were becoming increasingly prevalent."

And no problem, keep us posted either way