BSOD Vista - stop 0x7F {8, 801fd000, 0, 0}

Similar Questions

• Satellite A210 - Vista stopped recording operation

  Hi Forum,

  Whenever I start my A210 Satellite it calls an error message 'Recording Vista stopped functioning' (translated from the French). Does anyone have a solution for this horse?
  I wonder if something really bad could happen anytime soon.

  Thanks for any help.
  Pier

  Your laptop factory settings or you have installed Vista clean?

• Vista Stop error message: 0XC012001D after the installation of Windows updates.

  Original title: vista stop working

  Hello

  I need help on vista, because I update and restart and stop working and appear this error code:

  !! 0xc012001d! Registry\Machine\Components\DriverData...

  Hello

   

  
  1. remember the number of the update you have installed?
  2. could you give us the exact error message?
  3. Once you get this error message? Are you able to boot to the desktop?

   

  Method 1.
  Please check if you face the same problem when recording in safe mode. It is a possibility that one of the non-Microsoft application or driver is causing this issue. Start in safe mode and make sure that us. If you are able to start properly in safe mode, we can perform a clean boot in order to find the root cause.
   
  Step A.
  a. restart your computer.
  b. when the computer starts, you will see your computer hardware are listed. When you see this information tap the F8 on your keyboard key repeatedly until you are presented with the screen Windows Vista Advanced Boot Options.
  c. using the arrow keys, select the desired option of Mode without failure.
  d. press the Enter key on your keyboard to start in safe mode of Windows Vista.
  e. when Windows starts, you will be at a typical logon screen. Connect to your computer and the Windows Vista goes into safe mode.
  f. do whatever tasks you need and when you are done, reboot to return to normal mode.
   
  Step B.
  If it works fine in safe mode try performing a clean boot in order to find the cause root.
  See the article below for instructions on how to start your computer in a clean boot state.
  How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
  http://support.Microsoft.com/kb/929135
  Note: When the diagnosis is complete do not forget to reset the computer to a normal startup. Follow step 7 in the above article.
   

   

  Method 2.
  Best thing you can do is to perform a system restore just before where the problem occurred.
  I have listed a few articles that explain the system restore in Windows 7.
  System Restore: frequently asked questions
  http://Windows.Microsoft.com/en-us/Windows-Vista/system-restore-frequently-asked-questions

  
  System restore
  http://Windows.Microsoft.com/en-us/Windows7/products/features/system-restore

  Thus, the article above is applicable to Windows Vista.

   

   

  I hope this helps.

  Thank you, and in what concerns:
  Shekhar S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.
  If this post can help solve your problem, please click the 'Mark as answer' or 'Useful' at the top of this message. Marking a post as answer, or relatively useful, you help others find the answer more quickly.

• Once more my automatic update of Vista stopped working today.

  Once more my automatic update of Vista stopped working today; It looks updates constantly and never ends. Set to automatic update was working yesterday the download and installation of Windows Defender - KB915597 (1.229.1407.0 and 1.229.1054.0 definitions).  This issue happened on August 9, 2016 when Windows Defender - KB915597 (definition 1.225.3489.0) has successfully installed on 8 August.

  Volume Z replied to my request for help the Oct 1 instruct me to download and run KB3185911 by his specific instructions.  This clear up my problem.  I tried to run this file (. Windows6 0-KB3185991-x 86.msu) still today after initial Volume Z instructions and received the notice, it did not apply to my system.

  The issue was revived by the release yesterday of KB3191203.

  https://www.Microsoft.com/en-US/Download/details.aspx?ID=53972

  Best regards, VZ

• Vista stops himself and goes to a blue screen with the error code debug_usb_code.

  Vista stops himself, and a blue screen appears with a debug_usb_code.  I have problems with windows shut.  Tried a restore point.  Finished in the configuration of the system and found that the windows Defender has been the origin of the problem at startup.  I disabled it, and the computer is now in operation.  However, it is slow, sometimes crashes after about an hour, it will be stopped by itself and give the code mentioned above on a blue screen error.  Then it will restart by itself.  Please help!

  Run systempropertiesadvanced.exe and in the startup and recovery section, click settings.  Then uncheck 'automatically restart '.

