Help! I keep bsod'ing!

I built a computer last month, ever since i built it, installed windows 7 and installed all the drivers inc bios, i keep getting blue screens! i have ran memtest for about 10 hours and came back with no problems. also reinstalled windows 7 about a million times. i downloaded crash test and this is what it said. please help!

comp specs:
amd fx 4100 3.6ghz
asus m5a78l-m-lx motherboard
corsair vegeance 2x 4gb ram
his hd radeon 6670 graphics
hitachi 500gb hdd.

windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-4100 Quad-Core Processor AMD586, level: 21
4 logical processors, active mask: 15
RAM: 8571183104 total
VM: 2147352576, free: 1983873024



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 2/8/2012 1:15:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020712-22994-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x34 (0x50830, 0xFFFFF88002F7E7C8, 0xFFFFF88002F7E030, 0xFFFFF80002CBDC94)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 2/8/2012 1:15:00 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x34 (0x50830, 0xFFFFF88002F7E7C8, 0xFFFFF88002F7E030, 0xFFFFF80002CBDC94)
Error: CACHE_MANAGER
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 2/8/2012 12:49:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020712-27783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x34 (0x50830, 0xFFFFF88002F8C7C8, 0xFFFFF88002F8C030, 0xFFFFF80002C78C94)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 2/7/2012 11:18:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020712-22339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F649BD, 0xFFFFF88006D04030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Could you please upload your dump file/s?
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

View attachment 197211

heres the files

Thank you.

The BSOD was probably caused by ntkrnlmp.exe. This file is associated with Microsoft Windows NT operating systems.

You will need to run an sfc/scannow command in an elevated command prompt. If errors are found, run it twice more with each scan followed by a reboot.
SFC /SCANNOW Command - System File Checker

You should also stress test your other hardware using Prime95, just to be sure.
http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Finally, enable Driver Verifier. However before you do, it is advised that you create a system restore point and backup first.
Driver Verifier - Enable and Disable

If none of these work, isolate each stick of RAM (remove one at a time) and start the computer. Post back whether the BSOD's still occur.

Finally, update all of your drivers if you haven't done so already.

i updated to service pack 1, it was downloading when i made this post. i did sfc/scannow, came back with no problems.. did the test about 3-4 times. did a tress test for 2 hours, no problems also. last night i enabled the verifer, now the computer is just slower. last night i re-ran memtest for 7 hours, both of my ram sticks passed.

gusrawrr said:

i updated to service pack 1, it was downloading when i made this post. i did sfc/scannow, came back with no problems.. did the test about 3-4 times. did a tress test for 2 hours, no problems also. last night i enabled the verifer, now the computer is just slower. last night i re-ran memtest for 7 hours, both of my ram sticks passed.

Click to expand...

If it isnt RAM (have run run single sticks, and different mobo slots?) and the system passes SFC it is probably time for driver verifier to find which driver is the problem one.

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

Click to expand...

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Th

Click to expand...

en, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Click to expand...

Using Driver Verifier to identify issues with Windows drivers for advanced users

just set up the verifier just like you said, it blue screened on me right after i finished setting it up. now im just waiting for another one.


On Wed 2/8/2012 2:51:23 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1A (0x5003, 0xFFFFF90000812000, 0x4F5, 0x406A000009E2)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown MEMORY_MANAGEMENT

thats a new blue screen, haven't seen this one before.

gusrawrr said:

just set up the verifier just like you said, it blue screened on me right after i finished setting it up. now im just waiting for another one.


On Wed 2/8/2012 2:51:23 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1A (0x5003, 0xFFFFF90000812000, 0x4F5, 0x406A000009E2)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown MEMORY_MANAGEMENT

thats a new blue screen, haven't seen this one before.

Click to expand...

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

Click to expand...

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Click to expand...

i was going to add the dmp files before but it didn't save. it only has the dmp files from yesterday. thats why i went on whocrashed and copy and pasted the details from the latest blue screen.

it didn't save a dmp file, i looked before and it only had the dmp files from yesterday.

gusrawrr said:

i was going to add the dmp files before but it didn't save. it only has the dmp files from yesterday. thats why i went on whocrashed and copy and pasted the details from the latest blue screen.

Click to expand...

Thats one reason we dont recommend either who crashed or Blue screen view. They often also wrongly blame OS files.

still wait on a blue screen after changing the verifier settings, its been on since 6 in the morning and its nearly 8, surprised it hasn't blue screened yet.

Well, let's hope it does crash as that's more or less what we're trying to do by enabling driver verifier.

now my computer keeps freezing, i haven't recieved a blue screen since yesterday morning. i tried using that readiness tool but it said its already been installed.

gusrawrr said:

now my computer keeps freezing, i haven't recieved a blue screen since yesterday morning. i tried using that readiness tool but it said its already been installed.

Click to expand...

Please provide us with your Event Viewer administrative logs by following these steps:
{Instructions courtesy of writhziden}

Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

JHM, as i said in the post, i've reinstalled windows 7 heaps of times.. each time i do it, its a clean install. its not a windows 7 issue.

View attachment 197453
here you go zigzag