Solved Weird BSOD's new computer build transferred from an old one

[andy11235]

here are new dump files

 

[andy11235]

I am also downloading the new FX990 drivers that may be part of the problem i do not know yet but i think the drivers that came with the motherboard are meant for rev 1 and i think i have a rev 2.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {c0000005, fffff880063ded42, fffff8800a782210, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 )

Followup: MachineOwner

Usual causes:  System service, Device driver, graphics driver, memory

You have had a few BSODs linked to memory and faulty graphics and device drivers (Stop 0x3B), what were the results of the Memtest86+ and I would suggest also running Driver Verifier:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Run the test for least 24 hours, if a BSOD occurs before this period then you may stop the test and upload the corresponding .dmp file.

Okay and post back the results of the graphics driver update

 

[andy11235]

i am running mem test now, i scanned the registry and repaired it and then boom no boot and the startup repair can't even run fully so it is going to be ram or mboard. i hate getting faulty hardware.

 

[x BlueRobot]

Why did you use a registry repair program? :shock: They tend to delete important keys and hives within your registry, and can lead leave your computer in a unbootable state.

 

[andy11235]

I took an image right before pushed the image its running again and it is running mem test first test is finding allot of errors. does mem test look at cpu memory also?

I was removing some bad solidworks registry keys because it got to a point it was only crashing in solidworks.
I never had a big problem with using them before some times it makes it faster some times i need to revert never had a system just crash from it. why do they make them if it does more harm than good usually.

 

[andy11235]

Mem test is running and finding allot bad ram, when looking at it how do you figure out which ram is the bad one with out testing each individually?

 

[x BlueRobot]

You have to test each slot individually (it could also be bad DIMM slots), and registry cleaners are usually designed by malicious software companies who try to compromise a user's machine.

Run Memtest86+ for least 7-8 passes, and preferrly overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available

.

 

[andy11235]

Found the bad stick the rest are running overnight

 

[x BlueRobot]

Found the bad stick the rest are running overnight

Have you also placed the bad RAM module in a different slot, and then tested again, repeating the process with the same bad RAM module to identify a DIMM slot which may be causing issues?

 

[andy11235]

yes i did it with good and bad ram and moved the bad one to a different computer and it still came up bad right away.

 

[x BlueRobot]

Okay good work

It seems you have a bad RAM module, which in turn is causing problems with your system i.e. BSODs