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 64bit PSHED.dll + ntoskrnl


02 Jan 2011   #1
SirWilhelm

Windows 7 Enterprise 64bit
 
 
BSOD Windows 7 64bit PSHED.dll + ntoskrnl

Hi guys,

Starting to get really upset with my new PC. I'm not a complete noob on computers (don't consider me to be a expert either though) and I've been trying several things to resolve my BSOD's.

This PC is now 2 months old and I think I've had like at least 30 BSOD's during this time period.

So, what have I done:

- The most obvious and easy task...re-install Windows completely from scratch. Have done this now 3 times during this time period

- Updated all drivers for motherboard(intergrated sound and LAN),GPU and so on

- Unplugged everything and removed everything from the motherboard and re-inserted everything again...in case there where anything loose or not firmly set

- For some reason I suspected the harddrive at some point along the line so bought a brand new 60GB SSD (OCZ Vertex II) for OS disk only

- Not installed any antivirus software yet

- After re-installation #3 I made sure I only installed the display drivers and not the ATI CCC

The system still crashes, even though it's not that frequent as earlier.

Please help! i don't know what else I can do at the moment. I will make sure the reported problem about the HD Audio is resolved but to be honest I'm not at all convinced this is the accual cause right now.


My System SpecsSystem Spec
.

02 Jan 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by SirWilhelm View Post
Hi guys,

Starting to get really upset with my new PC. I'm not a complete noob on computers (don't consider me to be a expert either though) and I've been trying several things to resolve my BSOD's.

This PC is now 2 months old and I think I've had like at least 30 BSOD's during this time period.

So, what have I done:

- The most obvious and easy task...re-install Windows completely from scratch. Have done this now 3 times during this time period

- Updated all drivers for motherboard(intergrated sound and LAN),GPU and so on

- Unplugged everything and removed everything from the motherboard and re-inserted everything again...in case there where anything loose or not firmly set

- For some reason I suspected the harddrive at some point along the line so bought a brand new 60GB SSD (OCZ Vertex II) for OS disk only

- Not installed any antivirus software yet

- After re-installation #3 I made sure I only installed the display drivers and not the ATI CCC

The system still crashes, even though it's not that frequent as earlier.

Please help! i don't know what else I can do at the moment. I will make sure the reported problem about the HD Audio is resolved but to be honest I'm not at all convinced this is the accual cause right now.
Your approach has been organized and partially sucessful I suspect.

These two crashes were caused by your video driver. In some cases you may have to revert back to an older driver to resolve issues like this.

Please use the below to remove your current driver and re-install a fresh copy and we can go from there

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\010211-12058-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Sun Jan  2 11:48:05.835 2011 (GMT-5)
System Uptime: 0 days 2:42:58.897
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {22, 2000000, 0, 0}

Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+54d84 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000022, 
Arg2: 0000000002000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x19_22

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef90e0
 0000000002000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d16c80 to fffff80002cc1740

STACK_TEXT:  
fffff880`0ab7a2b8 fffff800`02d16c80 : 00000000`00000019 00000000`00000022 00000000`02000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ab7a2c0 fffff800`02df6518 : 00000000`00000000 fffff880`0ab7a410 fffff880`0ab7a380 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x72f8
fffff880`0ab7a350 fffff880`04856d84 : 00000000`00000000 00000000`00000000 fffffa80`07f8a040 fffff880`00000000 : nt!ExFreePoolWithTag+0x468
fffff880`0ab7a400 00000000`00000000 : 00000000`00000000 fffffa80`07f8a040 fffff880`00000000 fffff8a0`002a81a0 : atikmdag+0x54d84


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+54d84
fffff880`04856d84 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+54d84

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ea1

FAILURE_BUCKET_ID:  X64_0x19_22_atikmdag+54d84

BUCKET_ID:  X64_0x19_22_atikmdag+54d84

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

Ken J

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.
My System SpecsSystem Spec
03 Jan 2011   #3
SirWilhelm

Windows 7 Enterprise 64bit
 
 

Thanks, I've done this and will see if it helps.
1. uninstalled current drivers with standard windows unistall. 2. Restarted in safe mode. 3. in safe mode run Driver Sweeper and removed everything with ATI drivers 4. restart again in normal mode 5. installed new ATI drivers only
My System SpecsSystem Spec
.


16 Jan 2011   #4
SirWilhelm

Windows 7 Enterprise 64bit
 
 
...and another BSOD

ok, so received yet another BSOD today. Very not so cool.

Attaching reports.

Havent updated any drivers or other since the last above uninstall/reinstall.

Couple of regular Windows updates yesterday though...could they be the cause?
My System SpecsSystem Spec
Reply

 BSOD Windows 7 64bit PSHED.dll + ntoskrnl




Thread Tools



Similar help and support threads for2: BSOD Windows 7 64bit PSHED.dll + ntoskrnl
Thread Forum
ntoskrnl.exe windows 7 64bit BSOD Help and Support
Solved BSOD ntoskrnl.exe 64bit BSOD Help and Support
DIY Biostar System Keeps Blue Screening -PSHED.dll, NTLOS Kernel BSOD Help and Support
BSOD Win7 Pro 64bit - ntoskrnl.exe?? BSOD Help and Support
Win7 64bit, ntoskrnl.exe - DRIVER_VERIFIER_DETECTED_VIOLATION BSOD Help and Support
Random BSOD on Win 7 64bit.Probable cause: ntoskrnl.exe BSOD Help and Support
PSHED.DLL missing or corrupt General Discussion

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 11:12 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App