Solved New Build, Multiple BSOD, Unknown error code

[ddg5006]

Im thinking another bad board. This is insane, I'm never buying another MSI product again.

cuas the ram is testing good in memtest? what do you think ?

 

[Britton30]

I have had very poor experience with MSI and ASRock products. Of course others have good luck, not me though.

Let's see what Arc can see in the newest dumps?


Try running a single RAM memtest and see what happens.

 

[Arc]

I totally filed to understand what is going on there in the system. It happens sometimes with me. I have to confess that this issue is beyond my ability, provided there is no activation hack. I asked for mgadiag long ago .... but havent got the proper response.

Hardware is not failing. Motherboard is replaced. No driver is found as failing .... still so frequent and so versatile bugchecks.

BugCheck 19, {22, 100000000000, 0, 0}

GetPointerFromAddress: unable to read from fffff800028aa0e0
GetUlongFromAddress: unable to read from fffff800028aa198
GetUlongFromAddress: unable to read from fffff800028181b0
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+7338 )

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

BugCheck 1A, {5002, fffff90000812000, 2a3d, 3a2cfffffffe}

Probably caused by : win32k.sys ( win32k!memset+80 )

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

I dealt with some other threads of ddg5006 .....

• http://www.sevenforums.com/bsod-help-support/325043-bsod-when-trying-print.html
• http://www.sevenforums.com/bsod-help-support/324789-random-bsod-different-times.html

But for this one .... I can say that as far as I have seen, if all the statements of ddg5006 till now are correct, there is no sufficient reason for a BSOD, other than the fact that he got a bad replacement motherboard.



Unfortunately I have nothing more to say.

 

[ddg5006]

Try running a single RAM memtest and see what happens.

I did try that, I ran both tests, 1 test with both sticks for 14 passes or so,

and the second test with 1 stick only over 20 passes

 

[ddg5006]

So I flipped out on my online retailer, even though the board is non refundable they agreed to refund me the money to purchase a different brand. Any suggestions of a reliable board to get?

 

[ddg5006]

I totally filed to understand what is going on there in the system. It happens sometimes with me. I have to confess that this issue is beyond my ability, provided there is no activation hack. I asked for mgadiag long ago .... but havent got the proper response.

Hardware is not failing. Motherboard is replaced. No driver is found as failing .... still so frequent and so versatile bugchecks.

BugCheck 19, {22, 100000000000, 0, 0}

GetPointerFromAddress: unable to read from fffff800028aa0e0
GetUlongFromAddress: unable to read from fffff800028aa198
GetUlongFromAddress: unable to read from fffff800028181b0
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+7338 )

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

BugCheck 1A, {5002, fffff90000812000, 2a3d, 3a2cfffffffe}

Probably caused by : win32k.sys ( win32k!memset+80 )

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

I dealt with some other threads of ddg5006 .....

• http://www.sevenforums.com/bsod-help-support/325043-bsod-when-trying-print.html
• http://www.sevenforums.com/bsod-help-support/324789-random-bsod-different-times.html

But for this one .... I can say that as far as I have seen, if all the statements of ddg5006 till now are correct, there is no sufficient reason for a BSOD, other than the fact that he got a bad replacement motherboard.



Unfortunately I have nothing more to say.

I did some searching and it seems as if I'm not the only one experiencing this issues. NEVER AGAIN MSI!!!

Archie thanks for all your help and patience.

 

[Britton30]

Will you use the i5-4440 in the board?

 

[ddg5006]

Will you use the i5-4440 in the board?

yes, i am only swapping out the mb.

Are you allowed to link to products on this site ?

 

[Britton30]

Sure we can, here a few good ones I would use.
Newegg.com - Computer Parts, PC Components, Laptop Computers, LED LCD TV, Digital Cameras and more!

 

[ddg5006]

So turns out it was the ram all along even though we vigorously tested it and all signs seemed to point to the board. I RMA'd the ram and I would up switching for gigabyte board also. Anyway thanks for all your help and support guys.

 

[Arc]

All is well that ends well!

 

[ddg5006]

I suppose so, thanks again for all your help.