Solved Random BSOD-ongoing problem

BFHunter · Mar 21, 2012

I've been having a problem for quite a while. My Computer has been blue-screening frequently for months now. The BSODs happen most often when I'm trying to play games(doesn't matter what game), but it also happens when I'm browsing the internet, listening to music, using MS word ect. The point is, it's completely random, and is really getting on my nerves

On top of that, the error codes change almost every time. The "IRQL is not less than or equal to" is pretty common, but it also says "System Exception" and several others.
I have tried wiping my hard drive and reinstalling my OS(Windows Vista, which I replace with the Windows 7 upgrade I got when Windows 7 was first released), but it still had a BSOD.
I have no idea what's going on. my dump files zip is attached.
Any help is greatly appreciated

And if it will help, my PC is scratch built. Here's the specs I have right now
video card: XFX 6850
Processor:AMD Phenom II X4 975
Ram 2 Corsair XMS3 4GB DDR3 sticks
Hard drive: Western Digital 1TB
PS-the antivirus warning is because I haven't added AVG yet. I had the latest version of Norton before I reinstalled my OS

BFHunter · Mar 21, 2012

It just crashed again-the error this time was "Page Fault in nonpaged area"

here's what my PC says about it

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFFFFFFFFFFF8B
BCP2: 0000000000000001
BCP3: FFFFF80002EF1573
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

BFHunter · Mar 22, 2012

Ok, I just got ANOTHER one.
That makes four in one day, and I just finished a clean install of my OS.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFF80003E46CE9
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002EC90F9
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

writhziden · Mar 22, 2012

Security Software: ???

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\BFHunter\Windows_NT6_BSOD_jcgriff2\032112-18439-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03058e50
Debug session time: Wed Mar 21 17:28:00.255 2012 (UTC - 6:00)
System Uptime: 0 days 0:04:33.893
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff87ff09a9c98, 2, 0, fffff80002ed4099}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+5e4 )

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: fffff87ff09a9c98, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002ed4099, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c30e0
 fffff87ff09a9c98 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmZeroPageThread+5e4
fffff800`02ed4099 0fb6842488000000 movzx   eax,byte ptr [rsp+88h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009a9a80 -- (.trap 0xfffff880009a9a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004fe06f0 rbx=0000000000000000 rcx=fffff880009a9c68
rdx=fffffa8000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed4099 rsp=fffff880009a9c10 rbp=00000000000000ff
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8006a82e10
r11=fffff880009a9c08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MmZeroPageThread+0x5e4:
fffff800`02ed4099 0fb6842488000000 movzx   eax,byte ptr [rsp+88h] ss:0018:fffff880`009a9c98=00
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8c469 to fffff80002e8cf00

STACK_TEXT:  
fffff880`009a9938 fffff800`02e8c469 : 00000000`0000000a fffff87f`f09a9c98 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009a9940 fffff800`02e8b0e0 : fffffa80`04fdffd0 00000000`001a9600 fffffa80`04fdffd0 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a80 fffff800`02ed4099 : 00000000`000000ff 00000000`00000026 00000000`00000026 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9c10 fffff800`03130166 : fffffa80`06ba5040 00000000`00000080 fffffa80`06b2c9e0 fffff800`02e6b479 : nt!MmZeroPageThread+0x5e4
fffff880`009a9d40 fffff800`02e6b486 : fffff800`03005e80 fffffa80`06ba5040 fffff800`03013c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmZeroPageThread+5e4
fffff800`02ed4099 0fb6842488000000 movzx   eax,byte ptr [rsp+88h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MmZeroPageThread+5e4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MmZeroPageThread+5e4

BUCKET_ID:  X64_0xA_nt!MmZeroPageThread+5e4

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\BFHunter\Windows_NT6_BSOD_jcgriff2\032012-20326-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Tue Mar 20 23:10:43.138 2012 (UTC - 6:00)
System Uptime: 0 days 0:19:23.777
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880062562e8, fffff88006255b40, fffff8800130ea6c}

Probably caused by : hardware ( Ntfs!NtfsWriteLog+49c )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880062562e8
Arg3: fffff88006255b40
Arg4: fffff8800130ea6c

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


