BSOD - Vista Home Premium x64

cpangker · Feb 15, 2011

Laptop Specs:
About 2 Years old.
Gateway MD2614u.
CPU: AMD Turion X2 Dual-Core Mobile RM-72 2.10 GHz
RAM: 3 Gb
OS: Windows Vista Home Premium SP2 x64 OEM.

Problems:
I get BSOD randomly for some odd reason.

I was doing a windows update, BSOD.
I was running a virus scan, BSOD.
I was running "check for new solution", BSOD.
I was running chkdsk /f /r, BSOD.
I said randomly because it's BSOD the first try I did one of those tasks and for the second try, it was fine.

Please help.
TIA

richc46 · Feb 15, 2011

Code:

icrosoft (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\Temp20_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\Mini021011-02.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.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`01e4b000 PsLoadedModuleList = 0xfffff800`0200fdd0
Debug session time: Thu Feb 10 22:27:49.981 2011 (GMT-5)
System Uptime: 0 days 0:02:35.745
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {10, c, 0, fffff80001ebb194}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+20b )
Followup: MachineOwner
---------
1: 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: 0000000000000010, memory referenced
Arg2: 000000000000000c, 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: fffff80001ebb194, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002072080
 0000000000000010 
CURRENT_IRQL:  c
FAULTING_IP: 
nt!IopCompleteRequest+b74
fffff800`01ebb194 4c8b4910        mov     r9,qword ptr [rcx+10h]
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  PresentationSet
IRP_ADDRESS:  ffffffffffffff88
TRAP_FRAME:  fffffa600059f450 -- (.trap 0xfffffa600059f450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa6004fce3e8 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001ebb194 rsp=fffffa600059f5e0 rbp=fffffa80050ee478
 r8=0000000000000000  r9=fffffa600059f6d0 r10=fffffa800214f590
r11=fffffa80073d8a80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!IopCompleteRequest+0xb74:
fffff800`01ebb194 4c8b4910        mov     r9,qword ptr [rcx+10h] ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80001ea522e to fffff80001ea5490
STACK_TEXT:  
fffffa60`0059f308 fffff800`01ea522e : 00000000`0000000a 00000000`00000010 00000000`0000000c 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0059f310 fffff800`01ea410b : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`050ee400 : nt!KiBugCheckDispatch+0x6e
fffffa60`0059f450 fffff800`01ebb194 : 00000000`00000202 fffff800`01eb3700 fffffa80`06bb5bb0 fffff800`01ea7c7f : nt!KiPageFault+0x20b
fffffa60`0059f5e0 fffff800`01ec6bbe : 00000000`00000000 fffffa80`06bb5bb0 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0xb74
fffffa60`0059f6a0 fffff800`01ea79af : fffffa80`047fd710 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x19e
fffffa60`0059f740 fffff800`01e9c38b : 00000000`5d1ed695 fffffa80`06bb5bb0 fffffa80`047fd710 fffffa60`00000008 : nt!KiSwapThread+0x3ef
fffffa60`0059f7b0 fffff800`01ed13ab : 00000000`00000000 00000000`0000001b fffffa80`031dc600 fffffa80`06a36600 : nt!KeWaitForSingleObject+0x2cb
fffffa60`0059f840 fffff800`01eaca75 : ffffffff`ffb3b4c0 fffffa80`04494b40 00000000`00000001 00000000`00000103 : nt!ExpWaitForResource+0x43
fffffa60`0059f8a0 fffffa60`010234c4 : fffffa80`0705f170 fffff880`0016aaa0 00000000`00000000 fffffa80`04426aac : nt!ExAcquireResourceExclusiveLite+0xa5
fffffa60`0059f8f0 fffffa60`010cdf37 : fffff880`0016aaa0 fffffa80`06898010 fffff880`0016abd0 fffffa80`0705f010 : Ntfs!NtfsAcquireExclusiveFcb+0x64
fffffa60`0059f940 fffffa60`01023e29 : 00000000`00000000 00000000`00000000 fffffa60`04fce2d0 fffffa80`06bb5bb0 : Ntfs!NtfsCommonCleanup+0x277
fffffa60`0059fd30 fffff800`01e9f537 : fffffa60`04fce2d0 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCleanupCallout+0x19
fffffa60`0059fd60 fffff800`01e9f4ee : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`01eb6eca : nt!KxSwitchKernelStackCallout+0x27
fffffa60`04fce200 fffff800`01eb6eca : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
fffffa60`04fce220 fffffa60`01021f82 : fffffa60`04fce370 fffffa60`04fce370 fffffa80`06898010 fffffa80`06898010 : nt!KeExpandKernelStackAndCalloutEx+0x19a
fffffa60`04fce2a0 fffffa60`010d7f78 : fffffa60`04fce370 fffffa80`06898010 fffffa60`04fce370 fffffa60`04fce520 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffffa60`04fce310 fffffa60`00a08e91 : fffffa60`04fce370 fffffa80`06898010 fffffa80`06898368 00000000`00000000 : Ntfs!NtfsFsdCleanup+0x138
fffffa60`04fce570 fffffa60`00a070dd : fffffa80`04481040 00000000`00000000 fffffa80`025ce800 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x211
fffffa60`04fce5e0 fffff800`02112b84 : fffffa80`07459050 00000000`00000004 fffffa80`06bb5b01 fffff880`0ad24a50 : fltmgr!FltpDispatch+0xcd
fffffa60`04fce640 fffff800`021081f0 : 00000000`00000000 fffffa80`07459050 fffff880`0addf020 fffff880`0b61b680 : nt!IopCloseFile+0x184
fffffa60`04fce6d0 fffff800`0210fd87 : fffff880`0addf020 fffffa80`00000001 fffffa80`07151040 00000000`00000000 : nt!ObpDecrementHandleCount+0xc0
fffffa60`04fce760 fffff800`020f2fc8 : fffff880`0ad6f7e0 00000000`00000200 fffffa80`06bb5bb0 00000000`00000008 : nt!ObpCloseHandleTableEntry+0xb7
fffffa60`04fce800 fffff800`020f2f47 : 00000000`00000004 fffff800`020d6506 fffffa80`07151040 00000000`00000001 : nt!ObpCloseHandleProcedure+0x30
fffffa60`04fce840 fffff800`020f3ad1 : fffff880`0addea01 fffff800`020f21a0 fffffa80`07151040 fffff880`0ad6f7e0 : nt!ExSweepHandleTable+0x73
fffffa60`04fce870 fffff800`020fe7cd : fffff880`0addeab0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObKillProcess+0x61
fffffa60`04fce8b0 fffff800`020f21bd : fffffa60`00000000 fffff800`0210c501 000007ff`fffd6000 fffffa80`78457350 : nt!PspExitThread+0x46d
fffffa60`04fce9a0 fffff800`01ec6e61 : fffffa60`04fcea01 fffffa80`0651e610 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffffa60`04fce9d0 fffff800`01eca785 : fffffa60`04fceca0 fffffa60`04fcea70 fffff800`020f21d0 00000000`00000001 : nt!KiDeliverApc+0x441
fffffa60`04fcea70 fffff800`01ea4fdd : fffff880`00644078 fffffa80`07309840 fffffa80`073edeb0 00000000`00000000 : nt!KiInitiateUserApc+0x75
fffffa60`04fcebb0 00000000`775f6eca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xa2
00000000`02a0f458 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775f6eca
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiPageFault+20b
fffff800`01ea410b 488b0546e31c00  mov     rax,qword ptr [nt!KiInterlockedPopEntrySListResumeEntryPoint (fffff800`02072458)]
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiPageFault+20b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4cb7275f
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+20b
BUCKET_ID:  X64_0xA_nt!KiPageFault+20b
Followup: MachineOwner
---------

You have given me quite a few reports. The majority of them blame a Microsoft Driver, which is actually not the true culprit. Many also mentioned, but did not blame memory, so lets start there.
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If passes try a good stick in each slot for 3 passes
If fails do the same for 8 passes.

cpangker · Feb 15, 2011

Will do tonight and get back to you.

Thanks. :geek:

richc46 · Feb 15, 2011

Take your time, understand each step, ask questions. There is no rush, lets do it right. In case it does not work, we know that the problem is not the memory and we can move on to something else.

cpangker · Feb 16, 2011

Ran RAM test as instructed and received 0 error.
What's next?

Thanks.
Cp

richc46 · Feb 16, 2011

Did you run it for about 6-8 hours and then did you test the slots?

cpangker · Feb 19, 2011

Yes sir.
RAM and the slot is good and healthy. :party:

Regards.

richc46 · Feb 19, 2011

Driver Verifier Inst
Since the driver that crashed you has not been listed you should run driver verifier
Please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Enable the driver verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

BSOD - Vista Home Premium x64

cpangker

New Member

My Computer

System One

richc46

My Computer

System One

cpangker

New Member

My Computer

System One

richc46

My Computer

System One

cpangker

New Member

My Computer

System One

richc46

My Computer

System One

cpangker

New Member

My Computer

System One

richc46

My Computer

System One