need help with blue screen error

[win2]

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


Loading Dump File [C:\Users\Harjeet\Desktop\042111-28688-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03060e90
Debug session time: Thu Apr 21 15:25:38.330 2011 (UTC + 1:00)
System Uptime: 0 days 0:21:53.000
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+80610 )

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

 

[zigzag3143]

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


Loading Dump File [C:\Users\Harjeet\Desktop\042111-28688-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03060e90
Debug session time: Thu Apr 21 15:25:38.330 2011 (UTC + 1:00)
System Uptime: 0 days 0:21:53.000
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+80610 )

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

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[win2]

zip file

hope this help

 

[zigzag3143]

hope this help

Three problems

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it. (ASUSTeK Computer Inc. -Support- Drivers and Download Tools)
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).


2-AVG. Often causes BSOD's. remove and replace with Microsoft Security Essentials


AVG - Download tools

http://www.microsoft.com/security_essentials/



3-Hardware. The above may fix this, or may not.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

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


Loading Dump File [C:\Users\K\Desktop\042111-28688-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;srv*e:\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.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03060e90
Debug session time: Thu Apr 21 10:25:38.330 2011 (GMT-4)
System Uptime: 0 days 0:21:53.000
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( usbehci!EHCI_sMode_InitEndpoint+1e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+55f4952f03fade80
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8000441c7d8 -- (.exr 0xfffff8000441c7d8)
ExceptionAddress: fffff88004405d7e (usbehci!EHCI_sMode_InitEndpoint+0x000000000000001e)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff8000441c880 -- (.trap 0xfffff8000441c880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001c56e1d3 rbx=0000000000000000 rcx=fffff88005aa3180
rdx=fffff88005aa2180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004405d7e rsp=fffff8000441ca18 rbp=fffffa80053f76a0
 r8=fffffa8005e2c500  r9=0000000000000000 r10=fffffa8005e2c250
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na po cy
usbehci!EHCI_sMode_InitEndpoint+0x1e:
fffff880`04405d7e 004883          add     byte ptr [rax-7Dh],cl ds:1021:00000000`1c56e156=??
Resetting default scope

MISALIGNED_IP: 
usbehci!EHCI_sMode_InitEndpoint+1e
fffff880`04405d7e 004883          add     byte ptr [rax-7Dh],cl

LAST_CONTROL_TRANSFER:  from fffff80002e92ffe to fffff80002e9b610

STACK_TEXT:  
fffff800`0441b8b8 fffff800`02e92ffe : fffffa80`049b6490 fffffa80`04885000 fffff800`0441c030 fffff800`02ec72a0 : nt!KeBugCheck
fffff800`0441b8c0 fffff800`02ec6f6d : fffff800`030a2a10 fffff800`02fdec78 fffff800`02e1b000 fffff800`0441c7d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`0441b8f0 fffff800`02ec5d45 : fffff800`02fe20fc fffff800`0441b968 fffff800`0441c7d8 fffff800`02e1b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`0441b920 fffff800`02ed6dc1 : fffff800`0441c7d8 fffff800`0441c030 fffff800`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
fffff800`0441c000 fffff800`02e9acc2 : fffff800`0441c7d8 fffffa80`05e2c4e0 fffff800`0441c880 fffff880`05aa2180 : nt!KiDispatchException+0x135
fffff800`0441c6a0 fffff800`02e98e1f : fffff800`0441c880 fffff880`00000002 fffffa80`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`0441c880 fffff880`04405d7e : fffff880`044064ca 00000000`0000001f fffff880`05aa2180 fffffa80`05e2c4e0 : nt!KiInvalidOpcodeFault+0x11f
fffff800`0441ca18 00000000`00000000 : fffffa80`053f61a0 fffffa80`05e2c250 fffffa80`053f76a0 fffffa80`05e2c010 : usbehci!EHCI_sMode_InitEndpoint+0x1e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_sMode_InitEndpoint+1e
fffff880`04405d7e 004883          add     byte ptr [rax-7Dh],cl

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  usbehci!EHCI_sMode_InitEndpoint+1e

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_usbehci.sys

BUCKET_ID:  X64_IP_MISALIGNED_usbehci.sys

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

When the above is fixed we may have to start examining USB because it is mentioned in several.

 

[win2]

another blue screen error

thanks for the help for first one

 

[zigzag3143]

thanks for the help for first one

Could not read faulting driver name but curseClient was running at the time.


Please run driver verifier to find which driver.

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

 

[win2]

blue screen crash

any help would be appreciated

 

[win2]

need help fixing my blue screen error

i rebooted my computer so i think error cause by the hardware

 

[JMH]

i rebooted my computer so i think error cause by the hardware

Win2 welcome

I doubt that it is hardware there are several software problems that definitely cause bsod's.

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).


2-multiple anti virus applications are never recommended. You have Avast and Eset loaded in these minidumps.

I would remove both and replace them with Microsoft Security Essentials

http://files.avast.com/files/eng/aswclear5.exe

http://download.eset.com/special/ESETUninstaller.exe

http://www.microsoft.com/security_essentials/


Let us know if you need assistance

 

[win2]

blue screen error

i ve few errors any help is welcome

 

[JMH]

i ve few errors any help is welcome

Win 2 hi and welcome

You have several problems here


1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE http://support.asus.com/download/do...oduct=1&model=P7P55D LE&SLanguage=en-us&os=30
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).




2- You have two malware applications, never a good idea. Please remove both and replace with Microsoft Security Essentials

http://files.avast.com/files/eng/aswclear5.exe

http://download.eset.com/special/ESETUninstaller.exe


http://www.microsoft.com/security_essentials/


3-Old drivers please update at least these

scmndisp.sys    1/17/2007 03:48:03 AM    fffff880`015da000    0x0000a000    0x45add4b3    fffff880`015d0000                            
spldr.sys    5/11/2009 12:56:27 PM    fffff880`015e9000    0x00008000    0x4a0858bb    fffff880`015e1000                            
GEARAspiWDM.sys    5/18/2009 08:17:04 AM    fffff880`0483a000    0x0000d000    0x4a1151c0    fffff880`0482d000                            
amdxata.sys    5/19/2009 01:56:59 PM    fffff880`00ff8000    0x0000b000    0x4a12f2eb    fffff880`00fed000                            
L1E62x64.sys    6/11/2009 02:45:22 AM    fffff880`041ea000    0x00012000    0x4a30a802    fffff880`041d8000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[win2]

another blue screen crash

help me with blue screen it annoying me

 

[zigzag3143]

help me with blue screen it annoying me

This one was related to dxgmms1.sys (your video driver/card). I would re-install just the driver using this method

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

Or if the above doesnt work for you. Phyxion.net - Driver Sweeper

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

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


Loading Dump File [C:\Users\K\Desktop\052411-19297-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a59000 PsLoadedModuleList = 0xfffff800`02c96e50
Debug session time: Tue May 24 13:24:43.183 2011 (GMT-4)
System Uptime: 0 days 2:02:01.025
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88005167ec2, fffff880040fe818, fffff880040fe080}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProfilePerformanceTick+736 )

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

2: 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: fffff88005167ec2, The address that the exception occurred at
Arg3: fffff880040fe818, Exception Record Address
Arg4: fffff880040fe080, 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: 
dxgmms1!VidSchiProfilePerformanceTick+736
fffff880`05167ec2 4c8d9c2490000000 lea     r11,[rsp+90h]

EXCEPTION_RECORD:  fffff880040fe818 -- (.exr 0xfffff880040fe818)
ExceptionAddress: fffff88005167ec2 (dxgmms1!VidSchiProfilePerformanceTick+0x0000000000000736)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000001
Attempt to write to address 0000000000000001

CONTEXT:  fffff880040fe080 -- (.cxr 0xfffff880040fe080)
rax=0000000000000001 rbx=0000000000000000 rcx=000000000000000e
rdx=fffffa8003a02410 rsi=fffff88003c1ea08 rdi=0000000000000000
rip=fffff88005167ec2 rsp=fffff880040fea50 rbp=0000000000000003
 r8=0000000000000000  r9=0000000000000000 r10=0000000000005866
r11=fffffa8004297168 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffffa8003a02410
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
dxgmms1!VidSchiProfilePerformanceTick+0x736:
fffff880`05167ec2 4c8d9c2490000000 lea     r11,[rsp+90h]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000001

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d010e0
 0000000000000001 

FOLLOWUP_IP: 
dxgmms1!VidSchiProfilePerformanceTick+736
fffff880`05167ec2 4c8d9c2490000000 lea     r11,[rsp+90h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff880051942ea to fffff88005167ec2

STACK_TEXT:  
fffff880`040fea50 fffff880`051942ea : 00000000`00000001 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProfilePerformanceTick+0x736
fffff880`040feb10 fffff880`051672c6 : ffffffff`ff676980 fffffa80`03a02410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x22a
fffff880`040febb0 fffff880`05193e7a : 00000000`00000000 fffffa80`04a43c50 00000000`00000080 fffffa80`03a02410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`040fecc0 fffff800`02d6c7c6 : 00000000`01ddb393 fffffa80`04fa8b60 fffffa80`039cc040 fffffa80`04fa8b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`040fed00 fffff800`02aa7c26 : fffff800`02c43e80 fffffa80`04fa8b60 fffff800`02c51c40 fffff880`0121f2b4 : nt!PspSystemThreadStartup+0x5a
fffff880`040fed40 00000000`00000000 : fffff880`040ff000 fffff880`040f9000 fffff880`040fe650 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidSchiProfilePerformanceTick+736

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

STACK_COMMAND:  .cxr 0xfffff880040fe080 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VidSchiProfilePerformanceTick+736

BUCKET_ID:  X64_0x7E_dxgmms1!VidSchiProfilePerformanceTick+736

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

 

[win2]

blue screen error

another error

 

[zigzag3143]

another error

\


No useful info in this one.

 

[win2]

another crash

I am having some crashes that go black and grey lines going horizontal.

 

[yowanvista]

Its a hardware error caused by defective components such as your CPU, RAM or Graphics card
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

   Information

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
What graphics card are you using?

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004f26038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031a16b0 fffff800`02d17a99 : fffffa80`04f26010 fffffa80`039fbb60 00000000`00000009 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a1bd0 fffff800`02bf9677 : fffffa80`04f26010 fffff800`02c725f8 fffffa80`039fbb60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a1c00 fffff800`02b61c45 : fffff800`02cd4360 fffffa80`04922ab8 fffffa80`04922ab0 fffffa80`039fbb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a1c40 fffff800`02ada961 : fffff880`0111ee00 fffff800`02b61c20 fffffa80`039fbb60 96e90000`0230b701 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a1c70 fffff800`02d707c6 : 478b4900`00043c83 fffffa80`039fbb60 00000000`00000080 fffffa80`039e6040 : nt!ExpWorkerThread+0x111
fffff880`031a1d00 fffff800`02aabc26 : fffff880`02f63180 fffffa80`039fbb60 fffff880`02f6dfc0 24848b41`00000428 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d40 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`037de500 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

 

[win2]

graphic card

ATI Radeon HD 5700 Series

 

[win2]

error

it say blue screen but when the error happen the screen turn red