EXCEPTION_RECORD:  fffff880062562e8 -- (.exr 0xfffff880062562e8)
ExceptionAddress: fffff8800130ea6c (Ntfs!NtfsWriteLog+0x000000000000049c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 00000000ffffff8a
Attempt to write to address 00000000ffffff8a

CONTEXT:  fffff88006255b40 -- (.cxr 0xfffff88006255b40)
rax=00000000ffffffff rbx=0000000000000000 rcx=fffffa800925e010
rdx=fffffa8007216b60 rsi=fffff880062566b0 rdi=fffffa8007c55028
rip=fffff8800130ea6c rsp=fffff88006256520 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000001800000028
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000702 r15=fffffa800851f690
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs!NtfsWriteLog+0x49c:
fffff880`0130ea6c 10488b          adc     byte ptr [rax-75h],cl ds:002b:00000000`ffffff8a=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  msiexec.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  00000000ffffff8a

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af0e0
 00000000ffffff8a 

FOLLOWUP_IP: 
Ntfs!NtfsWriteLog+49c
fffff880`0130ea6c 10488b          adc     byte ptr [rax-75h],cl

FAULTING_IP: 
Ntfs!NtfsWriteLog+49c
fffff880`0130ea6c 10488b          adc     byte ptr [rax-75h],cl

BUGCHECK_STR:  0x24

MISALIGNED_IP: 
Ntfs!NtfsWriteLog+49c
fffff880`0130ea6c 10488b          adc     byte ptr [rax-75h],cl

LAST_CONTROL_TRANSFER:  from fffff880012fa4f6 to fffff8800130ea6c

STACK_TEXT:  
fffff880`06256520 fffff880`012fa4f6 : 00000000`00000000 fffffa80`0925e010 00000000`00000000 fffff880`062567b0 : Ntfs!NtfsWriteLog+0x49c
fffff880`06256770 fffff880`01268f51 : fffffa80`0851f690 00000000`00000000 fffffa80`0925e010 fffffa80`0851f690 : Ntfs!NtfsCommitCurrentTransaction+0x126
fffff880`06256800 fffff880`012f2dfa : fffff8a0`077092d0 fffffa80`07c68180 00000000`00000000 fffff880`0102d100 : Ntfs!NtfsExtendedCompleteRequestInternal+0x131
fffff880`06256840 fffff880`01261e0c : fffffa80`0925e010 fffffa80`0851f690 fffff880`06256901 fffff880`06256900 : Ntfs!NtfsCommonSetInformation+0xef1
fffff880`06256920 fffff880`0102723f : fffff880`06256a50 fffffa80`0851f690 fffffa80`0925e010 fffff880`06256948 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`062569a0 fffff880`010256df : fffffa80`07c63de0 fffffa80`0851f690 fffffa80`07c63d00 fffffa80`0851f690 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`06256a30 fffff800`03159142 : 00000000`00000008 fffff880`06256ca0 fffffa80`0851f690 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`06256a90 fffff800`02e78153 : 00000000`00000344 fffffa80`07216b60 00000000`0084f458 ffffffff`00000008 : nt!NtSetInformationFile+0x5ae
fffff880`06256bb0 00000000`7707012a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0084f438 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7707012a


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsWriteLog+49c

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88006255b40 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_Ntfs.sys

BUCKET_ID:  X64_IP_MISALIGNED_Ntfs.sys

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... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

If you are overclocking any hardware, please stop.
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.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Install all Windows Updates.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then 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 http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
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.

BFHunter · Apr 6, 2012

Well, I had my computer inspected, and I was told the hard drive was the problem. I've replaced it, but I've had three bluescreens today. I really don't get what the problem is, and I don't want to spend another $70 to get it rechecked since Fry's screwed up the first time

That said, here's my new system report

writhziden · Apr 6, 2012

Problem Devices:

Code:

Ethernet Controller	PCI\VEN_10EC&DEV_8168&SUBSYS_76401462&REV_06\4&1117575A&0&0028	The drivers for this device are not installed.

Security Software (just to check it is working and installed; nothing needs to be done with this information at this time):

Code:

mpcmdrun.exe	c:\program files\microsoft security client\antimalware\mpcmdrun.exe	3172	8	200	1380	4/5/2012 11:01 PM	3.0.8402.0	266.95 KB (273,352 bytes)	4/27/2011 5:21 PM
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	888	8	200	1380	4/5/2012 11:00 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2776	8	200	1380	4/5/2012 11:00 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\BFHunter\Windows_NT6_BSOD_jcgriff2\040599-15802-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Sun Apr  5 20:36:31.246 2099 (UTC - 6:00)
System Uptime: 0 days 0:03:29.885
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff80002e9203d, fffff880009a98f8, fffff880009a9150}

Probably caused by : hardware ( nt!KiCommitThreadWait+1bd )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002e9203d, The address that the exception occurred at
Arg3: fffff880009a98f8, Exception Record Address
Arg4: fffff880009a9150, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100          add     word ptr [rax],ax

EXCEPTION_RECORD:  fffff880009a98f8 -- (.exr 0xfffff880009a98f8)
ExceptionAddress: fffff80002e9203d (nt!KiCommitThreadWait+0x00000000000001bd)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880009a9150 -- (.cxr 0xfffff880009a9150)
rax=0000000000000000 rbx=fffffa8006b8bb60 rcx=0000000000000001
rdx=fffff80003011c40 rsi=fffffa8006b8bc20 rdi=fffff80003003e80
rip=fffff80002e9203d rsp=fffff880009a9b30 rbp=fffffa8006b8bb60
 r8=fffffa8006a87050  r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000060 r13=000000c832e6baa9
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!KiCommitThreadWait+0x1bd:
fffff800`02e9203d 660100          add     word ptr [rax],ax ds:002b:00000000`00000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

MISALIGNED_IP: 
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100          add     word ptr [rax],ax

LAST_CONTROL_TRANSFER:  from fffff80002ed24c5 to fffff80002e9203d

FAILED_INSTRUCTION_ADDRESS: 
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100          add     word ptr [rax],ax

STACK_TEXT:  
fffff880`009a9b30 fffff800`02ed24c5 : fffffa80`06b8bb60 00000000`00000000 fffff800`00000000 00000000`00000091 : nt!KiCommitThreadWait+0x1bd
fffff880`009a9bc0 fffff800`02ed1daa : fffffa80`06a82800 00000000`00000008 00000000`000000ff 00000000`00000000 : nt!KeWaitForGate+0x101
fffff880`009a9c10 fffff800`0312e166 : fffffa80`06b8bb60 00000000`00000080 fffffa80`06b27890 fffff800`02e69479 : nt!MmZeroPageThread+0x2ed
fffff880`009a9d40 fffff800`02e69486 : fffff800`03003e80 fffffa80`06b8bb60 fffff800`03011c40 00002640`e8000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a7700 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
nt!KiCommitThreadWait+1bd
fffff800`02e9203d 660100          add     word ptr [rax],ax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiCommitThreadWait+1bd

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880009a9150 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Your latest crashes are still pointing to hardware... Also, why does the latest date have a year of 2099?

You can probably get the system inspected for free since Fry's screwed up. Most support companies have a guarantee for their services. Did you proceed with the hardware checks in my previous post? What were the results?

Note: the hard disk check may still be worth running in case the new drive is faulty, as well, but it's up to you. You could just run the disk check with "Automatically fix file system errors" to check for corrupted data which takes 5-10 minutes instead of an hour or two with both boxes checked.

You should also try to get your latest Windows Updates installed.

BFHunter · Apr 6, 2012

To answer your question about the date, that was just a system fluke when I was setting it up again
I've run the Memtest and the VGA stress test-both passes without any problems. I'll run the disk check in ten minutes or so, then I'll move from there

writhziden · Apr 6, 2012

Ah, okay. Thanks for the data information. Hopefully that isn't a sign of CMOS problems... Never seen a date that far in the future in that scenario, though. Not sure what would cause it.

When you say you ran memtest, do you mean for the video card or Memtest86+ for seven passes or more?

Let us know how the disk check goes. Best of luck!

BFHunter · Apr 6, 2012

I've finished the disk check. The log's linked down below
As to the other question, it was Memtest 86+. I ran it for 8 passes, and it didn't come up with any errors
ON a side note, I've got a new error. The PC keeps making the "You've just BSOD'd" electronic noises and freezes for a second. then it stops doing it, then does it again. No idea what that's about

writhziden · Apr 6, 2012

Recommend running disk check again since it made corrections to the file system.

What do you mean by BSOD noises?

BFHunter · Apr 7, 2012

It sounded a bit like this:
Blue Screen Of Death With Sound - YouTube
but mine was a lot louder, and had considerably more buzz

writhziden · Apr 7, 2012

That usually means RAM, graphics card, or CPU. Test your RAM as in Part 3 of http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html, but instead of using Memtest86+ to test each individual module in each individual slot, just do your normal routine in Windows. See if one module/slot provides more stability in Windows than another. Try to determine if you have a bad module or slot that way.

BFHunter · Apr 8, 2012

Well, now I'm really upset. I just got a BSOD that lists the problem as an uncorrectable hardware error
details below:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8008461028
BCP3: 00000000B6004000
BCP4: 00000000D6000175
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

any insights you can glean from that? also, are there any tests I can run on the CPU and motherboard?
Also, I'm currently running the memory test for my graphics card. I'll post the results once they're done

writhziden · Apr 9, 2012

One CPU test is included in my earlier post. I include two here for convenience (remember to monitor temperatures):

Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
Follow the steps for doing a CPU stress test using IntelBurnTest

BFHunter · Apr 15, 2012

Well, as it turns out it was a really bizarre error. Somehow my bios was overclocking my CPU and ram as its default setting. The fry's guys fixed that, and it's been perfect since then. Thank you very much!

writhziden · Apr 15, 2012

Glad to see your solution was a BIOS tweak. Recommend writing down the current settings if default settings do not work for you. Wish you all the best!

Solved Random BSOD-ongoing problem

New member

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer