BSOD playing BF3 error 0x0000001a

JCL III · Feb 24, 2012

-Retail version Windows 7 home premium 64bit
-Hardware is about 8 months old

Hi guys I never thought I'd have to resort to this forum. I have a very minimal tech understanding. Recently (1 month ago when running Vista 64bit) my computer had started to blue screen when playing games like Battlefield 3 and Dota 2. I updated all drivers and ran Windows Memory Diagnostics advanced tests on my ram which had several passes without errors. It's killing me because I've never had any problems with my computers reliability, it would run on hours playing games like WoW, BF2, BF3.

Frustrated I installed a new hard drive and did a fresh install of Windows 7. Still the same problem. One thing to note is, when first booting up and playing a BF3, I can play for hours without any BSOD. However, I noticed if I play after waking my computer from sleep mode as opposed to a fresh boot up, it will crash within 1-10 minutes.

Thank you very much for your help.

mgorman87 · Feb 24, 2012

Only one minidump in your report and it's memory management. That is either bad RAM or a bad driver

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

A known BSOD maker in Windows 7. The 2005 version of this driver is known to cause BSOD on Windows 7 systems.
Download the ATK0110 utility from here - ASUSTeK Computer Inc. - Motherboards- ASUS M4A79XTD EVO
Expand the "Utilities" tab and find "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" and download it
After you install it browse to C:\windows\system32\drivers and check the properties of ASACPI.sys and make sure it now says 2009.

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
2. Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb 23 21:33:38.098 2012 (UTC - 5:00)
System Uptime: 0 days 5:24:39.659
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+117c3 )
BUGCHECK_STR:  0x1a_8886
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!_??_::FNODOBFM::_string_+117c3
BiosReleaseDate = 06/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

JCL III · Feb 25, 2012

New mini dump file

Hi there, I updated the driver and was waiting for another blue screen. Here's the new mini dump. I'm going to be running all of the tests now. Thank you.

mgorman87 · Feb 25, 2012

That has the same minidump as the first report.

If you get any new BSOD, then upload a report

JCL III · Feb 25, 2012

oops sorry...

here ya go

mgorman87 · Feb 25, 2012

No..I don't need anymore reports. Just do as I suggested and if you get a new BSOD, then upload a new report

JCL III · Feb 28, 2012

Hey there, after running memtest it turns out that one of my sticks of ram had several errors. I replaced the ram and I am still having bsod. I checked both of the ram slots with a healthy ram so I think it was just the ram. I also ran the stress tests and the hard drive extended tests, no errors or problems to report.

Don't know if it will be useful, but my computer only crashes on BF3 upon waking from sleep mode. From a fresh boot up there aren't any problems.

Here is the most recent dump file. Thank you.

mgorman87 · Feb 28, 2012

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

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Feb 27 20:06:25.844 2012 (UTC - 5:00)
System Uptime: 0 days 21:33:44.031
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46f0d )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+46f0d
BiosReleaseDate = 06/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

JCL III · Mar 5, 2012

Hey there, I ran driver verifier for a few days without any crashes. For some reason my computer stopped BSOD-ing. I've only had 1 crash since the last post. Just wanted to say thanks for the help.

For anyone that may read this post, running Battlefield 3 as administrator has seemed to fix the Memory_management BSOD. I'm not sure why but I guess it's worth a try. Again thanks!

JCL III · Mar 8, 2012

new error code

Hi again, my friend was trying to playing a game on my comp when it crashed again. I suspect it might be a driver of some sort this time. Any help would be much appreciated. There should be 3 minidump files in this one. Thank you for your time

writhziden · Mar 11, 2012

Unfortunately, the most recent crash did not generate a .dmp file. It also did not register in the error reports... I do see other error reports that lead me to believe Windows may not be running as it should. Since you did a fresh install, I suspect either a corrupted install source or driver issues. Where did you get your Windows install files?

If you are overclocking any hardware, please stop.
Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

JCL III · Mar 12, 2012

Hi there, I tried running sfc scannow and it got to 33% and then said "windows resource protection could not perform the required operation."

I ran it again and it said "windows resource protection did not find any integrity violations."

Before this post, I was trying to run battlefield 3 as normal with Firefox and but the browser crashed and then caused a page fault in nonpaged area BSOD. I looked in my minidump files but it didn't log the error report. I don't know what is going on lol.

I've also tried running BF3 with Internet Explorer and it has crashed before. Most of the time I can play BF3 without any problems but then sometimes it crashes after a couple of minutes. I'm going to run driver verfier again and see if it crashes. But last time it ran for 2 days without a crash. Thanks in advance for the help

writhziden · Mar 12, 2012

Remember, you want to do the steps that usually cause a crash with Verifier running.

Also, in the third step in Verifier, do not enabled the last two items in the red boxes shown in the image. Only enable Standard settings.

JCL III · Mar 13, 2012

Ok, I was running verifier with the settings they showed in tutorial but I'll change it asap. I just got a bsod and it created a minidump so here ya go, Thanks!

