Solved BSODs after Mainboard and CPU Upgrade plus change to 64 bit Windows 7

[Arc]

Is it crashing more now?

 

[toranaboy]

No further crashes but I was interested to note that WhoCrashed identified netio.sys as a potential culprit.

 

[toranaboy]

Thoroughly mystified by the late crash on 3rd November. My heart wants to blame the little people but my head tells me something else must have happened Given that nothing has happened now for a week, I will put it down to a brief infestation of fairies. Once again, thank you so much for your help.

 

[Arc]

You are welcome

 

[toranaboy]

Back So Soon

I spoke to soon. The pc crashed again last night. See minidump attached.

 

[Arc]

Not seeing any attachment though ....

 

[toranaboy]

Just uploaded the .dmp file, must have missed it somehow b4.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 1A[/COLOR], {8884, fffffa8009e54100, fffffa800c19b930, 502}
[COLOR=Red]
Probably caused by : memory_corruption[/COLOR] ( nt!MiRelinkStandbyPage+c6 )

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

According to Carrona.org, STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

So,

► 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, per RAM module per slot.

► Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[toranaboy]

Thanks. Verifier enabled again. As I reported at the outset, I ran Memtest86+ some weeks ago for 9 iterations without incident. I ran all modules at once in hopes that there would be no failures and I wouldn't have to check each DIMM separately over four days. As I say, nothing turned up so I thought the DIMMs were almost certainly OK (within reason).

 

[toranaboy]

I'm convinced the last crash a fortnight ago was caused by pixies, (the little scamps). I won't have any of your talk about reason and science. Thanks for putting up with me, I've marked the problem 'solved' again.

Regards,

Jim

 

[Arc]

Good news