BSOD Windows 7 Ultimate X64, All Files Attached

jim12 · 27 Feb 2012

The Zip file according to the guide was too big to attach to the post so I have uploaded it here.

System is Windows 7 Ultimate X64, have tried reading the debug files but am not sure what is causing the problem.

Any help would be appreciated, thanks.

panais · 27 Feb 2012

Hi. :)

Just go to C:\windows\minidump copy paste the 5-6 most recent minidumps in you desktop,zip them in folder and upload this folder here.

jim12 · 27 Feb 2012

Thanks, Have attached the zip file

writhziden · 27 Feb 2012

Possible out of date drivers:

Code:

PxHlpa64	fffff880`00c96000	fffff880`00ca1700	Wed Oct 17 12:25:02 2007 (4716537e)	00015810		PxHlpa64.sys
000	fffff880`059be000	fffff880`059e9000	Fri Sep 26 07:11:22 2008 (48dcdf7a)	00027c43		000.fcl
RTSTOR64	fffff880`03086000	fffff880`0309b000	Mon Feb 23 01:18:57 2009 (49a25bf1)	00014c15		RTSTOR64.SYS
OA009Ufd	fffff880`0251e000	fffff880`02545060	Fri Mar 06 00:33:57 2009 (49b0d1e5)	0003421d		OA009Ufd.sys
OA009Vid	fffff880`024d2000	fffff880`0251e000	Thu Mar 19 23:00:05 2009 (49c322d5)	00051a04		OA009Vid.sys
Apfiltr	fffff880`0461e000	fffff880`0465c000	Thu Apr 02 11:39:40 2009 (49d4f85c)	0003c905		Apfiltr.sys
stwrt64	fffff880`03163000	fffff880`031de000	Mon Jun 29 11:52:05 2009 (4a48ff45)	00078643		stwrt64.sys
bcmwl664	fffff880`046e6000	fffff880`0498e000	Tue Jul 07 18:45:04 2009 (4a53ec10)	002a9bad		bcmwl664.sys

PxHlpa64.sys
000.fcl
RTSTOR64.SYS
OA009Ufd.sys
OA009Vid.sys
Apfiltr.sys
stwrt64.sys
bcmwl664.sys

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\jim12\022512-22807-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02ea9670
Debug session time: Sat Feb 25 13:22:09.706 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:49.485
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff88000000000, fffff880061d8150, 0}

Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+60 )

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

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

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

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+13
fffff880`00000000 ff              ???

CONTEXT:  fffff880061d8150 -- (.cxr 0xfffff880061d8150)
rax=000000000000000a rbx=fffffa8007415620 rcx=fffffa8006745b20
rdx=fffffa8007415620 rsi=fffffa8007d8d501 rdi=fffff88000000000
rip=fffff88000000000 rsp=fffff880061d8b38 rbp=fffff880061d8c60
 r8=fffff8a002e26000  r9=0000000000000000 r10=fffffa800244f4b0
r11=0000000000100080 r12=0000000007b9f500 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
fffff880`00000000 ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c8d6f0 to fffff88000000000

STACK_TEXT:  
fffff880`061d8b38 fffff800`02c8d6f0 : fffffa80`0244f4b0 fffffa80`07415620 fffff880`061d8c60 fffff880`061d8bf0 : 0xfffff880`00000000
fffff880`061d8b40 fffff800`030f5ac6 : fffff880`061d8b01 fffffa80`07415640 fffffa80`07d8d560 fffff880`061d8bf8 : nt!IoCancelIrp+0x60
fffff880`061d8b80 fffff800`02cdfed3 : fffffa80`07605060 000007fe`faa136c0 fffffa80`07d8d560 00000000`000003e4 : nt!NtCancelIoFile+0xd6
fffff880`061d8be0 00000000`76e618ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`07b9f4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e618ea


FOLLOWUP_IP: 
nt!IoCancelIrp+60
fffff800`02c8d6f0 450f20c3        mov     r11,cr8

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!IoCancelIrp+60

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff880061d8150 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!IoCancelIrp+60

BUCKET_ID:  X64_0x3B_nt!IoCancelIrp+60

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

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
Thanks to Dave76 for help understanding possible causes.

All of your most recent crashes were the same. Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts
Alternatively:
1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

Also, please fill out your system specs following the guide in System Info - See Your System Specs