BSOD on laptop even after formatting, different codes everytime.

[atomicanom]

Hello,

I am having multiple BSOD on my old Windows 7 laptop. Despite a windows format, I am still getting BSOD.

Windows 7 x64
Asus k42jc
Battery is dead, running on power adapter directly.

All my BSOD codes are different, so I am not sure where to start. I thought this was a memory hardware issue but I ran MEMTEST 8+ already and it didnt find anything.

i've attached the archives files containing all the details.

Thank you,

 

[ICIT2LOL]

Hello and welcome atomicanom mate first up please follow this
Now before we can help we do need to know what is in your machine so please do this System Info - See Your System Specs - Windows 7 Help Forums
or either enter the specs of your system in your forum profile the specs will appear when we click on that little box bottom left of the post screen it is for me the preferable option as it is easy. As you may appreciate it is very hard when you don’t know what one is working with for example a diesel or petrol engine.
*(pretyped to save time)

BugCheck 9C, {0, fffff8800316cb70, 0, 0}

Probably caused by : [COLOR="Red"]intelppm.sys ( intelppm!MWaitIdle+19 )[/COLOR]

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

This is suggesting there is a problem with the CPU but the systems specs first

Now you mentioned a memtest please follow this if you need to run it again because this is the only memtest we recommend.
Now to make absolutely we are on the same page the memtest linked here is the only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+ - Windows 7 Help Forums
(This is pretyped to save time

Having said that it does appear to be a compilation of different faults so specs and then we can take it from there.

 

[atomicanom]

Hi,

I've rerun the test and I do see a faulty error, I have 2 stick so I tried to find the faulty one but both causes me BSOD.

I'll do a 8 round run tonight and tomorrow and see how it goes. I don't mind paying around 100$ for a 8GB replacement but I just want to make sure it is a stick issue and not my MOBO having an issue with the RAM slot

 

[atomicanom]

UPDATE 1: Changed RAM, tested single slots, no more error even after 8 runs.

Computer still BSOD with various error code like 20 times a day. What are the next tests I can do?

 

[ICIT2LOL]

Ok mate send those dumps again it's a shame the stick change did not fix the problem though and maybe pointing the finger at the slots. But lets see those dumps again before you go rushing into a new board - if indeed the problem is till the memory.

 

[ICIT2LOL]

Ok I did mean to ask you if you had any add on software installed as a little while back there was this

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88001355585, fffff8800b3ecea0, 0}

Probably caused by :[COLOR="Red"] fltmgr.sys [/COLOR]( fltmgr!FltpPerformPreCallbacks+815 )

Followup:     MachineOwner

This looks to be some form of Acronis software for computer management.

 

[atomicanom]

Here are my latest dumps. I also don't have Acronis, this is a fresh install and I've only installed so far LoL, debugging tools and ran a snappy driver yesterday to update all my drivers.

Still crashing today alot.

 

[ICIT2LOL]

Well from what I can see is that there are still driver issues and again a memory one that is referring to a problem with memory

PAGE_FAULT_IN_NONPAGED_AREA (50)
[COLOR="Red"]Invalid system memory was referenced. [/COLOR] This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: [COLOR="red"]fffff8a00c129ff8, memory referenced.[/COLOR]
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: [COLOR="red"][COLOR="red"]fffff8000306cb2f, If non-zero, the instruction address which referenced the bad memory
	address.[/COLOR][/COLOR]
Arg4: 0000000000000000, (reserved)

Now please follow this if only to eliminate the memory as the problem hopefully it is and that is easily fixed.
Now to make absolutely we are on the same page the memtest linked here is the only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+ - Windows 7 Help Forums

Plus are you using a aftermarket driver software to update drivers because if you are then it is really not the way to do it and you should use the Asus support drivers download for anything the only time I will use a driver software is when I have no options and then only one software which I remove after use but that is a rare thing for me to do.
Now you listed the model at AJ42C but ths is the closest I can get for the drivers for the machine you are on A42JC | Laptops | ASUS Global
I think maybe the wrong model number may have ben referenced.