BSOD or Freeze Vista 64 bit

[TurtleKing]

I think I am going to try the suggestions you mentioned for a possible fix. I really can't monitor the computer for that along, and keeping it only doing that as well. So hopefully one of those suggested fixes will bring this baby back to normal.

 

[TurtleKing]

I noticed I did not answer your fan question from a previous reply. The noise does seem to be coming from a fan. However, since the 3 fans (behind the case, above the case, and cpu fan) are close to each other I can't really pin point an exact location of which one is causing it. To me it sounds like the cpu fan.

On other note, I wanted to ask you if their was a power supply or motherboard stress test or problem detector? If so, are they just as long, and require careful monitoring?

I am contemplating on just buying a new cpu, after I receive my 120mm [intake] fan and fan-filter, and the computer gets the extra cooling help of a intake fan but still randomly crashes.

One of the difficulties I had with this BSOD on vista and restart on ubuntu, is that I had it while the computer is doing nothing and when running a video game. I understand overheating with a video game, but doing nothing? Also, it would be great if it happened when I ran a software or something, but its not consistent with anything since sometimes it crashed on something as simple as opening one of the mini-dumps? For this reason, I am sure it is one of the hardwares or a fan is possibly failing.

 

[richc46]

Here is some information on testing power supply; equipment will be required
Power Supply Test - How Do I Test the Power Supply in My Computer? - PSU Test

 

[TurtleKing]

Got a different BSOD while still waiting for power supply tester by mail. Maybe this one might give a better hint as to what might be the overall problem. The title for the BSOD was, "page fault in nonpaged area".

 

[richc46]

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Mini112010-01[1].zip\Mini112010-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`0205b000 PsLoadedModuleList = 0xfffff800`0221fdd0
Debug session time: Sat Nov 20 02:29:27.713 2010 (GMT-5)
System Uptime: 0 days 2:32:18.061
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6ffffc433e0, 0, fffff800020d806e, 2}
 
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiUpdateWsle+29e )
Followup: MachineOwner
---------
0: 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: fffff6ffffc433e0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800020d806e, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
 
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002282080
 fffff6ffffc433e0 
FAULTING_IP: 
nt!MiUpdateWsle+29e
fffff800`020d806e 498b00          mov     rax,qword ptr [r8]
MM_INTERNAL_CODE:  2
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  ~e5.0001
CURRENT_IRQL:  0
TRAP_FRAME:  fffffa600fe896f0 -- (.trap 0xfffffa600fe896f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=0000098000000000
rdx=ffffffff8867c001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800020d806e rsp=fffffa600fe89880 rbp=00000000000000da
 r8=fffff6ffffc433e0  r9=0200000000000000 r10=0000000fffffffff
r11=fffffa8000000028 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiUpdateWsle+0x29e:
fffff800`020d806e 498b00          mov     rax,qword ptr [r8] ds:fffff6ff`ffc433e0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002115ada to fffff800020b54d0
STACK_TEXT:  
fffffa60`0fe89608 fffff800`02115ada : 00000000`00000050 fffff6ff`ffc433e0 00000000`00000000 fffffa60`0fe896f0 : nt!KeBugCheckEx
fffffa60`0fe89610 fffff800`020b4059 : 00000000`00000000 fffffa80`0396ab00 fffffa60`0fe89a00 fffff700`01080498 : nt! ?? ::FNODOBFM::`string'+0x2c465
fffffa60`0fe896f0 fffff800`020d806e : fffff700`01080498 00000000`000000da fffffa80`04471330 00000000`00000001 : nt!KiPageFault+0x119
fffffa60`0fe89880 fffff800`020ceff0 : fffff700`01080498 fffff680`003bcc18 00000000`00000000 00000000`00000000 : nt!MiUpdateWsle+0x29e
fffffa60`0fe898e0 fffff800`020cf2d9 : 00000000`000005e5 00000000`a8968121 00000000`779838c9 fffffa80`01f9c380 : nt!MiCompleteProtoPteFault+0x270
fffffa60`0fe89960 fffff800`020cdfd0 : 00000000`00000510 00000000`00000000 00000000`0045f120 fffffa80`04471330 : nt!MiResolveProtoPteFault+0x129
fffffa60`0fe899e0 fffff800`020cb9dd : 00000000`00000000 00000000`779838c9 fffffa80`082853d0 00000000`00000000 : nt!MiDispatchFault+0x190
fffffa60`0fe89b40 fffff800`020b4059 : 00000000`00000008 00000000`02f0f908 00000000`00000001 00000000`0045e2c0 : nt!MmAccessFault+0x32d
fffffa60`0fe89c20 00000000`779838c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
00000000`0045dfd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779838c9
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiUpdateWsle+29e
fffff800`020d806e 498b00          mov     rax,qword ptr [r8]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!MiUpdateWsle+29e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e5ae3
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x50_nt!MiUpdateWsle+29e
BUCKET_ID:  X64_0x50_nt!MiUpdateWsle+29e
Followup: MachineOwner
---------

This one comes up code 50. It gives memory as a cause. Based on this and the prior BSOD, I would tend to agree.
These reports are like puzzle pieces. Two said hardware, this one says memory. Mermory is considered hardware; ram.
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If errors are not found, run a good stick in each slot for 3 passes
If errors are found run a good stick in each slot for 8 passes.

 

[TurtleKing]

Oh cool, I can afford new memory sticks as these were affordable compared to the other stuff. Anyways, when you say, "If errors are not found, run a good stick in each slot for 3 passes"; You mean like take one of the two sticks out and test it individually? My hypothesis from this BSOD is, maybe it has been passing memtest86 in the past since one of them perhaps is making up for the others errors. I hope this is true. lol

 

[richc46]

RAM errors can occur for two reasons
Bad sticks or bad slots
If you pass the test
Take one good stick and test each slot for 3 passes.
Remember the reports are like puzzle pieces we get closer each time, but the memtest may turn out negative.