BSOD Randomly/Mainly during Video playback

Anyone?

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\Boudi\Windows_NT6_BSOD_jcgriff2\021112-27066-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e55670
Debug session time: Sat Feb 11 05:42:44.869 2012 (GMT-7)
System Uptime: 0 days 2:35:50.790
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff7ff86ff838d, 2, 1, fffff80002d402de}

Probably caused by : ntkrnlmp.exe ( nt!PpmPerfCalculateCoreParkingMask+2de )

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: fffff7ff86ff838d, 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: fffff80002d402de, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebf100
 fffff7ff86ff838d 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!PpmPerfCalculateCoreParkingMask+2de
fffff800`02d402de 418b8c8300832700 mov     ecx,dword ptr [r11+rax*4+278300h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80003ffa110 -- (.trap 0xfffff80003ffa110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa80077a8468 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d402de rsp=fffff80003ffa2a0 rbp=0000000000000023
 r8=0000000000002134  r9=0000000000000064 r10=0000000000000000
r11=fffff80002c10000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!PpmPerfCalculateCoreParkingMask+0x2de:
fffff800`02d402de 418b8c8300832700 mov     ecx,dword ptr [r11+rax*4+278300h] ds:9180:fffff800`02e88304=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8c1e9 to fffff80002c8cc40

STACK_TEXT:  
fffff800`03ff9fc8 fffff800`02c8c1e9 : 00000000`0000000a fffff7ff`86ff838d 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`03ff9fd0 fffff800`02c8ae60 : fffffa80`090ad000 fffff880`02d60691 00000000`0032d4c5 fffff800`03ff0001 : nt!KiBugCheckDispatch+0x69
fffff800`03ffa110 fffff800`02d402de : fffffa80`090ad000 fffff880`02d60691 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff800`03ffa2a0 fffff800`02d3e7ec : fffff800`03ffa4c0 00000000`00000000 00000000`00000001 fffff800`03ffa4c0 : nt!PpmPerfCalculateCoreParkingMask+0x2de
fffff800`03ffa3d0 fffff800`02d7de70 : 00000000`0032d4c5 fffff800`03ffa4c0 00000000`00000001 fffff800`02c955fa : nt!PpmCheckRun+0x8c
fffff800`03ffa400 fffff800`02c985fc : fffffa80`09c100b0 fffff880`00000000 00000001`406f1288 00000000`00000055 : nt!PpmCheckStart+0x40
fffff800`03ffa430 fffff800`02c98496 : fffff800`02e29f50 00000000`0009256d 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`03ffa4a0 fffff800`02c9837e : 00000015`c581755e fffff800`03ffab18 00000000`0009256d fffff800`02e06028 : nt!KiProcessExpiredTimerList+0xc6
fffff800`03ffaaf0 fffff800`02c98167 : 00000007`40bfd3c1 00000007`0009256d 00000007`40bfd349 00000000`0000006d : nt!KiTimerExpiration+0x1be
fffff800`03ffab90 fffff800`02c8496a : fffff800`02e02e80 fffff800`02e10cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`03ffac40 00000000`00000000 : fffff800`03ffb000 fffff800`03ff5000 fffff800`03ffac00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PpmPerfCalculateCoreParkingMask+2de
fffff800`02d402de 418b8c8300832700 mov     ecx,dword ptr [r11+rax*4+278300h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PpmPerfCalculateCoreParkingMask+2de

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!PpmPerfCalculateCoreParkingMask+2de

BUCKET_ID:  X64_0xA_nt!PpmPerfCalculateCoreParkingMask+2de

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

Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each 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 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
  
  
  
• Check for a corrupted Windows installation (this can keep reoccurring if the installation media has corrupted files). 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.
  
  
  
  
• I noticed you do not have antivirus software installed. While this is a good method for stability troubleshooting, it leaves your system vulnerable if you use the internet. See the Good and Free system security combination. for better security steps and scanning tools that do not cause stability problems.
  
  
  
  
• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode. Start logging the temperature through sensor-only mode when the computer first starts, and let it run during stress or until a crash occurs.
  
  Save the CSV file in a place you will remember, and then compress the CSV file to a zip file and upload to here for us to analyze by following the steps in Screenshots and Files - Upload and Post in Seven Forums.
  
  Also, please upload the .html file including your system specs using HWINFO with sensor only mode unchecked. Click Save Report and save the HTML file in a location you will remember by clicking Browse. Compress (zip) the html file and upload following Screenshots and Files - Upload and Post in Seven Forums so we may check for compatibility of hardware.
  
  
  
• 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.

"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. "

I'm not sure how I should do this test, how long do I run each test for? And is there a log I should post after testing?

....Also while running the prime95 stress test, i was monitoring my cpu tempreture with HWinfo and the tempretures immediatly shot up to around 70degrees celcius, is this safe? I only have a stock heatsink and a couple of case fans to keep it cool. Would this be enough to run it at those kinds of tempretures safely?

Boudi said:

thank you for the reply, here are the results of the Disk Check. I'll keep posting as I go down the list.


Also the results of the 3 passes of SFC/SCANNow test came up clear with "no integrity violations found".

Windows has made corrections to the file system. You should run the disk check again until the message Windows has checked the file system and found no problems appears.

Boudi said:

And now for the HWinfo log. My system crashed (BSOD) while monitoring the tempreture stress test with this program. I was transfering files and had a hi def movie playing and serching the web. I have also included the log for that.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\Boudi\Windows_NT6_BSOD_jcgriff2\021412-17550-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`0329d670
Debug session time: Tue Feb 14 00:18:36.293 2012 (GMT-7)
System Uptime: 0 days 0:20:46.230
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6243952f03c0dd80
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c108 -- (.exr 0xfffff80000b9c108)
ExceptionAddress: fffff800031c52e7 (nt!PpmCheckRecordAllUtility+0x00000000000000f7)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff80000b9c1b0 -- (.trap 0xfffff80000b9c1b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000006c rbx=0000000000000000 rcx=0048f330001bf10c
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031c52e7 rsp=fffff80000b9c340 rbp=00000000000000fe
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=fffff80000b9c368 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!PpmCheckRecordAllUtility+0xf7:
fffff800`031c52e7 d5              ???
Resetting default scope

MISALIGNED_IP: 
nt!PpmCheckRecordAllUtility+f7
fffff800`031c52e7 d5              ???

LAST_CONTROL_TRANSFER:  from fffff800030cc5fe to fffff800030d4c10

STACK_TEXT:  
fffff800`00b9b1e8 fffff800`030cc5fe : fffffa80`0711f3b0 00000000`00000000 fffff800`00b9b960 fffff800`03100830 : nt!KeBugCheck
fffff800`00b9b1f0 fffff800`031004fd : fffff800`032de71c fffff800`0321bc30 fffff800`03058000 fffff800`00b9c108 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b220 fffff800`030ff2d5 : fffff800`0321f0fc fffff800`00b9b298 fffff800`00b9c108 fffff800`03058000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b250 fffff800`03110361 : fffff800`00b9c108 fffff800`00b9b960 fffff800`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
fffff800`00b9b930 fffff800`030d42c2 : fffff800`00b9c108 00000000`00000000 fffff800`00b9c1b0 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9bfd0 fffff800`030d241f : fffff800`00b9c1b0 fffffa80`0779f602 fffffa80`0700bd00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c1b0 fffff800`031c52e7 : fffffa80`00000000 fffffa80`08477508 fffff800`00b9c400 fffff800`03271f01 : nt!KiInvalidOpcodeFault+0x11f
fffff800`00b9c340 fffff800`031867ec : 3ba60000`00000000 3ba70000`3c050000 fffff800`0324ae80 fffff800`00b9c4c0 : nt!PpmCheckRecordAllUtility+0xf7
fffff800`00b9c3d0 fffff800`031c5e70 : 00000000`0032d49e fffff800`00b9c4c0 00000000`00000202 fffff800`030dafda : nt!PpmCheckRun+0x8c
fffff800`00b9c400 fffff800`030e05fc : fffffa80`0958dc48 fffffa80`00000000 00000006`400f1200 00000000`00000054 : nt!PpmCheckStart+0x40
fffff800`00b9c430 fffff800`030e0496 : fffffa80`077f85e8 fffffa80`077f85e8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`030e037e : 00000002`e6cfa315 fffff800`00b9cb18 00000000`0001380e fffff800`0324d448 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`030e0167 : 00000000`f78eeac3 00000000`0001380e 00000000`f78eeaa2 00000000`0000000e : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`030cc96a : fffff800`0324ae80 fffff800`03258cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`030cc5fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

This crash is usually caused by hardware or a driver. Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.

Boudi said:

"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. "

I'm not sure how I should do this test, how long do I run each test for? And is there a log I should post after testing?

Run each test to completion or until the GPU temperatures reach 90 C or CPU temperatures reach 76 C. The test programs will let you know if the graphics card passes.

Boudi said:

....Also while running the prime95 stress test, i was monitoring my cpu tempreture with HWinfo and the tempretures immediatly shot up to around 70degrees celcius, is this safe? I only have a stock heatsink and a couple of case fans to keep it cool. Would this be enough to run it at those kinds of tempretures safely?

If the CPU temperature gets to 76 C, stop the test. Your CPU is rated to get to about 98 C maximum, but we usually are more conservative and say T_Case + 5 C (which is about 78 C for that CPU; see Intel® Core)). If you are getting above 78 C, then you do not have adequate cooling and should think about replacing the heatsink/fan system or asking the manufacturer of the system how to run the system cooler.

Ran the windows memory diagnostics tool over night 2 passes extended with the following results:

"The Windows Memory Diagnostic tested the computer's memory and detected no errors"

I also ran MEMTEST86+ over 7 passes with positive results and no errors found.


And finally ran the disk check again and got a Windows has checked the file system and found no problems message.

... One qusetion about the FURMAR test, I cant seem to find the VGA test you mentioned, the Graphic card and GPU test or the OpenGL bench mark and GPU tempreture test are they all bundled in the same program or5 are they all seperate downloads?

Thanks Writhziden.

I'm really starting to think I have installed a wire or component or something in the wrong place when I built this rig, this was my first build from the ground up, I can take a few pics to show where everything has been installed etc if that would help. come to think about it, while I was putting it all together one of my hard disks (C drive) had a bit of a bump, nothing too major though.

could the version of windows itself be the problem here?

Had another two crashes over the last two days , One chrah occured while I was running the SFC /SCANNOW Command - System File Checker in dos and the other while playing a movie. I notice that the chances of getting a BSOD are somewhat increased if I am multitasking, namely tranferring files to an external HDD, palying a movie and have internet explorer open.

I'm just trying to narrow it down but going over what I have just read I think I've widened the error scale.

Never the less, I will run the rest of the prescibed tests tonight and post the result.