New
#1
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.