New
#21
here are new dump files
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.
Code:BugCheck 3B, {c0000005, fffff880063ded42, fffff8800a782210, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 ) Followup: MachineOwnerYou 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:Code:Usual causes: System service, Device driver, graphics driver, memory
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 :)
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.
Why did you use a registry repair program? They tend to delete important keys and hives within your registry, and can lead leave your computer in a unbootable state.
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.
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?
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.
.x BlueRobot said:
Found the bad stick the rest are running overnight