• Get the error as a broker for Vista stopped working when trying to start the Webex session

  Original title: broker for vista stopped working

  Anyone know what this means?  I get this message every time I try to open a Webex session.   I work under Vista

  Hello

  The question you posted would be better suited in the Cisco Forums. I would recommend posting your query in the Cisco Forum site:

  https://supportforums.Cisco.com/index.jspa

• Vista stops on its own

  Vista stops periodically restarts with the message, do not turn your computer off, 1 of 3, etc.  What needs to be fixed?

  Hello

  You can use the solutions in this KB - 3 methods and I listed a little help for them below

  The update is not installed successfully, you receive a message, and the computer restarts when you try to
  install an update in Windows Vista and Windows 7
  http://support.Microsoft.com/kb/949358

  Method 1: Start Windows Vista/Windows 7 with the Windows installation media and use the repair feature

  How to do a startup repair in Vista and Windows 7
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

  You can also do a safe mode startup repair to access the Recovery Options If you have them available
  or use the DVD as described above.

  This tells you how to access the system - Vista Recovery Options
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  This tells you how to access the system - Windows 7 Recovery Options
  http://Windows.Microsoft.com/en-us/Windows7/Startup-Repair-frequently-asked-questions

  Try recovery options Startup Repair

  How to do a startup repair
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

  Method 2: Start the system in safe mode and then use the system restore feature

  How to do a system restore in Vista and Windows 7
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

  You can also do a restore of the system of starting with a disk of Vista or Windows 7.

  Method 3: Use the downloads at the end of this article - note for Vista x 86 versions 32 bit and Vista
  x 64 64-bit.

  The update is not installed successfully, you receive a message, and the computer restarts when you try to
  install an update in Windows Vista and Windows 7
  http://support.Microsoft.com/kb/949358

  ------------------------------------------------------

  Once you are in Windows I was running once again reset here as a precaution.

  How to reset the Windows Update components?
  http://support.Microsoft.com/kb/971058

  Hope this helps sort it out for you.
  Rob - bicycle - Mark Twain said it is good.

