BSOD during random actions, no signal after computer sleeps

[cwburns32]

I did not install anything, ATI was already installed when I first booted up computer. I followed instructions to a T in the link provided. Even in that link the instructions say that some drivers may stay installed some you may have to reinstall. When I booted up computer my graphics driver was already installed.

 

[cwburns32]

Came home from work with another issue, different BSOD...

And I am reinstalling old graphics driver as every time the newer one is installed it seems that there are more issues.

 

[TVeblen]

The point of the troubleshooting guide is to eliminate all the correctable problems with software and setup before arriving at the inevitable conclusion that the hardware is defective. This is a better course of action than just replacing parts randomly.

When a video card crashes the system upon installation of new drivers, but works fine using older drivers, then that raises a few possibilities:

• The new drivers are no good (error at the manufacturer)
• The download is corrupted
• The installation* is no good
• The video card is no good**

* When dealing with problem drivers it is important to do a "clean" install:

Go to Start > Control Panel > Programs > Uninstall a program. Uninstall all the video apps (i.e.: nVidia 3D, PhysX) first, then uninstall the driver (the Control Panel will go with the driver). You will be asked to restart > restart.

When the computer reboots to the desktop Windows will install it's own generic WDDM1.1 driver and you will be asked to restart again. You must do so in order to install the new Drivers > Restart.

[At the above point in the process you could also press F8 during re-boot to get to the Windows boot menu. If you select "Start with VGA graphics" you can get to the (800x600) desktop without any installed drivers. This is usually not necessary.]

Once back on the desktop you can now install the new drivers from your download.




** Sometimes the manufacturer enables a feature of the video card in the new version of the driver package that the card should be able to execute. If that part of the card is defective the defect will not show until that feature has been activated.


Hope that helps.

 

[Arc]

► Install Service pack 1.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

► Test your RAM modules for possible errors.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003403991, fffff88008b91af0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003403991, Address of the instruction which caused the bugcheck
Arg3: fffff88008b91af0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAllocatePoolWithTag+5c1
fffff800`03403991 488910          mov     qword ptr [rax],rdx

CONTEXT:  fffff88008b91af0 -- (.cxr 0xfffff88008b91af0)
rax=fefff8000345ea80 rbx=fffffa8009c44c00 rcx=fffff8000345ea80
rdx=fffffa8009c44b40 rsi=0000000000001000 rdi=0000000000000000
rip=fffff80003403991 rsp=fffff88008b924d0 rbp=fffff8000345e880
 r8=0000000000000000  r9=fffff8000345ee80 r10=fffff8000345e888
r11=0000000000000001 r12=0000000000000040 r13=0000000000000000
r14=0000000000000000 r15=0000000020707249
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ExAllocatePoolWithTag+0x5c1:
fffff800`03403991 488910          mov     qword ptr [rax],rdx ds:002b:fefff800`0345ea80=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  TrustedInstall

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003403991

STACK_TEXT:  
fffff880`08b924d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x5c1


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff80003403657-fffff80003403b17)
fffff80003403650  8b  d8  e9  88  fe  ff  ff *f1  43  83  44  2c  18  01  f0  4b ........C.D,...K
...
fffff80003403b10  50  48  39  00  0f  84  ee *ff  ff  ff  e8  65  f0  e7  ff  e9 PH9........e....

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88008b91af0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Disc check:

1. Update your SSD's Firmware (Skip it if it is not a SSD)
2. Re-seat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

 

[cwburns32]

The point of the troubleshooting guide is to eliminate all the correctable problems with software and setup before arriving at the inevitable conclusion that the hardware is defective. This is a better course of action than just replacing parts randomly.

When a video card crashes the system upon installation of new drivers, but works fine using older drivers, then that raises a few possibilities:

• The new drivers are no good (error at the manufacturer)
• The download is corrupted
• The installation* is no good
• The video card is no good**

* When dealing with problem drivers it is important to do a "clean" install:

Go to Start > Control Panel > Programs > Uninstall a program. Uninstall all the video apps (i.e.: nVidia 3D, PhysX) first, then uninstall the driver (the Control Panel will go with the driver). You will be asked to restart > restart.

