BSOD Windows 7 64 bit Phed.dll & Ntoskrnl.exe

[Gvolution]

Hi I really am frustrated with my pc. I keep getting BSOD and even bought new ram recently as well as a new hard disk. I know it's not my hardisk or my windows installation because I get the error on multiple installations. My mainboard is decent and current so I don't really know what to make of these blue screens. One thing that is always there is the ntoskrnl.exe file and the pshed.dll. I have pasted them below. Thank you for any help you can give. I have run all diagnostics on memory and scannow, chkdsk, dxdiag, memtest.

Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 1a
BCP1: 0000000000008886
BCP2: FFFFFA8003812460
BCP3: FFFFFA800380FD60
BCP4: 0000000000000702
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

081010-19219-01.dmp 8/10/2010 12:46:39 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00008886 fffffa80`03812460 fffffa80`0380fd60 00000000`00000702 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\081010-19219-01.dmp 2 15 7600

081010-29250-01.dmp 8/10/2010 12:01:31 AM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 fffff880`14363b69 nvlddmkm.sys nvlddmkm.sys+468b69 x64 C:\Windows\Minidump\081010-29250-01.dmp 2 15 7600

080910-20295-01.dmp 8/9/2010 6:39:45 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 dxgmms1.sys dxgmms1.sys+e691 x64 C:\Windows\Minidump\080910-20295-01.dmp 2 15 7600

080910-22386-01.dmp 8/9/2010 11:21:44 AM BAD_POOL_HEADER 0x00000019 00000000`00000020 fffff900`c4218560 fffff900`c4218660 00000000`25100002 win32k.sys win32k.sys+861f1 x64 C:\Windows\Minidump\080910-22386-01.dmp 2 15 7600

080810-17784-01.dmp 8/8/2010 9:34:41 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`14bb54cd fffff880`04ff1658 fffff880`04ff0ec0 dxgmms1.sys dxgmms1.sys+263cb x64 C:\Windows\Minidump\080810-17784-01.dmp 2 15 7600

080810-24398-01.dmp 8/8/2010 2:11:39 PM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`02a72a01 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\080810-24398-01.dmp 2 15 7600

 

[Jonathan_King]

Welcome!

Please follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Thanks,
~JK

 

[Gvolution]

Windows 7 . . .
x64
Original installation
OEM but installed with disc myself.
Ram, motherboard, are new. Processor and graphics card are under a year old.


Hi I really am frustrated with my pc. I keep getting BSOD and even bought new ram recently as well as a new hard disk. I know it's not my hardisk or my windows installation because I get the error on multiple installations. My mainboard is decent and current so I don't really know what to make of these blue screens. One thing that is always there is the ntoskrnl.exe file and the pshed.dll. I have pasted them below. Thank you for any help you can give. I have run all diagnostics on memory and scannow, chkdsk, dxdiag, memtest.

Mainboard is Gigabyte GA-MA770T-UD3P

Memory is OCZ391800SR2G which just replaced some G.skill F3-12800CL9D-4GBNQ because I thought it was faulty memory.

Hard drive is WDC WD15EADS-00S2B0

 

[ttran]

Hi,

First of all, I suspect the graphic card:

BugCheck 7F, {8, 80050031, 6f8, fffff88014363b69}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+468b69 )
BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+2a19c1 )
BugCheck 1000007E, {ffffffffc0000005, fffff88014bb54cd, fffff88004ff1658, fffff88004ff0ec0}

Probably caused by : dxgmms1.sys ( dxgmms1!memmove+bd )

First step to try is to re-install the driver to see if the problem is resolved. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

In my experience, it looks like your graphic card has some problem, see if you can get another graphic card to try on your system (borrow perhaps).

Update this driver:

skfiltv  skfiltv.sys  Thu Aug 14 13:48:33 2008 (48A3D541)
probably Pilote USB audio (WDM); Creative wireless  headset; Hs-1200   Digital Wireless Headset -

See if you can update it, otherwise uninstall it so that we can eliminate if it is the cause.

Run system file checker please:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know if you need help

Tuan

 

[Gvolution]

Just bought an MSI R5850 so will test it and see and report back. Thank you

 

[Gvolution]

Ok just installed graphics card and still getting same error. I ran all the chkdsk and scannow and still ok. Always ntoskrnl and phed.dll in my files.

 

[Jonathan_King]

Looks almost as if the Catalyst Control Center is causing the problems. Not the first time I have seen this.

Try removing the Catalyst suite, and installing only the Catalyst drivers: Graphics Drivers & Software

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 10 15:48:00.918 2010 (UTC - 4:00)
System Uptime: 0 days 1:19:30.338
BugCheck 3B, {c0000005, fffff880044b7b56, fffff88007e6f0f0, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiGetDxgAdapterSafe+76 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  CCC.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Gvolution]

Ok the first ones that I posted didn't have ccc i just installed it yesterday..... I am not sure if that is the culprit because I had NVIDIA up until yesterday. I will try this though. Thanks again.

 

[Gvolution]

Looks almost as if the Catalyst Control Center is causing the problems. Not the first time I have seen this.

Try removing the Catalyst suite, and installing only the Catalyst drivers: Graphics Drivers & Software

Hello Jonathan,
I am very frustrated so far with this machine. I keep spending money on new ram and now a new video card. I don't know what is wrong with it but it crashes all the time with BSOD. I am uploading the new files. I have done everything you guys suggested and even scannow and never have errors. Every single error involves ntoskrnl.exe and this phed.dll.

 

[ttran]

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC /SCANNOW

2-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If your driver is missing, or there is a yellow triangle on it, you will need to update it.

5-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/Win7 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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users