JCL III · Mar 13, 2012

damn another crash. here's there 2nd minidump :cry:

.

writhziden · Mar 13, 2012

Code:

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\JCL III\Windows_NT6_BSOD_jcgriff2\031312-19858-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`03052670
Debug session time: Tue Mar 13 03:24:15.806 2012 (UTC - 6:00)
System Uptime: 0 days 0:07:11.993
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffd6f801e64e0, 2, 1, fffff80002e77601}

Probably caused by : memory_corruption ( nt!MmCreateKernelStack+e6 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffd6f801e64e0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e77601, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
 fffffd6f801e64e0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmCreateKernelStack+e6
fffff800`02e77601 49891cd2        mov     qword ptr [r10+rdx*8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff88008545240 -- (.trap 0xfffff88008545240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a21a458 rbx=0000000000000000 rcx=0000000fa800a21a
rdx=0000005df003cc9c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e77601 rsp=fffff880085453d0 rbp=0000000000000002
 r8=000000144348c000  r9=0000000fffffffff r10=fffffa8000000000
r11=fffffa800a21a450 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
nt!MmCreateKernelStack+0xe6:
fffff800`02e77601 49891cd2        mov     qword ptr [r10+rdx*8],rbx ds:f500:fffffd6f`801e64e0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e891e9 to fffff80002e89c40

STACK_TEXT:  
fffff880`085450f8 fffff800`02e891e9 : 00000000`0000000a fffffd6f`801e64e0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08545100 fffff800`02e87e60 : 00000000`00000000 fffff800`03092e28 fffff800`03092e28 fffffa80`078cf061 : nt!KiBugCheckDispatch+0x69
fffff880`08545240 fffff800`02e77601 : fffff800`030bf500 fffff880`08545510 00000000`00000000 fffff880`08545480 : nt!KiPageFault+0x260
fffff880`085453d0 fffff800`02e96792 : fffffa80`078cf060 00000000`00000002 fffff880`08545990 fffffa80`0918b680 : nt!MmCreateKernelStack+0xe6
fffff880`085454c0 fffff880`0103bd42 : fffff880`0103bcb0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x252
fffff880`085455a0 fffff880`010daa04 : fffff880`08545670 fffff880`08545670 fffff880`08545670 fffff8a0`019449e8 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`08545610 fffff800`0332fc16 : fffff880`08545670 fffff980`44d50c10 fffff980`44d50c10 fffffa80`087f4030 : Ntfs!NtfsFsdCleanup+0x144
fffff880`08545880 fffff880`00c02bcf : fffff980`44d50fb0 fffff880`08545920 fffffa80`07bbaae0 fffffa80`079a3d60 : nt!IovCallDriver+0x566
fffff880`085458e0 fffff880`00c016df : fffffa80`085f28e0 fffffa80`085f28e0 fffffa80`08498c00 fffff980`44d50c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`08545970 fffff800`0332fc16 : fffff980`44d50c10 00000000`00000002 fffffa80`085f28e0 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`085459d0 fffff800`03191a0f : fffff980`44d50c10 fffffa80`08147b30 00000000`00000000 fffffa80`07bed6d0 : nt!IovCallDriver+0x566
fffff880`08545a30 fffff800`03181174 : 00000000`00000000 fffffa80`08147b30 00000000`00000001 fffffa80`079b3b80 : nt!IopCloseFile+0x11f
fffff880`08545ac0 fffff800`03180f31 : fffffa80`08147b30 fffffa80`00000001 fffff8a0`03091240 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`08545b40 fffff800`031814f4 : 00000000`00000788 fffffa80`08147b30 fffff8a0`03091240 00000000`00000788 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`08545bd0 fffff800`02e88ed3 : fffffa80`078cf060 fffff880`08545ca0 00000000`fffd5000 00000000`fffd5000 : nt!ObpCloseHandle+0x94
fffff880`08545c20 00000000`7767140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0209e4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7767140a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmCreateKernelStack+e6
fffff800`02e77601 49891cd2        mov     qword ptr [r10+rdx*8],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MmCreateKernelStack+e6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MmCreateKernelStack+e6

BUCKET_ID:  X64_0xA_nt!MmCreateKernelStack+e6

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\JCL III\Windows_NT6_BSOD_jcgriff2\031312-22011-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03054670
Debug session time: Tue Mar 13 02:04:49.754 2012 (UTC - 6:00)
System Uptime: 0 days 5:17:15.314
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffff8003, 1, fffff80002e98348, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SleepInputIdle+79 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffff8003, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e98348, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030be100
 ffffffffffff8003 

FAULTING_IP: 
nt!KeClearEvent+0
fffff800`02e98348 83610400        and     dword ptr [rcx+4],0

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009957950 -- (.trap 0xfffff88009957950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c207fce0 rbx=0000000000000000 rcx=ffffffffffff7fff
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e98348 rsp=fffff88009957ae8 rbp=0000000000000000
 r8=fffffa80093e39a0  r9=000000000000000a r10=0000000000000000
r11=fffff88002fd5100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeClearEvent:
fffff800`02e98348 83610400        and     dword ptr [rcx+4],0 ds:ffffffff`ffff8003=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e379fc to fffff80002e8bc40

STACK_TEXT:  
fffff880`099577e8 fffff800`02e379fc : 00000000`00000050 ffffffff`ffff8003 00000000`00000001 fffff880`09957950 : nt!KeBugCheckEx
fffff880`099577f0 fffff800`02e89d6e : 00000000`00000001 ffffffff`ffff8003 00000000`00000000 fffff900`c272ec20 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`09957950 fffff800`02e98348 : fffff960`0010ca31 00000000`00000000 fffffa80`093e3900 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`09957ae8 fffff960`0010ca31 : 00000000`00000000 fffffa80`093e3900 00000000`00000000 00000000`00000000 : nt!KeClearEvent
fffff880`09957af0 fffff960`0010c90d : fffff900`c272ec00 00000000`0000000d 00000000`00000401 fffff960`00096e00 : win32k!SleepInputIdle+0x79
fffff880`09957b20 fffff960`0010c989 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!xxxRealSleepThread+0x27d
fffff880`09957bc0 fffff960`0011f4f6 : fffffa80`093e3900 fffff880`09957ca0 00000000`76e505ba 00000000`00000000 : win32k!xxxSleepThread+0x59
fffff880`09957bf0 fffff800`02e8aed3 : fffffa80`093e3900 fffff880`09957bd8 00000000`00070168 00000000`fffdc033 : win32k!NtUserWaitMessage+0x46
fffff880`09957c20 00000000`74e32e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ff048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74e32e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SleepInputIdle+79
fffff960`0010ca31 4883c428        add     rsp,28h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!SleepInputIdle+79

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10ff24

FAILURE_BUCKET_ID:  X64_0x50_win32k!SleepInputIdle+79

BUCKET_ID:  X64_0x50_win32k!SleepInputIdle+79

Followup: MachineOwner
---------


[/list]

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.

None of the above crashes were Verified, which means this is probably a hardware problem. You also had the file system on the stack, so it could be corrupted file system data on the hard disk file system.

Disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator ->
verifier /reset
-> Restart your computer.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

JCL III · Mar 18, 2012

Hi again. So I've run all the tests except the windows memory diagnostics tool although it has run and passed before. But I guess ill run it again tonight. Memtest, video memory stress test both had 20+passes no errors.

I didn't know if you wanted the details from the Check Disk event viewer but here you go just in case

Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 175616 file records processed. File verification completed. 99 large file records processed. 0 bad file records processed. 0 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 216336 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 175616 file SDs/SIDs processed. Cleaning up 722 unused index entries from index $SII of file 0x9. Cleaning up 722 unused index entries from index $SDH of file 0x9. Cleaning up 722 unused security descriptors. Security descriptor verification completed. 20361 data files processed. CHKDSK is verifying Usn Journal... 36695352 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 175600 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 228301546 free clusters processed. Free space verification is complete. Windows has checked the file system and found no problems. 976657407 KB total disk space. 63089292 KB in 75099 files. 53240 KB in 20362 indexes. 0 KB in bad sectors. 308691 KB in use by the system. 65536 KB occupied by the log file. 913206184 KB available on disk. 4096 bytes in each allocation unit. 244164351 total allocation units on disk. 228301546 allocation units available on disk. Internal Info: 00 ae 02 00 f1 74 01 00 a0 db 02 00 00 00 00 00 .....t.......... ce 01 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 ....<........... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.

I'm beginning to think that the bluescreens are caused by something that I cannot fix and that I'll just have to build a new computer. I have a couple of more dump files that I'll post. Thank you in advance for any help.

writhziden · Mar 18, 2012

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

Thanks to Dave76 for help learning RAM Stability

JCL III · Mar 18, 2012

So I took a few pictures of the bios settings that I will attach and hopefully they are clear enough for you.

Also some of the voltages that you asked for.
NB VOLTAGE 1.1V
NB1.8V -1.8
SB 1.2V
DRAM 1.5V STANDARD
CPU VDDA 2.5V
HT 1.2V

I don't have anything overclocked or modified in the BIOS, everything is set to Auto. Thanks again

writhziden · Mar 19, 2012

The memory you have appears to be designed for Intel CPUs and may not work with AMD CPUs.

Optimized for Compatibility with the Latest CPUs and Motherboards

Vengeance memory is designed specifically for the latest CPUs. Vengeance modules run at 1.5V for maximum compatibility with all Intel® Core™ i3, i5 and i7 processors, as well as the 2nd generation Intel processor family. Vengeance DDR3 memory is available in single modules, and two or three module kits, making it easy for you to match the DIMM population requirements of your motherboard.

Vengeance®

BSOD playing BF3 error 0x0000001a

New member

My Computer My Computer

At a glance

BSOD Squad

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Squad

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Squad

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Squad

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer