Windows 7 x64
Built the computer hardware myself.
Tried reinstalling drivers doesnt seem to have fixed anything.
It BSOD at least once a day.
The Hardware is maybe a year old.
OS has been on system maybe a month or two.
Please and thank you for any help. If you want to know anymore about my pc just ask.
These were caused by hardware one suggests your video driver and I suspect the second does indirectly
remove video driver
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Run a system file check
SFC /SCANNOW Command - System File Checker
Remove virtual drive software
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: http://www.duplexsecure.com/en/downloads
Let us know if you need help
Ken J
dmp
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\100610-24507-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/;srv*e:\symbols *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 Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e55e50 Debug session time: Wed Oct 6 23:50:11.666 2010 (GMT-4) System Uptime: 0 days 0:17:39.524 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {75012079, d, 1, fffff80002c84b9e} Probably caused by : hardware ( nt!KiInterruptDispatchNoLock+ce ) 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: 0000000075012079, memory referenced Arg2: 000000000000000d, 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: fffff80002c84b9e, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec00e0 0000000075012079 CURRENT_IRQL: d FAULTING_IP: nt!KiInterruptDispatchNoLock+ce fffff800`02c84b9e 208079200175 and byte ptr [rax+75012079h],al CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: EFT.exe TRAP_FRAME: fffff8800824ba50 -- (.trap 0xfffff8800824ba50) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff80002e02e80 rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002c84b9e rsp=fffff8800824bbe0 rbp=fffff8800824bc60 r8=000000000000002b r9=00000000771b71be r10=fffffa8004b33610 r11=0000000000000202 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl nz na pe nc nt!KiInterruptDispatchNoLock+0xce: fffff800`02c84b9e 208079200175 and byte ptr [rax+75012079h],al ds:c056:00000000`75012079=?? Resetting default scope MISALIGNED_IP: nt!KiInterruptDispatchNoLock+ce fffff800`02c84b9e 208079200175 and byte ptr [rax+75012079h],al LAST_CONTROL_TRANSFER: from fffff80002c87ca9 to fffff80002c88740 STACK_TEXT: fffff880`0824b908 fffff800`02c87ca9 : 00000000`0000000a 00000000`75012079 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx fffff880`0824b910 fffff800`02c86920 : fffff880`0824bb00 00000000`039396ac 00000000`75392450 00000000`0008ec70 : nt!KiBugCheckDispatch+0x69 fffff880`0824ba50 fffff800`02c84b9e : fffffa80`04b33610 00000000`0018fe58 fffffa80`04b33610 00000000`0000c056 : nt!KiPageFault+0x260 fffff880`0824bbe0 00000000`0046f9be : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0xce 00000000`0018fe78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x46f9be STACK_COMMAND: kb FOLLOWUP_IP: nt!KiInterruptDispatchNoLock+ce fffff800`02c84b9e 208079200175 and byte ptr [rax+75012079h],al SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiInterruptDispatchNoLock+ce FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
Quote