• all the time on vista blue screen - stop 0x7F

  I get this blue screen im on vista please help me
  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.0.6002.2.2.0.768.3
  Locale ID: 2057

  More information about the problem:
  BCCode: 1000007f
  BCP1: 00000008
  BCP2: 80156000
  BCP3: 00000000
  BCP4: 00000000
  OS version: 6_0_6002
  Service Pack: 2_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\Mini061811-03.dmp
  C:\Users\dan\AppData\Local\Temp\WER-170437-0.SysData.XML
  C:\Users\dan\AppData\Local\Temp\WER924F.tmp.version.txt

  Read our privacy statement:
  http://go.Microsoft.com/fwlink/?LinkId=50163&clcid=0x0409

  Hello

  You have ZoneAlarm or any 3rd party firewall installed? If so, this could be the cause.
  Other antivirus/security programs could be at least partially responsible.

  This fix "could" apply however do not use if you are quite safe.

  Two drivers of platform using WFP (Windows Filtering) causes a computer crash when the
  computer running Windows Vista, Windows 7 or Windows Server 2008
  http://support.Microsoft.com/kb/979278

  Check also:

  The General causes of errors "STOP 0x0000007F" (applies to Vista and Windows 7 as well)
  http://support.Microsoft.com/kb/137539

  ===========================================================

  For the methods of troubleshooting blue screen using BlueScreenView and MyEventViewer see my answers
  If this thread - top 3 RESPONSES (+ 1 other).

  http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

  We can analyze the minidumps if make you it available to the SkyDrive or another file
  sharing sites.

  ZIP or download the content of the C:\Windows\minidump

  Use SkyDrive to upload collected files.
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  ----------------------------------------------------

  BCCode: 0x0000007f with the parameter 00000008 7f usually means a hardware problem.

  Have you added a hardware or drivers updated recently? Check Control Panel - Windows
  Updates to see if all drivers have been updated it just before what is going on has begun.

  For 7f - this could be a problem of material such as uncomfortable cards or memory, while there are
  other causes. Power electric low could also lead to this. Use the troubleshooters above and below
  and when you get to the drivers and memory sections refer to my next message below and then
  return if necessary troubleshooting services

  If a PC remove ALL power. Opening the case, remove and reinstall all memory cards and ALL
  cable (try not just to close) on both ends if they are accessible and on the device ends if not
  (remove the cables and the resettlement of help them to eliminate minor corrosion).

  Notice the 08 (double fault) as 1st parameter means there are likely two causes. Do not forget to update
  your drivers manually as using Windows updates are only certified and Microsoft drivers and
  device manufacturers are far behind in this process. NETWORK, WiFi, BIOS and video/display card update and
  other major engines

  If a laptop or a PC, you will need to take a shop (not BestBuy or other BigBox stores) or your
  Support of the machine system.

  ----------------------------------------------------------------------

  BCCode: 7F 0x0000007F which is the same as 0x1000007F

  UNEXPECTED_KERNEL_MODE_TRAP bug control has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel could not catch this trap.

  This trap might be a bound trap (a trap the kernel is not allowed to capture) or adouble foul(an error occurred during the processing of an earlier fault, which always results in a failure of the system).

  Parameters

  The first parameter that is displayed on the blue screen indicates the number of trap.

  The most common trap codes are the following:

  • 0x00000000 or division by zero error, indicates that a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems or software failures can cause this error.
  • 0 x 00000004, or overflow, occurs when the processor executes a call to an interrupt handler when the overflow (OF) is flag set.
  • 0x00000005, or limits check fault, indicates that the processor, then executing a BOUND instruction, determines that the operand exceeds the specified limits. A BOUND instruction ensures that a signed array index is within a certain range.
  • 0 x 00000006 or Opcode not valid, indicates that the processor attempts to execute an invalid instruction. This error occurs generally when the instruction pointer is corrupted and point to the wrong address. The most common cause of this error is hardware memory corruption.
  • 0x00000008 or Double fault, indicates that an exception occurs during a call to the previous exception handler. In general, two exceptions are handled in series. However, there are several exceptions that cannot be handled serially, and in this case, the processor signals a double fault. There are two common causes of a double fault

  
  CAUSE

  0x7F bug check occurs after the installation of a faulty or incompatible hardware (including memory) or if installed hardware fails.

  A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same battery. For example, if two file system filter drivers are associated to the same stack and then again the recursively of file system, the capacity of the battery.

  
  Solve the problem

  Troubleshooting: If you have recently added the material to the computer, remove to see if the error recurs. If the hardware failure existing, remove or replace the faulty component. Run the diagnostics of material that does not have the system manufacturer supplies to determine which hardware component.

  The scanner memory is particularly important. Faulty or incompatible memory can cause this bug check. For more information on these procedures, see the manual of your computer. Check that all the cards in the computer are well calibrated. Use an ink eraser or electrical contact treatment, available in electronic supply stores, to ensure the adapter card contacts are clean.

  If the error appears on a newly installed system, check the availability of updates for BIOS, SCSI, or card network controller. These updates are generally available on the Web site or the hardware manufacturer BBS.

  Confirm that all hard drives, hard disk controllers and SCSI adapters are listed in the list of the products tested Microsoft Windows market.

  If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver. If, in this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system Safe Mode, you must start the computer by using the Recovery Console in order to access the file.

  Also to restart your computer and press F8 to character-based menu that displays the choice of operating system. In the menuof Advanced Options , select thelast known good Configuration option. This option is most effective when you add a single driver or service at a time.

  Overclocking (setting of the CPU to run at a speed higher than the nominal specification) can cause this error. If you have overclocked to the computer that is experiencing the error, return the CPU to default clock speed setting.

  Check the system log in Event Viewer for additional error messages that might help identify the device or driver that generated the error. You can also disable caching memory BIOS to try to resolve the problem.

  If you have encountered this error during the upgrade to a new version of the Windows operating system, the error can be caused by a device driver, system service, an anti-virus or a backup tool that is not compatible with the new version. If possible, remove all third-party device drivers and system services and disable all antivirus before upgrade you. Contact the software manufacturer for updates of these tools. Also, make sure that you have installed the latest Windows Service Pack.

  Finally, if all of the steps above do not resolve the error, take the system motherboard to a repair for the diagnostic facility. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.

  BCCode: 7F 0x0000007F which is the same as 0x1000007F<-- read="" this="">
  * 1304.html http://www.faultwire.com/solutions-fatal_error/Run-a-System-diagnostic-Utility-supplied-by-your-0x1000007F-

  ==================================================================

  Look in the Event Viewer to see if something is reported on those.
  http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  -------------------------------------------------------------------------
  Also this, so you can see the probable bluescreens.

  Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
  http://www.winvistatips.com/disable-automatic-restart-T84.html

  -------------------------------------------------------------------------

  Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
  info that would help. Such as ITC and 4 others entered at the bottom left. And all others
  error information such as codes of STOP and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

  As examples:

  BCCode: 116
  BCP1: 87BC9510
  BCP2: 8C013D80
  BCP3: 00000000
  BCP4: 00000002

  or in this format:

  Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
  Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

  It is an excellent tool for displaying the blue screen error information

  BlueScreenView scans all your minidump files created during 'blue screen of death '.
  hangs and displays information about all accidents of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged, in particular the video drivers drivers however
  There are other causes.

  You can do without if needed fail or the Vista DVD or recovery command prompt mode
  Options if your system was installed by the manufacturer.

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  You can try a system restore to a point before the problem started when one exists.

  How to make a Vista system restore
  http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

  -------------------------------------------------------------------------

  Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

  Enter this at the command prompt - sfc/scannow

  How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
  generates in Windows Vista cbs.log
  http://support.Microsoft.com/kb/928228

  The log can give you the answer if there is a corrupted driver. (Says not all possible
  driver problems).

  Also run CheckDisk, so we cannot exclude as much as possible of the corruption.

  How to run the check disk at startup in Vista
  http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

  -------------------------------------------------------------------------

  Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, part 3
  keyboard and mouse, as well as of other major device drivers.

  Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
  http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

  How to install a device driver in Vista Device Manager
  http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

  How to disable automatic driver Installation in Windows Vista - drivers
  http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
  http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

  -------------------------------------------------------------------------

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
  quit unexpectedly
  http://support.Microsoft.com/kb/958233

  Troubleshooting, STOP error blue screen Vista
  http://www.chicagotech.NET/Vista/vistabluescreen.htm

  Understanding and decoding BSOD (blue screen of death) Messages
  http://www.Taranfx.com/blog/?p=692

  Windows - troubleshooting blue screen errors
  http://KB.wisc.edu/page.php?id=7033

  -------------------------------------------------------------------------

  In some cases, it may be necessary.

  The Options or Vista recovery disk Startup Repair

  How to do a startup repair
  http://www.Vistax64.com/tutorials/91467-startup-repair.html

  This tells you how to access the System Recovery Options and/or a Vista DVD
  http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">

• BSOD Vista KS.sys

  Just started getting the BSOD with the ks.sys BSOD error. I am attaching the .dmp files as I do not understand what is the cause.

  Signature of the problem:

  Problem event name: BlueScreen

  The system version: 6.0.6001.2.1.0.768.3

  Locale ID: 2057

  More information about the problem:

  BCCode: 3B

  BCP1: 00000000C 0000005

  BCP2: FFFFFA600421A0FE

  BCP3: FFFFFA60051F3E40

  BCP4: 0000000000000000

  OS version: 6_0_6001

  Service Pack: 1_0

  Product: 768_1
  http://www.4shared.com/document/O79H0eOc/WER-38126-0sysdata.html] WER-38126 - 0.sysdata.xml
  http://www.4shared.com/file/8-lgxir7/Mini072011-01.html] Mini072011 - 01.dmp
  http://www.4shared.com/document/sXT_YGpc/WERA2Dtmpversion.html] WERA2D.tmp.version.txt

  Hello AndrewMenzies,

  I took a look in the dump that you file sent and it seems that ks.sys may actually be the victim here.

  Before ks.sys, atihdLH6.sys appears in the stack.  Since it is a minidump, I can't read the dismount, but we generally see a third-party driver sending an invalid parameter to the top of the stack.

  The atihdLH6 driver is fairly new - March 2011.  We check with ATI to see if they have an update for it.  If this isn't the case, then we could revisit the driver that came out before this iteration.

  Here is my analysis of the discharge.  My comments are in "BOLD":

  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: SRV * c:\websymbols* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) free x 64
  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 6001.18538.amd64fre.vistasp1_gdr.101014 - 0432
  Computer name:
  Kernel base = 0xfffff800' 01b 59000 PsLoadedModuleList = 0xfffff800'01e1edb0
  The debugging session: 11:43:14.656 Wed Jul 20 2011 (UTC - 05:00)
  System Uptime: 0 days 0:00:23.825

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck 3B {c0000005, fffffa600421a0fe, fffffa60051f3e40, 0}

  Probably caused by: ks.sys (ks! KspPinPropertyHandler + 17 (a)<-- debugger="" blames="" ks.sys-="" but="" it="" looks="" like="" it="">
  Follow-up: MachineOwner actually the victim here.
  ---------

  2: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  System_service_exception (3B)<-- stop="" code="" and="">
  An exception occurred during the execution of a system service routine.
  Arguments:
  Arg1: 00000000c 0000005, Exception that caused the error checking code
  Arg2: fffffa600421a0fe, the address of the instruction that caused the error checking
  Arg3: fffffa60051f3e40, address of the context record to the exception that caused the error checking
  Arg4: 0000000000000000, zero.

  Debugging information:
  ------------------

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

  FAULTING_IP:
  Msg KspPinPropertyHandler + 17
  fffffa60'0421a0fe 448b0a mov r9d, dword ptr [rdx]<-- this="" could="" very="" well="" be="" from="" a="" bad="" parameter="" that="">
  CONTEXT: fffffa60051f3e40-(.cxr 0xfffffa60051f3e40) spent on top of the stack.
  Rax = fffffa80071324e8 rbx = 0000000000000000 rcx = 0000000000000000
  RDX = 0000000000000000 rsi = rdi fffffa80071322b0 = 0000000000000008
  RIP = fffffa600421a0fe rsp = fffffa60051f46a0 rbp = 0000000000000001
  R8 = 0000000000000001 r9 = 0000000000000002 r10 = fffff8800096e140
  R11 = 00000000fffffff8 r12 = r13 0000000000000008 = fffff8800096e140
  R14 = 00000000ffffffff r15 = 0000000000000001
  iopl = 0 nv in pe of na EI pl nz nc
  CS = 0010 ss = 0018 ds = 002 b're = 002 b fs = 0053 gs = 002 b efl = 00010202
  MSG KspPinPropertyHandler + 0x17a:
  fffffa60'0421a0fe 448b0a mov r9d, dword ptr [rdx] b ds:002: 00000000'00000000 =?
  Reset the default scope

  2: kd > .cxr 0xfffffa60051f3e40<-- getting="" context="">
  Rax = fffffa80071324e8 rbx = 0000000000000000 rcx = 0000000000000000
  RDX = 0000000000000000 rsi = rdi fffffa80071322b0 = 0000000000000008
  RIP = fffffa600421a0fe rsp = fffffa60051f46a0 rbp = 0000000000000001
  R8 = 0000000000000001 r9 = 0000000000000002 r10 = fffff8800096e140
  R11 = 00000000fffffff8 r12 = r13 0000000000000008 = fffff8800096e140
  R14 = 00000000ffffffff r15 = 0000000000000001
  iopl = 0 nv in pe of na EI pl nz nc
  CS = 0010 ss = 0018 ds = 002 b're = 002 b fs = 0053 gs = 002 b efl = 00010202
  MSG KspPinPropertyHandler + 0x17a:
  fffffa60'0421a0fe 448b0a mov r9d, dword ptr [rdx] b ds:002: 00000000'00000000 =?
  2: kd > kv
  Resets to the last context set-.thread/.cxr stack trace it
  Child-SP RetAddr: Args to child: call Site
  "fffffa60 '051f46a0 fffffa60' 0422001b: fffffa80 '071322b 0 fffffa80 ' 07189460 fffffa80' 071322b 0 fffff880 ' 009a 8880: ks! KspPinPropertyHandler + 0x17a
  "fffffa60 '051f46f0 fffffa60' 042f4f32: 00000000' 7070534b fffffa80 ' 07189460 fffff880 ' 009a57e0 00000000'00000020: ks! KsPinPropertyHandler + 0x1b
  fffffa60 '051f4730 fffffa60' 042172ab: fffffa80 '071322b 0 fffffa80' 066f53f0 00000000'00000000 00000000'00000003: portcls! PcPinPropertyHandler + 0 x 152
  fffffa60 '051f4770 fffffa60' 0422059b: 00000000 '00000000 fffff880' fffffa60 00000003 '051f4880 fffff880' 009a8ab0: ks. KspPropertyHandler + 0x6cb
  fffffa60 '051f47d0 fffffa60' 042f5904: fffffa60 ' 051f4880 fffff880 '009a8ab0 fffffa80' 071322b 0 fffffa80 ' 0675dcc0: ks. KsPropertyHandler + 0x1b
  "fffffa60'051f4820 fffffa60'0430869 c: 00000000 ' 00000001 fffffa80 ' 071322b 0 fffffa80 '066f5540 fffffa60' 042d90cb: portcls! PcHandlePropertyWithTable + 0 x 64
  fffffa60 '051f4850 fffffa60' 042f4b01: fffffa80 ' 071322b 0 fffffa80 '066f53f0 fffffa80' 066f5540 fffffa60 ' 051f4a88: portcls! CPortFilterWaveRT::DeviceIoControl + 0 x 144
  fffffa60'051f48b0 fffffa60'042176 8 d: 00000000' c000000d fffffa80 '071324e8 fffffa80' 066f53f0 00000000'60000000: portcls! DispatchDeviceIoControl + 0 x 79
  fffffa60 '051f48e0 fffffa60' 042f406c: fffffa60'051f4a18 11cf51ad '134960 0000 8 c 101' 00000001 f8948a87 c' 00000003: ks! KsDispatchIrp + 0xd8
  fffffa60'051f4910 fffffa60'042 d 3765: 00000000 ' 00000001 fffffa80' 07132530 fffffa60 '051f4a00 fffffa60' 04336a 87: portcls! PcDispatchIrp + 0x5c

  "fffffa60'051f4940 00000000 00000001': fffffa80 ' 07132530 '051f4a00 fffffa60' fffffa60 04336a 87 fffffa80 ' 071322b 0: AtihdLH6 + 0x1b765<-- 3rd="" party="">

  fffffa60'051f4948 fffffa80'07132530: fffffa60'051f4a00 fffffa60 '04336-87 fffffa80' 071322b 0 00000000 00000000': 0 x 1
  fffffa60 '051f4950 fffffa60' 051f4a00: fffffa60'04336 has 87 fffffa80 '071322b 0 00000000 00000000' fffffa80' 0675dcc0: 0xfffffa80'07132530
  fffffa60 '051f4958 fffffa60' 04336a 87: fffffa80' 071322b 0 00000000 00000000' fffffa80 '0675dcc0 fffffa80' 071322b 0: 0xfffffa60'051f4a00
  "" fffffa60 '051f4960 fffffa60' 043367dd: 00000000 ' 00000001 fffffa80 ' 071324e8 fffffa80 ' 07132530 fffffa80 ' 071322b 0: ksthunk! CKSThunkDevice::DispatchIoctl + 0xcf
  fffffa60 '051f4990 fffff800' 01f31a6a: fffffa80 '0675dcc0 fffffa60' 051f4ca0 00000000'00000000 00000000'00000001: ksthunk! CKernelFilterDevice::DispatchIrp + 0x11d
  fffffa60 '051f49f0 fffff800' 01f4a966: fffffa80'06e87c10 00000000'00000000 00000000'00000000 00000000'00000000: nt! IopXxxControlFile + 0x5da
  fffffa60 '051f4b40 fffff800' 01cadeb3: fffff880'0aea91e0 fffffa80 '06ebd700 00000000'00000300 fffff800' 01f2a634: nt! NtDeviceIoControlFile + 0 x 56
  fffffa60 '051f4bb0 00000000' 7739507a: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiSystemServiceCopyEnd + 0 x 13 (TrapFrame @ fffffa60'051f4c20)
  00000000' 0160f3a8 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: 0x7739507a
  2: kd > lmvm AtihdLH6
  start end module name
  fffffa60'042 b 8000 fffffa60'042 d 8000 AtihdLH6 T (no symbol)
  Loaded symbol image file: AtihdLH6.sys
  Image path: \SystemRoot\system32\drivers\AtihdLH6.sys
  Image name: AtihdLH6.sys
  Timestamp: Kills Mar 31 02:15:13 2011 (4D942A01)<-- driver="" is="" fairly="" new. ="" we="" should="" check="" for="" an="" update="" for="" it="" or="" revert="" to="" earlier="">

  Let us know if you have any questions.

  Best regards

  Matthew_Ha

• IRQL_NOT_LESS_OR_EQUAL BSOD Vista

  I have a Vista computer and get the BSOD, and then stops. It happens in safe mode as well

  Here is some information I found in the dump file

  Ntkrnlpa.exe ntkrnlpa.exe + 2b83c 0x81c12000 0x81fcc000 0x003ba000 0x513a901f 08/03/2013 9:27:59 PM system Microsoft® Windows® NT Kernel operating system & 5.1.2600.6368 (xpsp_sp3_gdr.130307 - 0422) Microsoft Corporation C:\WINDOWS\system32\ntkrnlpa.exe
  RASPPTP.sys raspptp.sys + cc84 x 0 82397000 0x823ab000 0 x 00014000 0 x 47919112 01/19/2008 1:56:34 AM Microsoft® Windows® Operating System - to - Peer Tunneling Protocol 5.1.2600.5512 (xpsp.080413 - 0852) Microsoft Corporation C:\WINDOWS\system32\drivers\raspptp.sys

  Tracy

  These have been associated with raspptp.sys - to-Peer Tunneling Protocol of Microsoft Corporation, but the underlying cause is Symantec I think.  I would like to remove and replace with MSE

  Symantec is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER
  http://us.Norton.com/support/kb/web_view.jsp?wv_type=public_web&docURL=20080710133834EN

  Use it to Norton 360 http://Symantec.pcperformancetools.com/Norton-360-how-to-uninstall.html 

  http://www.Microsoft.com/security_essentials/

• Many BSOD - Vista-64 bit

  Hello members,

  Under Vista and several BSOD.

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.0.6002.2.2.0.768.3
  Locale ID: 1033

  More information about the problem:
  BCCode: 7f
  BCP1: 0000000000000008
  BCP2: 0000000080050031
  BCP3: 00000000000006F8
  BCP4: FFFFF80002072BD0
  OS version: 6_0_6002
  Service Pack: 2_0
  Product: 768_1

  Thank you, kattails

  We need the DMP file because it contains the single record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
  You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.
  If you are overclocking stop.  (chances are if you are unsure if you are, you are not) a
  To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".  We need at least 2 FILES DMP to diagnose and confirm
  
  The procedure:
  * Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
  * Zip up the copy.
  * Join ZIP archive to your message by using the button (attachments) "trombone". (if available on your site, MS has this)
  * Please download to a service like Skydrive or "Rapidshare" to share files and put a link to them in your answer.

  Link to find out how to download below.
  http://www.WikiHow.com/use-SkyDrive

  
  To ensure the minidumps are enabled:
  * Click Start, in the search box, type: sysdm.cpl, press ENTER.
  * On the Advanced tab, click Startup and recovery... Settings button.
  * Make sure that automatically restart is unchecked.
  * Under the writing debugging information header, select image partial memory (256 KB) in the list box drop-down (varies from 256kb).
  * Ensure to that small Dump Directory is listed as % systemroot%\Minidump.
  * OK your way out.
  * Reboot if changes have been made.
  
  Please also run MSinfo32 and download the output as well.
  To run MSinfo32 please go to start > run > MSinfo32
  Go to 'file', 'save' and download the PDF is saved with the DMP
  (Instructions for XP, Vista, Win 7, Win 8)

  System specs are often useful so include everything you know

  The Zigzag3143.com team

• BSOD error: "Stop: 0 x 00008086 (0 x 00000301, 0x000001c8, 0 x 00000002, 0 x 00000000).

  I get the BSOD when I boot Windows Vista from my Lenovo T61. The error is "Stop: 0 x 00008086 (0 x 00000301, 0x000001c8, 0 x 00000002, 0 x 00000000). Another user posted on this same error, but received only a generic response from BSOD. DOEA really knows the exact HW / SW issues this error and how to fix? Thank you!

  It can help to look at the files minidump against accidents with a debugger.

  Can you zip the minidump in the C:\Windows\Minidump folder files and (provide link) available via Windows Live SkyDrive or similar site?

  The following link has information about the use of Windows Live SkyDrive:

  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  If you have problems to compress the minidump files copy the minidump files to another location such as a folder on the desktop

  In addition, you do not necessarily have compress the minidump files, you can download one at a time.

• Windows (Vista) stop way unexpectedly in the middle of sessions and caused the problem would BlueScreen. Here are more details: OS Version: 6.0.6002.2.2.0.768.3

  Frequent unexpected stops in the middle of sessions.  Problem event name is BlueScreen.  This problem is related to the Service Pack 2.0.

  Hi Mir,

  1. do you get an error with the Blue Screen Error of death (BSOD) code?
  2. When you get this error message?

  I suggest you to follow the steps and check if it helps.

  Method 1: Follow the steps in the link and check if that helps.
  http://support.Microsoft.com/kb/958233

  Method 2: You can also check out the link and check if it helps.
  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Note: This link is also applicable to Windows Vista.

  Method 3: Check related error in the observer of events and after return.

  http://Windows.Microsoft.com/en-us/Windows7/open-Event-Viewer

• BSOD Vista ataport.sys

  So I ran computer in safe mode because the normal mode does not work.

  Can not turn on microsoft security databases.

  The screen displays this error.

  STOP: 0X0000008E (0XC000005, 0X85F9EA65)

  ataport.sys address 85F9EA65 base at 85f9aooo.

  Any help will be apreciated.

  Hello

  Maybe this might help you:

  http://www.pchelpforum.com/win-7-Vista-BSOD/103587-blue-screen-death-ataport-sys.html

  Start with your Win Vista DVD and access to the command prompt and type (press enter on each line):

  c:
  Bootrec /fixmbr
  Bootrec /fixboot

  LC

• Satellite A300 - Vista stopped loading of Firefox, Chrome, and Word

  Hello
  I just finished backup my laptop and suddnely Firefox, chrome stopped and Word.
  I don't know if there is a link between them, but they all stopped.
  I use toshiba a300 with 32-bit windows visa.

  Thanks for your help.

  Hello

  There is no connection between all of these applications.
  Mentioned work as stand-alone software apps and each software can be uninstalled and installed separately.
  I think you need to uninstall these software and after having cleaned the Vista using CCleaner (freeware software) install the software again.

  Good luck