blue screen windows 7 64bit

Strange. May I suggest a clean install of Windows?

Drewbie said:

blue screen view will help you isolate the problem and get specific information about it
you then will just have to research those issues but at least you can get more specific info
<<<<Blue screen of death (STOP error) information in dump files. >>>>>>>>
I did not read this thread and don't know if thats been suggested
good luck

Hello Drew,

We use Windbg instead. It is much more accurate than BlueScreenView.

Probably Caused By: hardware.

Please follow my instructions here: https://www.sevenforums.com/crashes-d...tml#post785751

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\061710-17768-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e95e50
Debug session time: Thu Jun 17 18:21:56.632 2010 (UTC - 4:00)
System Uptime: 0 days 0:41:06.536
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fc4acf, fffff88006dd80c0, 0}

Probably caused by : hardware ( nt!IoRemoveIoCompletion+13f )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fc4acf, Address of the instruction which caused the bugcheck
Arg3: fffff88006dd80c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!IoRemoveIoCompletion+13f
fffff800`02fc4acf 0000            add     byte ptr [rax],al

CONTEXT:  fffff88006dd80c0 -- (.cxr 0xfffff88006dd80c0)
rax=0000000000000000 rbx=fffffa80064f2ca0 rcx=fffff88006dd8ac8
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000001
rip=fffff80002fc4acf rsp=fffff88006dd8a90 rbp=fffff88006dd8ca0
 r8=fffff80002c58000  r9=0000000000000000 r10=fffffffffffffffd
r11=fffff88006dd8a60 r12=0000000000000000 r13=fffff88006dd8ba8
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!IoRemoveIoCompletion+0x13f:
fffff800`02fc4acf 0000            add     byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  pol.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!IoRemoveIoCompletion+13f
fffff800`02fc4acf 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from fffff80002cd8996 to fffff80002fc4acf

STACK_TEXT:  
fffff880`06dd8a90 fffff800`02cd8996 : 00000000`00000001 fffff880`06dd8ba8 fffff880`06dd8bc8 00000000`00000001 : nt!IoRemoveIoCompletion+0x13f
fffff880`06dd8b20 fffff800`02cc7853 : fffffa80`03fc6060 00000000`7ef95000 fffff880`06dd8ca0 00000000`7ef95000 : nt!NtWaitForWorkViaWorkerFactory+0x285
fffff880`06dd8c20 00000000`772917ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`058fe7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772917ba


FOLLOWUP_IP: 
nt!IoRemoveIoCompletion+13f
fffff800`02fc4acf 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!IoRemoveIoCompletion+13f

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88006dd80c0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

It could still point to either, unfortunately. CPU is most likely, but motherboard is next.

See if you can borrow a CPU or PSU from someone else.