BSODs (at seemingly random moments)

3ASUSFan · 09 Jun 2011

Hi!

I've been having these random BSODs for about a month now, and I have no idea what the cause is. The PC runs perfectly fine for a few days and then sometimes just starts having a BSOD several times whihtin a few hours. I've tried returning the PC to an earlier state, upgrading the drivers and it didn't help.

I hope you guys can help me because it's getting pretty annoying.

My Windows 7 did not come pre installed and is downloaded from MSDN. (for further system specs, look @ profile please)

richc46 · 09 Jun 2011

Code:

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_Windows_NT6_BSOD_jcgriff2+Perfom.zip\Windows_NT6_BSOD_jcgriff2\053011-27924-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
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03a12000 PsLoadedModuleList = 0xfffff800`03c57650
Debug session time: Mon May 30 14:40:18.096 2011 (GMT-4)
System Uptime: 0 days 0:12:33.298
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {48, 2, 1, fffff80003b3a01f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
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: 0000000000000048, 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: fffff80003b3a01f, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cc1100
 0000000000000048 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MiIdentifyPfn+26f
fffff800`03b3a01f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
TRAP_FRAME:  fffff88008c3c4e0 -- (.trap 0xfffff88008c3c4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0800000000000020
rdx=0000000000092632 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003b3a01f rsp=fffff88008c3c670 rbp=fffffa8005344090
 r8=0000000000092633  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiIdentifyPfn+0x26f:
fffff800`03b3a01f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh ds:00000000`00000048=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80003a912a9 to fffff80003a91d00
STACK_TEXT:  
fffff880`08c3c398 fffff800`03a912a9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08c3c3a0 fffff800`03a8ff20 : 00000000`42506650 00000000`00000000 00000000`00000000 02800000`00092629 : nt!KiBugCheckDispatch+0x69
fffff880`08c3c4e0 fffff800`03b3a01f : 00000000`00000000 02000000`0009262a 00000000`42506600 fffff800`03d7cdff : nt!KiPageFault+0x260
fffff880`08c3c670 fffff800`03b3accb : 00000000`00000000 00000000`00000004 fffffa80`0415f438 fffffa80`0415e000 : nt!MiIdentifyPfn+0x26f
fffff880`08c3c710 fffff800`03e9f9e5 : fffffa80`0415e000 fffff880`08c3cca0 fffff880`08c3c7e8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`08c3c750 fffff800`03de26c8 : 00000000`00000006 00000000`00000000 fffffa80`0415e000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`08c3c7a0 fffff800`03d9b263 : 00000000`00000000 00000000`00000000 00000000`64496d4d 00000000`64496d01 : nt! ?? ::NNGAKEGL::`string'+0x48c6d
fffff880`08c3c830 fffff800`03d9bad9 : 00000000`01fbbbc8 fffff800`04005895 00000000`01fbbc20 fffff880`08c3cca0 : nt!ExpQuerySystemInformation+0x1193
fffff880`08c3cbe0 fffff800`03a90f93 : fffffa80`06379b60 00000000`02f1d6c0 00000000`0696f201 00000000`07c47568 : nt!NtQuerySystemInformation+0x4d
fffff880`08c3cc20 00000000`7794167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01fbbae8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7794167a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiIdentifyPfn+26f
fffff800`03b3a01f f0410fba6e481f  lock bts dword ptr [r14+48h],1Fh
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nt!MiIdentifyPfn+26f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
Followup: MachineOwner
---------

Apparently your computer has problems with memory.
Please follow these instructions for memory test.
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If it passes try a good stick in each slot for 3 passes
If it fails do the same for 8 passes.
Here is some additional information to help explain the procedure
http://www.geekstogo.com/forum/topic...ing-memtest86/

mgorman87 · 09 Jun 2011

Code:

sptd.sys     Sun Mar 22 08:35:35 2009 (49C63097)

Remove Daemon Tools/Alcohol 120%. Its driver, SPTD, is known to cause BSODs in Windows 7. Once the program is removed run the SPTD removal tool. DuplexSecure

Run Memtest86 for 7-8 passes - RAM - Test with Memtest86+. Report back the results

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun  9 18:43:26.167 2011 (UTC - 4:00)
System Uptime: 0 days 9:22:45.369
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun  7 18:23:02.117 2011 (UTC - 4:00)
System Uptime: 1 days 20:00:44.319
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
BiosReleaseDate = 04/08/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 30 14:40:18.096 2011 (UTC - 4:00)
System Uptime: 0 days 0:12:33.298
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+26f
BiosReleaseDate = 02/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat May 28 20:17:13.089 2011 (UTC - 4:00)
System Uptime: 0 days 4:53:02.681
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+110
BiosReleaseDate = 02/17/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3ASUSFan · 09 Jun 2011

Hmmm, I've had Deamon Tools for a very long time and I didn't start having BSOD's until recently. I'll look into that if the memory test procedure you guys suggested doesn't help. I'll do that tomorrow and report back.

Thanks for the help. :)

richc46 · 09 Jun 2011

Although not included in my report, I suggest that you remove Daemon, too. If needed there is similar software that can be used.
Daemon is a known cause of BSODs and because you did not have them before is no proof that it cannot be the cause now or the future. The immediate cause, however is memory.

3ASUSFan · 12 Jun 2011

Ok, I've left the memtest on overnight and got 13 passes. No errors at all. After I restarted the PC I got a BSOD after several minutes though. I'll try different slots tonight. I've also tried the Windows built in memory and HDD check after restart, didn't show any negative results.

Btw, I remember having the first BSOD shortly after updating the Realtek HD Audio driver. Could that be related? I mean, if it is, you'd see it in the logs right?

I've removed Daemon Tool Lite. Do you guys know any good alternatives?

richc46 · 12 Jun 2011

Daemon replacement
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Your reports were all consistent and conclusive, they all point toward memory.
Take a good stick and test each slot.
Did you ever buy RAM? If so did you mix and match?

3ASUSFan · 12 Jun 2011

What do you mean whith a good stick? You mean one which I know is fine? Problem is I don't know which of both is or isn't since I've got no errors in any test. But like I said, I'll try different slots tonight, and I'll also try a single stick in all slots.

And the RAM I've got was a pair (2x2GB). So I could run it in Dual Channel mode. I bought it when I upgraded my whole system in late 2010 (went from AMD 939 socket to AM3 socket).

Thanks for the alternative for Deamon btw.

richc46 · 12 Jun 2011

I realize that your memory testing is not over. Take a good stick and test each slot for at least 4-5 pases. If this comes up negative, I have another idea. I have noticed that most if not all your BSODs were caused within the process of svchost.exe
I know from past experience that this is a hiding place for virus. To be on the safe side, run a full, updated anti virus scan and download and make a full scan with malwarebytes. May be negative, but scans can never be the wrong thing to do.

3ASUSFan · 08 Aug 2011

I did the memtest on both stick, in all slots for 8 passes, no errors. Also multiple full system scans, with MSE and no viruses or malware. I reinstalled Windows 7 twice since last time I replied, once on my old drive and once on my new SSD. Since I reinstalled Windows the first time the driver causing the issue seems to be ntoskrnl.exe now. I also just reflashed my BIOS to an older one (thought it might be a BIOS problem), but it doesn't seem to help because I just had a BSOD a moment ago (while typing a reply with an update here -_-, lucky me).