critical structure bsod

Yeah it's completely normal, and can upload the results from SFC /SCANNOW command, and have you tried running CHKDSK from command prompt at boot?

Read Option 3 for uploading the results:

• SFC /SCANNOW Command - System File Checker
• Command Prompt at Startup

I had to rerun the sfc cause when I brought the last one to the desk top it was empy and I'm gonna run check disc at boot right now.

Chkdsk said windows did not find any problems but it said it failed to transfer logs with status 50

There doesn't seem to be any problems with your system files, and if no problems were found, then it should be fine to continue. Here's some explanation for the error code:

• failed to transfer logged messages to the event log with status 50 - Microsoft Community

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• Driver Verifier - Enable and Disable

More Help and Information with Driver Verifier - Using Driver Verifier to identify issues with Drivers

Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 7-8 passes, and preferably 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.

It bsod again and now its trying to attempt repairing but it doesn't seem like its working.Its been trying for about 10 minutes now,any suggestions.


well it finished but was unsuccessful and asked me send or not send then clicked finish and it shut down.

I booted back up and disabled driver verifier and used the sfc tool to create a file so here it is

Code:

BugCheck 109, {a3a039d8991b6504, b3b7465eeb9834ca, fffff80002b1afdd, 1}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+30d0 )

Code:

Usual causes:  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

Complete the memory test, and then to beginning to test the CPU.

• Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

I ran memtestx86 for 13 passes and no errors were found with both sticks of ram in,do I still need to test each stick individually.I was reading about the stress test with prime95 and it said I should monitor my temps but I do not know what would be considered high temps.

There seems to be no problems with your RAM, and I wouldn't recommend going above 80*C with Prime95.