When the computer reboots to the desktop Windows will install it's own generic WDDM1.1 driver and you will be asked to restart again. You must do so in order to install the new Drivers > Restart.

[At the above point in the process you could also press F8 during re-boot to get to the Windows boot menu. If you select "Start with VGA graphics" you can get to the (800x600) desktop without any installed drivers. This is usually not necessary.]

Once back on the desktop you can now install the new drivers from your download.




** Sometimes the manufacturer enables a feature of the video card in the new version of the driver package that the card should be able to execute. If that part of the card is defective the defect will not show until that feature has been activated.


Hope that helps.

► Install Service pack 1.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

► Test your RAM modules for possible errors.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003403991, fffff88008b91af0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003403991, Address of the instruction which caused the bugcheck
Arg3: fffff88008b91af0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAllocatePoolWithTag+5c1
fffff800`03403991 488910          mov     qword ptr [rax],rdx

CONTEXT:  fffff88008b91af0 -- (.cxr 0xfffff88008b91af0)
rax=fefff8000345ea80 rbx=fffffa8009c44c00 rcx=fffff8000345ea80
rdx=fffffa8009c44b40 rsi=0000000000001000 rdi=0000000000000000
rip=fffff80003403991 rsp=fffff88008b924d0 rbp=fffff8000345e880
 r8=0000000000000000  r9=fffff8000345ee80 r10=fffff8000345e888
r11=0000000000000001 r12=0000000000000040 r13=0000000000000000
r14=0000000000000000 r15=0000000020707249
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ExAllocatePoolWithTag+0x5c1:
fffff800`03403991 488910          mov     qword ptr [rax],rdx ds:002b:fefff800`0345ea80=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  TrustedInstall

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003403991

STACK_TEXT:  
fffff880`08b924d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x5c1


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff80003403657-fffff80003403b17)
fffff80003403650  8b  d8  e9  88  fe  ff  ff *f1  43  83  44  2c  18  01  f0  4b ........C.D,...K
...
fffff80003403b10  50  48  39  00  0f  84  ee *ff  ff  ff  e8  65  f0  e7  ff  e9 PH9........e....

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88008b91af0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Disc check:

1. Update your SSD's Firmware (Skip it if it is not a SSD)
2. Re-seat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

Will do both of these right now and report back later on. Sorry been away from the house for the holidays. Out of town.

 

[cwburns32]

The point of the troubleshooting guide is to eliminate all the correctable problems with software and setup before arriving at the inevitable conclusion that the hardware is defective. This is a better course of action than just replacing parts randomly.

When a video card crashes the system upon installation of new drivers, but works fine using older drivers, then that raises a few possibilities:

• The new drivers are no good (error at the manufacturer)
• The download is corrupted
• The installation* is no good
• The video card is no good**

* When dealing with problem drivers it is important to do a "clean" install:

Go to Start > Control Panel > Programs > Uninstall a program. Uninstall all the video apps (i.e.: nVidia 3D, PhysX) first, then uninstall the driver (the Control Panel will go with the driver). You will be asked to restart > restart.

When the computer reboots to the desktop Windows will install it's own generic WDDM1.1 driver and you will be asked to restart again. You must do so in order to install the new Drivers > Restart.

[At the above point in the process you could also press F8 during re-boot to get to the Windows boot menu. If you select "Start with VGA graphics" you can get to the (800x600) desktop without any installed drivers. This is usually not necessary.]

Once back on the desktop you can now install the new drivers from your download.




** Sometimes the manufacturer enables a feature of the video card in the new version of the driver package that the card should be able to execute. If that part of the card is defective the defect will not show until that feature has been activated.


Hope that helps.

Did clean install of display driver and all display applications.

 

[cwburns32]

► Install Service pack 1.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

► Test your RAM modules for possible errors.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003403991, fffff88008b91af0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003403991, Address of the instruction which caused the bugcheck
Arg3: fffff88008b91af0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAllocatePoolWithTag+5c1
fffff800`03403991 488910          mov     qword ptr [rax],rdx

CONTEXT:  fffff88008b91af0 -- (.cxr 0xfffff88008b91af0)
rax=fefff8000345ea80 rbx=fffffa8009c44c00 rcx=fffff8000345ea80
rdx=fffffa8009c44b40 rsi=0000000000001000 rdi=0000000000000000
rip=fffff80003403991 rsp=fffff88008b924d0 rbp=fffff8000345e880
 r8=0000000000000000  r9=fffff8000345ee80 r10=fffff8000345e888
r11=0000000000000001 r12=0000000000000040 r13=0000000000000000
r14=0000000000000000 r15=0000000020707249
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ExAllocatePoolWithTag+0x5c1:
fffff800`03403991 488910          mov     qword ptr [rax],rdx ds:002b:fefff800`0345ea80=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  TrustedInstall

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003403991

STACK_TEXT:  
fffff880`08b924d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x5c1


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff80003403657-fffff80003403b17)
fffff80003403650  8b  d8  e9  88  fe  ff  ff *f1  43  83  44  2c  18  01  f0  4b ........C.D,...K
...
fffff80003403b10  50  48  39  00  0f  84  ee *ff  ff  ff  e8  65  f0  e7  ff  e9 PH9........e....

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88008b91af0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Disc check:

1. Update your SSD's Firmware (Skip it if it is not a SSD)
2. Re-seat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

Having world of trouble installing SP1 or any update for that matter. Tried all the Microsoft troubleshooting, the Automatic Troubshooter and the Windows Update System Readiness update to no avail.... Now I am stuck.

UPDATE: Since uninstalling graphics driver and reinstalling haven't seen any issues but it may be to early to tell. Whenever I try and update to SP1 or any of the other available updates I get these two errors...

Code 800B0100
Code 8024200D

Like I mentioned above, tried all troubleshooting to no avail. Remaining patient but starting to become frustrated.

 

[Arc]

I am asking NoelDP to have a look.

 

[NoelDP]

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and attach it to your reply.

 

[cwburns32]

Doing this now. Will edit post when it is done with zipped file.

EDIT: File uploaded.

 

[NoelDP]

You have a rather large number of errors present, many involving vbscript and jscript.
It's only just about within the realms of many (many?) manual (!) fixing (rather than a repair install), and could take some time for me to craft a fix - please be patient.
If you haven't heard within 24 hours, please shout at me

 

[NoelDP]

I think I've get them all now. (we'll soon see!)


I've uploaded a file - CWB Files.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder CWB Files in the same place.

Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the

C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[cwburns32]

I think I've get them all now. (we'll soon see!)


I've uploaded a file - CWB Files.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder CWB Files in the same place.

Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the

C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

Copy the packages content to the C:\...\packages and manifest content to C:\...\manifests and replace the existing files in each folder? Or just paste them into those folders without replacing old files?

 

[NoelDP]

just copy/paste them - no need to delete the old ones

 

[cwburns32]

just copy/paste them - no need to delete the old ones

That's what I thought but it tells me there are some duplicates and if I want to replace those with the new ones. Sorry to keep slamming you with questions just want to get this straight.

25 conflicts with packages and 15 with manifests...

EIDT: Here is CheckSUR, copied over the files that were in the folder... hope that was okay.

 

[NoelDP]

That wasn't too bad - I just missed 4 pairs.
(in a list that long, it's easy to get lost!

back with hopefully the last ones later.

 

[NoelDP]

...actually, looking closer, I only missed two

Same procedure - the new download file is
CWBfiles2.zip

 

[cwburns32]

...actually, looking closer, I only missed two

Same procedure - the new download file is
CWBfiles2.zip

You sir are very helpful, thanks so much! Unfortunately this a problem I found within a problem within a problem. Hopefully you can help me with my other issues as soon as you fix this one. Regardless I appreciate your fast responses and wonderful help!

 

[NoelDP]

Great - that's cleared CheckSUr of problems.

Now please run SFC /SCANNOW (from an elevated command prompt!), and post the new CBS.log
....


SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.


Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and attach it to your response.

 

[cwburns32]

Great - that's cleared CheckSUr of problems.

Now please run SFC /SCANNOW (from an elevated command prompt!), and post the new CBS.log
....


SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.


Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and attach it to your response.

Here you are sir.