Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Windows 7 - ntoskrnl.exe+7cc40

23 Feb 2012   #31
garthrs

Windows Home Premium 64bit
 
 

Still getting the same errors...

Followed your instructions, only one file and it was in the ATI Technologies folder.

I tried scanning hard drives again, creating a new user profile (Read that on backspacetab.com), memory tested good through 8 passes of Memtest86+ last night...

I have an ibuypower oem disk and i can't extract the \i386\ntoskrnl.ex_ file... so Basically i have to hope it isn't the file that is corrupt.

Attached are the dumps.

I really appreciate your patience with me and my issue.


My System SpecsSystem Spec
.
23 Feb 2012   #32
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\022312-20716-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 Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030ac670 Debug session time: Thu Feb 23 16:48:16.458 2012 (UTC - 7:00) System Uptime: 0 days 0:20:34.019 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, 0, fffff8800783c898, fffff8800783c0f0} Probably caused by : ntkrnlmp.exe ( nt!PfTCreateTraceDump+2e3 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: fffff8800783c898, Exception Record Address Arg4: fffff8800783c0f0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: +16 00000000`00000000 ?? ??? EXCEPTION_RECORD: fffff8800783c898 -- (.exr 0xfffff8800783c898) ExceptionAddress: 0000000000000000 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 0000000000000000 Attempt to execute non-executable address 0000000000000000 CONTEXT: fffff8800783c0f0 -- (.cxr 0xfffff8800783c0f0) rax=fffff8a00d490ff8 rbx=fffff8a00232afd8 rcx=fffff8a00d490ff8 rdx=fffffffff4e99fe0 rsi=fffff8a00d490ff8 rdi=0000000000000000 rip=0000000000000000 rsp=fffff8800783cad8 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=0000000000003cb4 r11=fffff8a00d490ff8 r12=fffff8a00d490020 r13=00000000000000fc r14=fffff8a00232a000 r15=00000000000000fc iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 00000000`00000000 ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 0000000000000000 WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003116100 0000000000000000 FOLLOWUP_IP: nt!PfTCreateTraceDump+2e3 fffff800`03300f63 41016c2404 add dword ptr [r12+4],ebp FAILED_INSTRUCTION_ADDRESS: +2e3 00000000`00000000 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff80003300f63 to 0000000000000000 STACK_TEXT: fffff880`0783cad8 fffff800`03300f63 : fffff8a0`0232afc8 00000000`00000001 fffff8a0`0d490fe8 fffff800`00000000 : 0x0 fffff880`0783cae0 fffff800`033500b0 : fffff880`0783cc10 fffff8a0`0232a018 fffff8a0`0d490000 fffff8a0`0d478000 : nt!PfTCreateTraceDump+0x2e3 fffff880`0783cbe0 fffff800`03355ca3 : fffffa80`07b9b001 00000000`00000080 fffffa80`069ab9e0 fffff800`0306bda8 : nt!PfTGenerateTrace+0x10 fffff880`0783cc10 fffff800`0317efee : ffffffff`ff676980 fffffa80`07b9b060 fffffa80`0875b060 fffff800`02edb757 : nt!PfTLoggingWorker+0x113 fffff880`0783cd40 fffff800`02ed55e6 : fffff800`03059e80 fffffa80`07b9b060 fffff800`03067cc0 fffff880`01265cb0 : nt!PspSystemThreadStartup+0x5a fffff880`0783cd80 00000000`00000000 : fffff880`0783d000 fffff880`07837000 fffff880`0783c790 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!PfTCreateTraceDump+2e3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff8800783c0f0 ; kb FAILURE_BUCKET_ID: X64_0x7E_NULL_IP_nt!PfTCreateTraceDump+2e3 BUCKET_ID: X64_0x7E_NULL_IP_nt!PfTCreateTraceDump+2e3 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\garthrs\022312-21496-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 Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`030a6670 Debug session time: Thu Feb 23 14:47:01.614 2012 (UTC - 7:00) System Uptime: 0 days 0:27:23.785 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff80000000000, 0, fffff800032faffc, 0} Could not read faulting driver name Probably caused by : ntkrnlmp.exe ( nt!PfTCreateTraceDump+37c ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff80000000000, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff800032faffc, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003110100 fffff80000000000 FAULTING_IP: nt!PfTCreateTraceDump+37c fffff800`032faffc 4c3b36 cmp r14,qword ptr [rsi] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88006c3a940 -- (.trap 0xfffff88006c3a940) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8a00fbdd598 rbx=0000000000000000 rcx=000000000000ffff rdx=0000000000000083 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800032faffc rsp=fffff88006c3aad8 rbp=0000000000000001 r8=0000000000000010 r9=fffff8a0024e7000 r10=0000000000005083 r11=fffff88006c3ab00 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!PfTCreateTraceDump+0x37c: fffff800`032faffc 4c3b36 cmp r14,qword ptr [rsi] ds:0002:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002e899fc to fffff80002eddc40 STACK_TEXT: fffff880`06c3a7d8 fffff800`02e899fc : 00000000`00000050 fffff800`00000000 00000000`00000000 fffff880`06c3a940 : nt!KeBugCheckEx fffff880`06c3a7e0 fffff800`02edbd6e : 00000000`00000000 fffff800`00000000 ffffffff`f290ff00 fffff8a0`024c15c8 : nt! ?? ::FNODOBFM::`string'+0x4611f fffff880`06c3a940 fffff800`032faffc : fffff800`032fafdd fffff8a0`024c15b8 00000000`00000001 fffff8a0`0fbdd578 : nt!KiPageFault+0x16e fffff880`06c3aad8 fffffa80`08743b01 : fffff800`0334a0b0 fffff880`06c3ac10 fffff8a0`024ba018 fffff8a0`0fbbe000 : nt!PfTCreateTraceDump+0x37c fffff880`06c3abd8 fffff800`0334a0b0 : fffff880`06c3ac10 fffff8a0`024ba018 fffff8a0`0fbbe000 fffff8a0`0fb88000 : 0xfffffa80`08743b01 fffff880`06c3abe0 fffff800`0334fca3 : fffffa80`08743b01 00000000`00000080 fffffa80`069ab9e0 fffff800`03065da8 : nt!PfTGenerateTrace+0x10 fffff880`06c3ac10 fffff800`03178fee : ffffffff`ff676980 fffffa80`08743b60 fffffa80`08ce75c0 fffff800`02ed5757 : nt!PfTLoggingWorker+0x113 fffff880`06c3ad40 fffff800`02ecf5e6 : fffff800`03053e80 fffffa80`08743b60 fffff800`03061cc0 fffff880`01026cb0 : nt!PspSystemThreadStartup+0x5a fffff880`06c3ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!PfTCreateTraceDump+37c fffff800`032faffc 4c3b36 cmp r14,qword ptr [rsi] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!PfTCreateTraceDump+37c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x50_nt!PfTCreateTraceDump+37c BUCKET_ID: X64_0x50_nt!PfTCreateTraceDump+37c Followup: MachineOwner ---------
  1. Possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
  2. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

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 step to see if stability increases (the hardware tests you can run concurrently as they will not increase stability). 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.
My System SpecsSystem Spec
24 Feb 2012   #33
garthrs

Windows Home Premium 64bit
 
 

1. I am not overclocked, all equipment is factory standard.

OS Drive Chkdsk:
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)...
156928 file records processed. File verification completed.
471 large file records processed. 0 bad file records processed. 0 EA records processed. 92 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
211238 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
156928 file SDs/SIDs processed. Cleaning up 133 unused index entries from index $SII of file 0x9.
Cleaning up 133 unused index entries from index $SDH of file 0x9.
Cleaning up 133 unused security descriptors.
Security descriptor verification completed.
27156 data files processed. CHKDSK is verifying Usn Journal...
34509968 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
156912 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
97231125 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
488282111 KB total disk space.
99012832 KB in 121664 files.
71756 KB in 27157 indexes.
0 KB in bad sectors.
273023 KB in use by the system.
65536 KB occupied by the log file.
388924500 KB available on disk.
4096 bytes in each allocation unit.
122070527 total allocation units on disk.
97231125 allocation units available on disk.
Internal Info:
00 65 02 00 60 45 02 00 68 01 04 00 00 00 00 00 .e..`E..h.......
0e 02 00 00 5c 00 00 00 00 00 00 00 00 00 00 00 ....\...........
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.

Secondary Drive:
Chkdsk was executed in read/write mode.
Checking file system on D:
Volume label is SATA160.
CHKDSK is verifying files (stage 1 of 5)...
17408 file records processed. File verification completed.
0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
18748 index entries processed. Index verification completed.
 
CHKDSK is verifying security descriptors (stage 3 of 5)...
17408 file SDs/SIDs processed. Cleaning up 28 unused index entries from index $SII of file 0x9.
Cleaning up 28 unused index entries from index $SDH of file 0x9.
Cleaning up 28 unused security descriptors.
Security descriptor verification completed.
671 data files processed. CHKDSK is verifying Usn Journal...
1284504 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
17392 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
11502423 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
156280288 KB total disk space.
110178468 KB in 6672 files.
2640 KB in 672 indexes.
89488 KB in use by the system.
65536 KB occupied by the log file.
46009692 KB available on disk.
4096 bytes in each allocation unit.
39070072 total allocation units on disk.
11502423 allocation units available on disk.

3. SFC /SCANNOW returned no errors three times in a row.

4. Furmarking now.

SMART Data from WD Diagnosis tool Passed both drives.

Furmark and Video Memory passed with zero erros.

Most recent crash file attached.
My System SpecsSystem Spec
.

25 Feb 2012   #34
garthrs

Windows Home Premium 64bit
 
 

Just re-installed windows... Repair install. Maybe the ntoskrnl.exe is corrupt. Here's to hoping.
My System SpecsSystem Spec
25 Feb 2012   #35
writhziden

Windows 7 Home Premium 64 Bit
 
 

It is not likely ntoskrnl.exe was corrupt. That process is usually blamed when Windows is unable to find the true culprit.

A repair install still may resolve the problem if there were other corrupted files/registry errors/driver problems. It is a good step to take.
My System SpecsSystem Spec
25 Feb 2012   #36
garthrs

Windows Home Premium 64bit
 
 

Can you think of any more checks i can do? The system is rock solid during furmark and video ram testing.
My System SpecsSystem Spec
25 Feb 2012   #37
writhziden

Windows 7 Home Premium 64 Bit
 
 

Only thing left to try is backup all important data and Clean Install Windows 7.

I remember you did this before, but you have not done so with the new graphics card. Also, what causes the crashes? Is there anything that is known to cause them, or are they random?

The only hardware you have not yet replaced are hard disk drives and PSU. The drives look good from the reports given, so I would consider testing another PSU in your system. Try to get one that has as good or a better rating than your current unit.
My System SpecsSystem Spec
25 Feb 2012   #38
garthrs

Windows Home Premium 64bit
 
 

I can almost guarentee a crash when I render a video.

I use Sony Vegas HD Movie Studio Platinum V. 11. That will almost always give me a blue screen.

I Play Dungeon Defenders on Steam. That will also almost always give me a blue screen.

Just over half the time, I get a Blue screen on Minecraft.

I get these crashes in game either when I am using FRAPS to record it or not.

Unless I am rendering a video, standard Microsoft Office use does not crash my PC. I can view videos on you tube, or from hard drive without concern.

I run a small you tube channel, so not being able to put out more than a few videos a week kind of sucks for me.

Usually I can get a video rendered if I just keep trying, last one took 30+ attempts.
My System SpecsSystem Spec
25 Feb 2012   #39
writhziden

Windows 7 Home Premium 64 Bit
 
 

That does sound rather frustrating. I still recommend trying the clean install. It is possible the new card is having issues due to the card having been on the system before. I'd be somewhat surprised this is still the case after a repair install, but it still may be possible.

The other possibility is the PSU may not be able to handle the intensive processes you use the video card for. I do not know if that would be due to a faulty PSU, or 750 W not being enough (although 750 W I would think would be plenty).

As I said, try the clean install first, then if problems continue, consider testing with a borrowed or new PSU.
My System SpecsSystem Spec
25 Feb 2012   #40
garthrs

Windows Home Premium 64bit
 
 

Here is a weird factoid...

I seem to remember having about 70-ish Windows updates on the last install (SP 1)

This one is at 102 for windows alone... Why the huge gap? I thought standard sp1 was about 70 updates.
My System SpecsSystem Spec
Reply

 BSOD Windows 7 - ntoskrnl.exe+7cc40




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Windows 7 - ntoskrnl.exe+7cc40
hi, here is the issue: about two weeks ago I took my laptop to the service because its disk drive not seeing any cd or dvd than they changed it with a new one after that they said we updated the bios after 2 or 3 days later I'm on the Internet I got blue screen error driver power state failure,...
BSOD Help and Support
BSOD ntoskrnl.exe 7cc40
Im getting massive BSOD's every day. I can't even use this computer most hours and it'll probably BSOD in a few minuetes. Could someone look at the txt file I included and point me in the right direction? Or if I need more info please tell me!!! Because Im going crazy with this BSOD.
BSOD Help and Support
BSOD ntoskrnl.exe+7cc40
Have received this BSOD several times while the machine has been in Sleep Mode. Normal operation is to turn the monitor off and put the computer into that mode during the night. The BSOD is the normal DRIVER_POWER_STATE_FAILURE ntoskrnl.exe caused by address ntoskrnl.exe+7cc40. Desktop...
BSOD Help and Support
Random BSOD - ntoskrnl.exe (nt+7cc40) Please Help
Hello, I am getting BSOD every couple of days with no apparent reason sometime with doing virus scans, running windows movie maker and sometime while idle. Not sure what's going on please help - I have attached .dmp for assessment. ...
BSOD Help and Support
ntoskrnl.exe+7cc40 BSOD's
Hi, I have a new rig i built my self and it runs perfectly except the occasional BSOD and i cant for the life of me work out why... 091711-6006-01.dmp 17/09/2011 21:33:23 BAD_POOL_HEADER 0x00000019 00000000`00000003 fffff8a0`1205a820 ff8af8a0`1205a820 fffff8a0`1205a820 ...
BSOD Help and Support
BSOD ntoskrnl.exe+26ee0 ntoskrnl.exe+7cc40
Hi, I've been having this BSOD appear very randomly. IRQL_NOT_LESS_OR_EQUAL 0x0000000a (all reports in .rar file) Sometimes within 1 hour, other times as long as 24hrs+. I've got my BIOS/Drivers up to date for my CPU, Graphics Card, and Motherboard. I've rigorously tested my memory and have...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:37.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App