Solved Constant BSOD from 3d gaming, ntoskrnl+7cc40

[writhziden]

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\Windows_NT6_BSOD_jcgriff2\042512-17409-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02c68000 PsLoadedModuleList = 0xfffff800`02eac650
Debug session time: Wed Apr 25 20:56:46.247 2012 (UTC - 6:00)
System Uptime: 0 days 1:22:32.730
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {800000, 2, 0, fffff80002cef7a2}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )

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: 0000000000800000, memory referenced
Arg2: 0000000000000002, 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: fffff80002cef7a2, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f16100
 0000000000800000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiProcessExpiredTimerList+72
fffff800`02cef7a2 803818          cmp     byte ptr [rax],18h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c450 -- (.trap 0xfffff80000b9c450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000800000 rbx=0000000000000000 rcx=fffffa8004af7b80
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cef7a2 rsp=fffff80000b9c5e0 rbp=000000000004d828
 r8=fffff80002e80f01  r9=000000000000002a r10=fffff80002e59e80
r11=fffff80002e80fa0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KiProcessExpiredTimerList+0x72:
fffff800`02cef7a2 803818          cmp     byte ptr [rax],18h ds:1288:00000000`00800000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ce4229 to fffff80002ce4c80

STACK_TEXT:  
fffff800`00b9c308 fffff800`02ce4229 : 00000000`0000000a 00000000`00800000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c310 fffff800`02ce2ea0 : fffffa80`00000001 fffff880`00000064 fffffa80`04a6fb50 fffffa80`04af7ba0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c450 fffff800`02cef7a2 : fffffa80`04af7ba0 fffffa80`04af7be8 fffffa80`04af7be8 00000000`00000102 : nt!KiPageFault+0x260
fffff800`00b9c5e0 fffff800`02cef6de : 0000000b`880ebb75 fffff800`00b9cc58 00000000`0004d828 fffff800`02e5c788 : nt!KiProcessExpiredTimerList+0x72
fffff800`00b9cc30 fffff800`02cef4c7 : 00000002`9585d9c2 00000002`0004d828 00000002`9585d9d0 00000000`00000028 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cdc98a : fffff800`02e59e80 fffff800`02e67cc0 00000000`00000000 fffff880`01ccda00 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiProcessExpiredTimerList+72
fffff800`02cef7a2 803818          cmp     byte ptr [rax],18h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiProcessExpiredTimerList+72

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+72

BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+72

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

The above crash indicates driver or hardware issues. I noted that another crash indicated possible data corruption.

I also see that the crashes were gone for a couple weeks. Was this due to inactivity with the system, or have you done something different in the past two days that may have changed the system, i.e. added hardware or software that you were not previously using?

• Run Disk Check with Automatically fix file system errors checked. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

 

[Vimicry]

I haven't done anything different for the past 2 weeks, nothing was changed.
chkdsk logs

Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
  276736 file records processed.                                          File verification completed.
  935 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
  367848 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 3)...
  276736 file SDs/SIDs processed.                                         Cleaning up 8 unused index entries from index $SII of file 0x9.
Cleaning up 8 unused index entries from index $SDH of file 0x9.
Cleaning up 8 unused security descriptors.
Security descriptor verification completed.
  45557 data files processed.                                            CHKDSK is verifying Usn Journal...
  34031480 USN bytes processed.                                             Usn Journal verification completed.
Windows has checked the file system and found no problems.

 296233983 KB total disk space.
 141219304 KB in 214868 files.
    113944 KB in 45558 indexes.
         0 KB in bad sectors.
    389047 KB in use by the system.
     65536 KB occupied by the log file.
 154511688 KB available on disk.

      4096 bytes in each allocation unit.
  74058495 total allocation units on disk.
  38627922 allocation units available on disk.

Internal Info:
00 39 04 00 56 f9 03 00 6e 10 07 00 00 00 00 00  .9..V...n.......
65 06 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  e...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  261376 file records processed.                                          File verification completed.
  169 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  339238 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  261376 file SDs/SIDs processed.                                         Cleaning up 200 unused index entries from index $SII of file 0x9.
Cleaning up 200 unused index entries from index $SDH of file 0x9.
Cleaning up 200 unused security descriptors.
Security descriptor verification completed.
  38932 data files processed.                                            CHKDSK is verifying Usn Journal...
  34566704 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  261360 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  52470949 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 296233983 KB total disk space.
  85856672 KB in 208169 files.
    122272 KB in 38933 indexes.
         0 KB in bad sectors.
    371239 KB in use by the system.
     65536 KB occupied by the log file.
 209883800 KB available on disk.

      4096 bytes in each allocation unit.
  74058495 total allocation units on disk.
  52470950 allocation units available on disk.

Internal Info:
00 fd 03 00 4a c5 03 00 25 e3 06 00 00 00 00 00  ....J...%.......
70 04 00 00 2c 00 00 00 00 00 00 00 00 00 00 00  p...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[Wrench97]

What are you seeing for temps now on the CPU, GPU, and Motherboard(system)?

 

[Vimicry]

I get temps of 50-60 degrees on CPU, 43-50 on motherboard, I can't get the temperatures for my GPU. I don't have the GPU sensors for temp. Do you want me to do a furmark test again?

 

[writhziden]

Run Furmark again.

Also, scan for malware and viruses.

• Run a full scan with Microsoft Security Essentials.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan.

 

[Vimicry]

Crashed twice trying to post back.
Malwarebytes and MSE didn't pick up anything.
I had temperatures of 69-70 in the first 8 mins. 71-73 degrees in 20 mins. Didn't crash.
Computer crashed 2 mins later when I attempted to reply back, hard to describe, it was like a white checkerboard.
After rebooting, had a BSOD trying to post back.

 

[writhziden]

Those sound like screen artifacts. Can you provide the crash report?

 

[Vimicry]

Attached are my dumps. 2 new blue screens too.
edit:
after posting this, another blue screen appeared, I was using google chrome at the time, the page repetitively crashed, the crashing page then turned purple and my computer proceeded to blue screen.

 

[Wrench97]

Naming the ATI drivers.

Did the video drivers come from ATI/AMD or the HP D/L page for your laptop?

There are also some strange drivers for a Win7 system
iirsp.sys Tue Dec 13 16:47:54 2005> Intel Raid storage driver
nfrd960.sys Tue Jun 06 17:11:48 2006 Intel Server Raid Storage driver
vsmraid.sys Fri Jan 30 20:18:57 2009>> Via Raid storage driver
nfrd960.sys Tue Jun 06 17:11:48 2006> IBM Server Raid storage driver
SiSRaid2.sys Wed Sep 24 14:28:20 2008
sisraid4.sys Wed Oct 01 17:56:04 2008 > Both Sis Raid storage drivers.
nvraid.sys Fri Mar 19 16:59:20 2010?> Nvidia Raid storage driver.

Even if you had a Raid setup only the driver for the raid controller used should be on the system.

Where are you getting these drivers from?

1: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios .logclose;q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000009289, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880044d7f7a, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebd100
 0000000000009289 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiProcessDpcVSyncCookie+122
fffff880`044d7f7a 8b4550          mov     eax,dword ptr [rbp+50h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800391b640 -- (.trap 0xfffff8800391b640)
.trap 0xfffff8800391b640
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000e9f rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044d7f7a rsp=fffff8800391b7d0 rbp=0000000000009239
 r8=0000000000009218  r9=fffffa8004726040 r10=fffffa8003419bd0
r11=fffff8800391b888 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
dxgmms1!VidSchiProcessDpcVSyncCookie+0x122:
fffff880`044d7f7a 8b4550          mov     eax,dword ptr [rbp+50h] ss:0018:00000000`00009289=????????
.trap
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8b229 to fffff80002c8bc80

 

[Vimicry]

I'm getting the drivers from ATI/AMD. The catalyst_mobility_64-bit_util.exe.
I'll uninstall the ATI/AMD drivers and reinstall the HP ones. I bet it'll fix some problems.

 

[Wrench97]

It just may, some mobility cards are flaky that way.

 

[writhziden]

Typically, with laptops, it is best to get the graphics card drivers from the laptop manufacturer. The graphics card drivers are more finicky than most because those provided by the laptop manufacturer were designed to provide the best power management for the laptop. Other drivers can cause issues because the laptop is trying to use the power management scheme designed by the vendor developers and the display card drivers taken from the display card manufacturer are not designed for that scheme and interfere with that scheme.

 

[Vimicry]

Ah, I understand that. Unfortunetly, after I reinstalled the drivers, I'm still receiving some problems. I'm going to try and reinstall the drivers again, this time with driver sweeper, see if it might help. Attached is a picture when I crashed.

 

[writhziden]

ooo that doesn't look pretty... If you use Driver Sweeper, make sure to create a system restore point first. I have seen Driver Sweeper clean too much on occasion and leave Windows unbootable. It usually does not cause issues, but it is best to exercise caution before using it.

 

[Vimicry]

So reinstalling the video card drivers after using driver sweeper didn't seem to help at all.
I really don't see what's going wrong and I'm tempted to reformat again. Crash reports added just incase. Do you guys reccomend that I reformat?

 

[writhziden]

Do you have recovery discs made for the system? If not, see http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164

Can you please fill in your system specs to make it a little easier to determine what system you have? http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html can help in that regard. Fill in your specs in your profile and not in a post in this thread.

 

[Wrench97]

I'm leaning more towards a failed GPU then a driver issue.

 

[writhziden]

Wrench97, I agree that it appears more likely that it is a GPU failure based on the image in post #33... Ah, a second edit due to reading the first post of this thread again. Seems I forgot that this does have a dedicated graphics card. Unfortunately, dedicated graphics on a notebook PC still requires sending it in to HP for repairs...

Vimicry, it is up to you whether you want to send in your notebook for repairs/replace the notebook or go through the clean re-install or factory restore.


Sorry for the original misinformation, and then the second set of misinformation needing a second edit. This is why it helps to fill in the system specs. I forgot this was a laptop... I also forgot you have dedicated graphics...

Please fill in your system specs as I asked in my previous post to avoid these complications as you get help in the future.

 

[Wrench97]

I also have at times overlooked the spec of a laptop that can at times lead to some very strange replies when working on graphics problems

 

[Vimicry]

Yeah, I kind of expected it to be a GPU failure. Sorry for responding so late, but I gave up on this laptop after I restored everything to factory settings. I wasn't able to even boot up at the time, I kept getting the same blue screens when I got past the Windows booting screen.

During safe mode, I don't seem to crash. I'll probably just stick to safe mode and not do anything major.

Thanks for sticking with me for so long, I really appreciated the time you guys put in on figuring out what the problem was.