Predator 17 BSOD repeatedly (IRQL_NOT_LESS_OR_EQUAL)

Similar Questions

• Another BSOD error: IRQL_NOT_LESS_OR_EQUAL

  Hello

  I want to thank you again for my previous question answered and fixed. Apparently, it was the faulty motherboard and I've updated so that now there is no problem with my previous BSOD. Until just now.

  I just got an error at the time when I played in Skyrim. He was going well until all of a sudden the screen went distorted and static with graphic artifacts all over the screen and eventually BSOD with error "IRQL_NOT_LESS_OR_EQUAL" I see myself on this problem happened to me before, but I don't don't know where to start with. This morning I made the backup using Windows backup on my hard drive and yesterday, I upgraded my unit of graphics card from Nvidia GT 440 to ATi Radeon HD 6670 but yet before I did, I uninstalled all of the Nvidia software on my PC before grooving in the new ATi. And I scanned for malware using Malwaresbytes Anti-Malware and F - Secure Internet Security, no infected files or suspicious software at the end of the scan. I hope you guys could understand by taking a peek at my crash dump file. Set in the .zip file contains the dump file and dxdiag report just in case.

  Crash dump file

  A bit of luck with it? I hope that you guys can understand this.

  Thank you!

  To identify what loads when you start using Autoruns (freeware from Microsoft).
  http://TechNet.Microsoft.com/en-us/sysinternals/bb963902

  With Autoruns, you can deselect an item which disables startup, or you can click with the right button on an item, then remove it. If you clear the check box that you can check back for re - activate the element. It is an approach much safer than editing the registry and better than using msconfig.

  Another useful feature of the program is that you can click with the right button on an item and select search online to get information about the selected item.

• Screens BSOD repeated last month - never known

  I downloaded and installed the Debugging Tools for Windows to try to identify the problem - but a lot of data and not enough information (at least for me!).

  Can someone help me to interrogate these debugging/dumps files please?

  Thank you very much.

  The last one was:

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

  Microsoft (R) Windows debug 10.0.10586.567 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\Windows\Minidump\032916-33633-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: srv *.
  Executable search path is:
  Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 7601.19160.amd64fre.win7sp1_gdr.160211 - 0600
  Computer name:
  Kernel base = 0xfffff800'03850000 PsLoadedModuleList = 0xfffff800'03 has 97730
  The debugging session: killed Mar 29 15:42:32.351 2016 (UTC + 01:00)
  System Uptime: 1 day 4:42:48.163
  Loading the kernel symbols
  .

  Press (cdb, ntsd, kd) ctrl-c or ctrl-BREAK (windbg) to drop the charges of symbol that take too much time.
  Run! SYM noisy before .reload to track symbols loading issues.

  ..............................................................
  ................................................................
  .....................................................
  Loading user symbols
  Loading unloaded module list
  .....................................
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Error checking 19, {20, fffffa800ce30930, fffffa800ce30950, 402000}

  WARNING: Unable to verify timestamp for mwac.sys
  ERROR: Module load completed but symbols can be loaded for mwac.sys
  Probably caused by: fwpkclnt.sys (c:\windows\system32\drivers\fwpkclnt! FwpsConstructIpHeaderForTransportPacket0 + 20 (a)

  Follow-up: MachineOwner
  ---------

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

  BAD_POOL_HEADER (19)
  The pool is already damaged at the time of the current request.
  This may or may not be due to the appellant.
  The internal pool links must be traversed to find a possible cause of
  the problem and the pool then special applied to the suspect tags or driver
  Auditor for a suspect driver.
  Arguments:
  Arg1: 0000000000000020, a pool block header size is damaged.
  Arg2: fffffa800ce30930, the pool entry we were looking for on the page.
  Arg3: fffffa800ce30950, the next entry to the pool.
  Arg4: 000000000402000a, (reserved)

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

  DUMP_CLASS: 1

  DUMP_QUALIFIER: 400

  BUILD_VERSION_STRING: 7601.19160.amd64fre.win7sp1_gdr.160211 - 0600

  SYSTEM_MANUFACTURER: Dell Inc.

  SYSTEM_PRODUCT_NAME: OptiPlex 790

  SYSTEM_VERSION: 01

  BIOS_VENDOR: Dell Inc.

  BIOS_VERSION: A18

  BIOS_DATE: 24/09/2013

  BASEBOARD_MANUFACTURER: Dell Inc.

  BASEBOARD_PRODUCT: 0HY9JP

  BASEBOARD_VERSION: A02

  DUMP_TYPE: 2

  BUGCHECK_P1: 20

  BUGCHECK_P2: fffffa800ce30930

  BUGCHECK_P3: fffffa800ce30950

  BUGCHECK_P4: 402000a

  BUGCHECK_STR: 0x19_20

  POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b01100
  Could not get MmSystemRangeStart
  fffffa800ce30930

  CPU_COUNT: 8

  CPU_MHZ: d40

  CPU_VENDOR: GenuineIntel

  CPU_FAMILY: 6

  CPU_MODEL: 2A

  CPU_STEPPING: 7

  CPU_MICROCODE: 6a, 2, 7, 0 (F, M, S, R) GIS: 29'00000000 (cache) 29'00000000 (init)

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

  Nom_processus: mbamservice.ex

  CURRENT_IRQL: 2

  ANALYSIS_SESSION_HOST: DELL-7

  ANALYSIS_SESSION_TIME: 29/03/2016 16:03:23.0647

  ANALYSIS_VERSION: 10.0.10586.567 amd64fre

  LAST_CONTROL_TRANSFER: from fffff800039facae to fffff800038c4080

  STACK_TEXT:
  fffff880 '0b 694168 fffff800' 039facae: 00000000'00000019 00000000'00000020 fffffa80 '0ce30930 fffffa80' 0ce30950: nt! KeBugCheckEx
  fffff880 '0b 694170 fffff880' 02128d2d: 676e7049 fffffa80 00000000'00000008 00000000'00000010 00000000' 142310 d 6: nt! ExDeferredFreePool + 0x12da
  fffff880 '0b 694220 fffff880' 01fb1066: 00000000 00000000' fffff880 '01fad0c3 00000000 00000000' fffffa80' 13b 64250: tcpip! IppInspectBuildHeaders + 0x65d
  fffff880 '0b 694500 fffff880' 08ac012d: 00000000'00000000 00000000'00000014 00000000'00000000 fffffa80 13 cf 1630: c:\windows\system32\drivers\fwpkclnt! FwpsConstructIpHeaderForTransportPacket0 + 0x20a
  fffff880 '0b6945a0 00000000' 00000000: 00000000'00000014 00000000'00000000 fffffa80 13 cf 1630 fffffa80 13 CF 1644: mwac + 0x612d

  STACK_COMMAND: kb

  THREAD_SHA1_HASH_MOD_FUNC: 2647a8884c8b09f064ff759df6d75b2848c3da21

  THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8fcf995ee0f14a68f835dd0cf90d0f79e4bd9785

  THREAD_SHA1_HASH_MOD: d22f46aff69f74919852fff5c04c9e17fb5861c0

  FOLLOWUP_IP:
  c:\windows\system32\drivers\fwpkclnt! FwpsConstructIpHeaderForTransportPacket0 + 20 has
  fffff880'01fb1066 85 c 0 test eax, eax

  FAULT_INSTR_CODE: 2c74c085

  SYMBOL_STACK_INDEX: 3

  SYMBOL_NAME: c:\windows\system32\drivers\fwpkclnt! FwpsConstructIpHeaderForTransportPacket0 + 20 has

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: c:\windows\system32\drivers\fwpkclnt

  Nom_image: fwpkclnt.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 533f5b09

  IMAGE_VERSION: 6.1.7601.18438

  FAILURE_BUCKET_ID: X64_0x19_20_fwpkclnt! FwpsConstructIpHeaderForTransportPacket0 + 20 has

  BUCKET_ID: X64_0x19_20_fwpkclnt! FwpsConstructIpHeaderForTransportPacket0 + 20 has

  PRIMARY_PROBLEM_CLASS: X64_0x19_20_fwpkclnt! FwpsConstructIpHeaderForTransportPacket0 + 20 has

  TARGET_TIME: 2016-03 - 29 T 14: 42:32.000Z

  OSBUILD: 7601

  OSSERVICEPACK: 1000

  SERVICEPACK_NUMBER: 0

  OS_REVISION: 0

  SUITE_MASK: 272

  PRODUCT_TYPE: 1

  OSPLATFORM_TYPE: x 64

  OSNAME: Windows 7

  OSEDITION: Windows 7 Windows NT (Service Pack 1) TerminalServer SingleUserTS

  OS_LOCALE:

  USER_LCID: 0

  OSBUILD_TIMESTAMP: 2016-02-11 17:40:22

  BUILDDATESTAMP_STR: 160211-0600

  BUILDLAB_STR: win7sp1_gdr

  BUILDOSVER_STR: 6.1.7601.19160.amd64fre.win7sp1_gdr.160211 - 0600

  ANALYSIS_SESSION_ELAPSED_TIME: 79E

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:x64_0x19_20_fwpkclnt! fwpsconstructipheaderfortransportpacket0 + 20 has

  FAILURE_ID_HASH: {863e217f-0693-d7a3-6d21-a4c5a3f57698}

  Follow-up: MachineOwner

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

  I think that the problem is resolved.

  Interesting experience. This software has helped me identify TWO sources of software conflict constantly producing the BSOD.

  The software were anti-virus & anti-malware. Incredible.

  BitDefender has been the worst culprit. Absolute nightmare.

  Mawarebytes was also a problem, but at least they released an updated version to remove the bug (if it says the person on it!).

  • I removed the paid version of Bitdefender - and I recommend people to not to touch it with a barge-pole (it was the latest in a long line of ineffective).
  • Update Malwarebytes seems stable.

  I hope this is a help for the next poor soul who must borrow the BSOD way :-)

• BSOD with IRQL_NOT_LESS_OR_EQUAL code

  My boss has been do BSOD almost everyday for the past few weeks.   I checked all of its software and drivers for updates and all have been applied.   He still gets the BSOD, so I copied the minidump files and I need to know what I can do.  Please let me know if I need to include any other system to dump file.   It is on a Lenovo H330 Win 7 Pro 64-bit with all windows updates installed.

  The picture taken here are some of the stop codes displayed if they are of no use:

  0x0000000A (0xFFFFF880C2CA7698, 0 x 0000000000000002, 0xFFFFF80002E977F9)

  AK

  All these between 2013 and today have been associated with your Kaspersky software.  IMHO it is rubbish and should be deleted.  You can use MSE in its place

  Kaspersky is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER.

  http://support.Kaspersky.com/downloads/utils/kavremover10.zip
  http://www.Microsoft.com/security_essentials/

  

• After installing Photoshop CC 2015, when I run, it appears the BSOD with IRQL_NOT_LESS_OR_EQUAL nvlddmkm.sys message.

  Hello everyone,

  my machine configuration is:

  ASUS N56J

  Intel core I7-4710HQ processor

  8 GB RAM

  NVIDIA GEFORCE GTX850M with the latest version of the pilot aired on May 31, 2015.

  Thank you.

  RIccardo

  Hi Riccardo,

  This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.

  A driver tried to access a pageable (or that is completely invalid) address while the IRQL was too high. This bug check is usually caused by drivers who used a wrong address.

  Recommend to boot the machine in safe mode and then try to run Photoshop.

  Please post on the Adobe Forums.

• BSOD repeated in my brand new X 230 (with Windows 8)

  Hello

  I bought the new X 230 in early December and then on vacation (without him) for two weeks. So it's really my first week using it. I've had NINE blue screens of death already, each with the term dpc_watchdog_violation. In addition, my Citrix remote work permit system stops on this computer, making the computer nearly useless for work. I am concerned, it is a lemon - how can I have so many accidents during the first week of use? Below is the summary of crash events. Anyone had similar problems? Did someone had problems with rtwlane.sys on their X230s?

  Thanks for your thoughts and time,

  ML

  Saturday, January 12, 2013 20:41:48 CEST your computer crashed
  crash dump file: C:\windows\Minidump\011213-19546-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Saturday, January 12, 2013 20:41:48 CEST your computer crashed
  crash dump file: C:\windows\memory.dmp
  This was probably caused by the following module: rtwlane.sys (rtwlane + 0xFF204)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\drivers\rtwlane.sys
  product: Realtek PCIEWireless LAN PCI-E NIC
  company: Realtek Semiconductor Corporation
  Description: Realtek PCIE NDIS Driverr
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: rtwlane.sys (Realtek PCIE NDIS Driverr, Realtek Semiconductor Corporation).
  Google search: Realtek Semiconductor Corporation DPC_WATCHDOG_VIOLATION

  Friday, January 11, 2013 20:08:31 CEST your computer crashed
  crash dump file: C:\windows\Minidump\011113-22437-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, January 11, 2013 6:27:07 CEST your computer crashed
  crash dump file: C:\windows\Minidump\011113-20000-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, January 10, 2013 20:25:31 CEST your computer crashed
  crash dump file: C:\windows\Minidump\011013-19296-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, January 10, 2013 20:18:01 CEST your computer crashed
  crash dump file: C:\windows\Minidump\011013-25890-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, January 10, 2013 18:50:59 GMT crashed your computer
  crash dump file: C:\windows\Minidump\011013-26921-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, January 10, 2013 7:01:44 AM GMT crashed your computer
  crash dump file: C:\windows\Minidump\011013-73421-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, January 9, 2013 20:18:40 CEST your computer crashed
  crash dump file: C:\windows\Minidump\010913-17562-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7AD40)
  Bug check code: 0 x 133 (0 x 281, 0 x 280, 0x0, 0x0)
  Error: DPC_WATCHDOG_VIOLATION
  file path: C:\windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: watchdog of the DPC has detected an operation extended to a level IRQL DISPATCH_LEVEL or higher.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem may be due to a thermal problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Hi, MLinBerlin

  I did some research on this topic on the Microsoft Web site and found this page explaining what is a DPC_WATCHDOG_VIOLATION . According to Microsoft, this error is usually caused by hardware or a driver of related material. For this reason, I recommend making sure that all the drivers and BIOS are up-to-date to exclude any reasons for software for this problem. All drivers for your system can be found here. It could possibly be material, but hope that some updates will operate smoothly.

  Good luck and let me know how it goes

  Adam

• Constant BSoD, corrupt files, preventing a Win7 installation, no known recent driver updates

  From 4 days ago, my wife (Vista Home Premium) laptop started BSoD repeatedly.  We have not updated all the drivers recently (but who knows what performed auto-updates).  It restarted 4 times that night and each time it seemed to come as soon as she tried to access any URL in IE or Firefox.  She brought home for me and I had no problem with him in a browser, but the next day, he began to die again.

  Common mistakes are 7th and 8th, and it continues to hang, even after a system restore to a point of recovery two weeks ago (although it took 6 trials to actually restore - BSoD kept killing the process).  Repair of the system does not work either, it crashes, as well.  I remember at least three messages on the BS itself: CACHE_MANAGER and IRQL_NOT_LESS_OR_EQUAL BAD_POOL_HEADER.  I suspect a problem with the map NETWORK, but Windows says its pilots are underway (2008), especially as the most recent accident has been when I tried to connect to my wireless network.

  I was hoping a custom to Win7 Setup would fix it, but it continues to crash during the installation (at different points of the installation, as a bonus).  When trying to install, it is usually said of a file (usually a different each time) is corrupted.  I tried to run windows setup, and also start from the disc, or what allows me to complete the installation.  Is there a way to just reformat the hard disk during the installation as the back with Windows XP?

  Also, can someone tell me why "Contact Microsoft Support" says there is a problem with the ID of the product on the website?  It is said to put it in the right format, but it already is.  If I go back and choose a different product, it recognizes that the product key is wrong for the selected product, but for some reason, it doesn't let me continue to the next step.

  Thank you much for the help!

  Thanks for the answer, it turns out it was a bad stick of RAM.  I finally got to the point where I could boot from my CD of Windows, so I formatted the drive, but I still have bluescreened, so I thought it must be a problem with the hardware at its base.  I pulled one of the sticks and it crashed immediately, if I swapped out and it installed fine.  Thanks again for the interest, morality is to check things easy before going deep into the software!

• Bsod IRQL when you attempt to reinstall Vista

  • Trying to reinstall Vista on a formatted hard drive, I get a BSOD, if I put in the disk of Vista I choose install, etc and get where she asks you which partition you want to use. It then continues to the first of several listed as follows to install Vista first being «analyze"the «...» "to show you that it is doing something more. After a few minutes it freezes and the BSOD error "irql_not_less_or_equal" This could be enough info to help me somehow, or that I have to write the 0x0000... It gives me at the bottom of the BSOD?

  Hello

  Is the drive that you are installing a generic retail Vista disc or one provided by HP? A generic retail disk does not contain the necessary drivers for the HP System.

  IEEE 1394 is commonly known as firewire. This is only a review if you have a firewire port.

  Good luck, Rick Rogers, aka "Crazy" - Microsoft MVP http://mvp.support.microsoft.com Windows help - www.rickrogers.org

• Blue screen Bad Pool Header 0 x 00000019 (0x00000020, 0x89637d90, 0x89637eb8, 0x0a250001)

  original title: BSOD BAD POOL HEADER 0 x 00000019 (0x00000020, 0x89637d90, 0x89637eb8, 0x0a250001)

  Had this BSOD repeatedly after expansion RAM

  Help, please?

  OK, I found the cause of the problem...

  After some research, I noticed that the motherboard has a maximum ceiling. 2 GB so the 4 GB is too...

• Problems with Alienware Aurora R4 Windows 10

  I had strange problems, especially since the update to Windows 10. Sometimes, I have no answer to click on in the lower left corner of Windows icon. Other times, it has a transparent background, etc. I was also at random to make a BSOD with IRQL_NOT_LESS_OR_EQUAL error. Here is a link to the dump file...

  

  I'm under BIOS A11, GTX690, 16 GB ram, i7 - 4820K @ 3.7 GHz. Those who know how to interpret the dump files can point me in the right direction?

  Thank you.

  You will probably get a better response if you re - post it in the forum of the Club of Alienware .

• "Satellite P300D-201: BSOD: irql_not_less_or_equal" and pointer reference

  The first few weeks, I got Windows 7 32 Bit on my Satellite Pro P300D 201, it worked fine. But suddenly, there was a blue screen with the label "reference_by_pointer" I've tried to stop as usual. I have not installed any new software a few days before (just a few updates "Windows Update"). Now this apears blue screen every time I try to stop. Hibernation and energy saving still work.

  But, sometimes when I connect my mobile phone "Sony Ericsson K800i" using the USB connection and the "Sony Ericsson PC Suite 6" it is "irql_not_less_or_equal" blue screen.»

  I don't know if theres something wrong with the RAM/working memory, but I can't think because this computer is brand new and it never fell down or something like that.

  I'm sorry for my bad English, I'm still learning.

  Hello

  Perhaps Windows isn't compatible with your software up-to-date and causing this BSOD. You should try to use the restore system to a previous state.

  Also have you updated the software for your mobile phone? Maybe it's not compatible with Windows 7's again. Visit the site of the factory for an update.
  I have the same phone but I m using MyPhoneExplorer which works quite well on Windows 7 but I m using the Bluetooth connection and not on the cord.

• Hello. I repeated the BSOD is since I've owned this computer. I'm tired of trial and error.

  Hello. I had repeated BSOD (Blue Screen of Death) since I've owned this computer.

  Product: HP TouchSmart 300-1017 PC Desktop

  Product # NY604AA-ABA; [Personal information]

  W7/64.

  "DRIVER_POWER_STATE_FAILURE.

  My last HP support ticket number is 805 154 7061.

  These BSOD occur only when the machine is in

  STANDBY or hibernation,

  NEVER when it is active. NEVER.

  I called support 5 - 6 times and spent hours trying to get the problem solved.

  They took control and made things such as the update of the BIOS, the DL updates, etc., but the problem persists. Then on a reminder 24 hours later, they ask if everything is OK.

  WELL, WHAT * IS * OK UNTIL THE NEXT BSOD.

  These efforts have NO analysis as to what could be the cause of the problem.

  I'm tired of trial and error approaches, involving mainly conjecture.

  I have right to more effort has been to resolve this problem.

  Information about the BSOD settings on the causes of the problem are listed below.

  The code is always "Stop 0x0000009F.» Track dump parameters:

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

  Dump file
  050711-19000 - 01.dmp

  Time of the accident
  07/05/2011 09:47:02

  Bug control chain
  DRIVER_POWER_STATE_FAILURE

  Bug check code
  0x0000009F

  Parameter 1
  00000000'00000003

  Parameter 2
  fffffa80'05c0ca00

  Parameter 3
  fffff800'00ba2748

  Parameter 4
  fffffa80'04472180

  Caused by the driver
  Ntoskrnl.exe

  Caused by address
  Ntoskrnl.exe + 80640

  Description of the file
  NT kernel & system

  Name of the product
  Microsoft® Windows® operating system

  Company
  Microsoft Corporation

  Version of the file
  6.1.7601.17592 (win7sp1_gdr.110408 - 1631)

  Processor
  x 64

  Full path
  C:\Windows\minidump\050711-19000-01.dmp

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

  This requires an ANALYST determine the CAUSE of this recurring problem.

  There may be a solution to the MS Support Article ID: 977186 - "error message when you try to resume a Windows 7-based or Windows Server 2008 R2 computer for.

  "hibernation:" Stop 0x0000009F "

  He said: "to resolve this problem immediately, contact Microsoft Customer Support Services to obtain the fix. For a complete list of the Support Services client Microsoft

  phone numbers and information on the costs involved, see the Microsoft Web site at the following address:
  http://support.Microsoft.com/contactus/?WS=support (http://support.microsoft.com/contactus/?ws=support).

  I think that MS wants to charge a person for download. But I think any charges should be covered by HP, under my support contract.

  I want a permanent solution so that I can keep from losing my job.

  Tom Jones, Burbank, CA

  Ox9F errors are pilot errors.   Often they are solved by updating the graphics driver, but it could be any driver.  Sometimes something wrong in the system can cause a problem to another driver - they can be very difficult to solve.

  I saw a document on the Microsoft Web site that may apply - I might try what it says and see if that makes a difference.   http://support.Microsoft.com/kb/982091

  Also - make sure that you have updated the graphics and TV tuner driver (and everything that needs to be updated) - there were a few difficulties for crashes and blue screens in some of them.

  http://h10025.www1.HP.com/ewfrf/wc/softwareCategory?OS=4063&LC=en&cc=us&DLC=da&sw_lang=&product=4007366#n142

  -DM (an employee of HP long)

• Ntkrnlpa.exe repeated original BSoD problem

  Hi all

  I recently got a laptop Toshiba Satellite by a customer who complained only that he had "taken a turn for the worse. After playing with him for a few minutes, it was not long to bluescreen. What was fascinating, however, is that the system was unable to display anything on the screen when he stopped. There was a little blue at the bottom of the screen and a lot of pixels turn random colors.
  In any case, after rooting around the internet looking for what exactly ntkrnlpa.exe can do to cause a blue screen, I found a forum thread that says a rogue pilot could be the problem and that it is just to show up in the landfill as ntkrnlpa.exe. Remembering the glitches I've seen to every BSoD (except 1), I decided to download and install new graphics drivers. (The card is an ATI Mobility Radeon 3100) After that new drivers have been installed, I rebooted, launched Google Chrome, browsed Internet for a while and was greeted with an another BSoD. To be honest, I don't have never seen anything quite like this since I've been working on computers, and I'm stumped. I have this vague feeling that it may be a problem with the hardware for the following reasons:
  • The machine is from 2006-07.
  • The machine runs very hot even on a granite surface.
  • Even with the new graphics drivers, it cannot correctly display the blue screen error screen.
  Help? Thank you!
   
  EDIT: I can't get files to dump the machine since I'm working on a permissions problem, but I'll put the important information below (from BlueScreenView)

  Crash #1: Bug string control: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

  • Bug check code: 0x1000007e
  • Caused by the driver: ntkrnlpa.exe
  • Plant address: ntkrnlpa.exe + 3e598

  Crash #2: Bug Check String: IRQL_NOT_LESS_OR_EQUAL

  • Bug check code: 0x0000000a
  • Caused by the driver: ntkrnlpa.exe
  • Plant address: ntkrnlpa.exe + 4df99

  Crash #3: Bug Check string: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

  • Bug check code: 0x1000007e
  • Caused by the driver: ntkrnlpa.exe
  • Plant address: ntkrnlpa.exe + 3e598

  Crash #4: Bug Check String: KERNEL_MODE_EXCEPTION_NOT_HANDLED

  • Bug check code: 0x1000008e
  • Caused by the driver: ntkrnlpa.exe
  • Plant address: ntkrnlpa.exe + 23ae21

  Crash #5 (this one is from a different file, but I thought I would include it in any way): Bug Check String: IRQL_NOT_LESS_OR_EQUAL

  • Bug check code: 0x0000000a
  • Caused by the driver: C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS
  • C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS + 17289
   
   
   

  mpzeevi

  Altogether.  I suspect that it's symantec and it is much easier to remove (in most cases).  Some people are adamant about not removing it so I give the possibility of driver verifier.

  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

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

• IRQL_NOT_LESS_OR_EQUAL (Vista BSOD 0x0000000A)

  error 0x0000000A (0x00000002, 0x00000000, 0x9B150300, 0x81C0C11F)

  The machine regularly seems blue screen. Any help?

  Topher-

  Hello

  Check this thread for more information using BlueScreenView, MyEventViewer and other methods
  to troubleshoot the BlueScreens - 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 (such as MediaFire). If you have problems to download the copy of minidumps
  for the office or in the Documents folder and download them from there.

  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: 0a 0x0000000A

  Drivers could be at fault, however the problems of disk or security/antivirus/antispyware products are
  just as likely to be the root cause that they can force a driver to corrupt or go out of bounds.
  The video driver or something affecting it would be questionable.

  At the end of this message, I'll post a bluescreen generic and in the next convenience store
  How do to update the drivers and BIOS but also to check memory message.

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

  BCCode: 0a 0x0000000A

  Cause

  This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high.

  The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

  If you encounter a bug 0xA control during the upgrade to a later version of Windows, this 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.

  Solve the problem

  If a kernel debugger is available, get a stack trace.

  To resolve an error caused by the faulty device driver or service system, BIOS

  1. Restart your computer.
  2. Press F8 to character-based menu that displays the choice of operating system.
  3. In the WindowsAdvanced Options menu, select last known good Configuration . This option is most effective when a pilot or a service is added at a time.

  To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

  1. Check the system log in Event Viewer for error messages that may identify the device or driver that caused the error.
  2. Try disabling the cache in memory of the BIOS.
  3. Run the diagnostics of equipment provided by the manufacturer of the system, in particular the scanner memory. For more information about these procedures, see the manual of your computer.
  4. Make sure that the latest Service Pack is installed.
  5. If your system has cards (SCSI) small computer system interface, contact the card manufacturer for updated Windows drivers. Try to disable sync negotiation in the SCSI BIOS, check the wiring and the SCSI ID of each device and confirming the proper termination.
  6. For devices (IDE) peripheral electronic integrated, set the built-in as only primary IDE port. Also, check each IDE device to the right setting master/slave/stand alone. Try to remove all IDE devices except for the hard drives.

  If the message appears during installation of Windows, make sure that the computer and installed devices are listed in the list of the products tested Microsoft Windows market.

  Comments

  Before upgrading to a new version of Windows, remove all third-party device drivers and system services and disable any antivirus. Contact software manufacturers for updates of these third-party tools.

  BCCode: 0a 0x0000000A<-- read="" this="">
  * 1025.html http://www.faultwire.com/solutions-fatal_error/IRQL-not-less-or-Equal-0x0000000A-

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

  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="">

• Cannot start Vista somehow without BSOD, including Mode without fail & last known--IRQL_NOT_LESS_OR_EQUAL

  I don't know exactly what the cause of the problem, but I have a feeling that it is a driver problem. I don't know why the problem started, I've had a laptop where the monitor came out on this subject so I photographed the hard to VMware, I never started an operating system that has not been installed in native mode via vmware before so I thought there may be errors.

  The first time it booted up it starts normally, the Windows Activation came, although I do not know why I have reactivated, and he says that it needs to restart. I restarted and it said it was installing 10 updates - after the updates done, it restarted and then any startup mode, I choose to get exactly the same problem blue screen of death.

  I searched for hours a reply - all, I access the Startup Repair tool command prompt. I think it's a driver issue, but I don't know how to uninstall the drivers from the command prompt.

  It is vital that I have fix without restoring the system or in a Format that I need all programs intact with their original settings. I probably just need to uninstall all the drivers and install them again.

  Hello

  Best to check also with VMware Support and forums.

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

  There are two Bug_Checks with IRQL_NOT_LESS_OR_EQUAL then its best to specify the BCCode or
  Stop Code. Both are 0 a 0x0000000A and D1 0x000000D1.

  Check this thread for more information on using BlueScreenView, MyEventViewer and other methods of
  Troubleshoot the BlueScreens - top 3 methods (+ 1 other).

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

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

  Drivers could be at fault, however the problems of disk or security/antivirus/antispyware products are
  just as likely to be the root cause that they can force a driver to corrupt or go out of bounds.
  The video driver or something affecting it would be questionable.

  Make sure that BIOS driver low-level chipset and drivers are all updated by checking manually
  system manufacturer and device manufacturers sites.

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

  BCCode: 0a 0x0000000A

  Cause

  This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high.

  The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

  If you encounter a bug 0xA control during the upgrade to a later version of Windows, this 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.

  Solve the problem

  If a kernel debugger is available, get a stack trace.

  To resolve an error caused by the faulty device driver or service system, BIOS

  1. Restart your computer.
  2. Press F8 to character-based menu that displays the choice of operating system.
  3. In the WindowsAdvanced Options menu, select last known good Configuration . This option is most effective when a pilot or a service is added at a time.

  To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

  1. Check the system log in Event Viewer for error messages that may identify the device or driver that caused the error.
  2. Try disabling the cache in memory of the BIOS.
  3. Run the diagnostics of equipment provided by the manufacturer of the system, in particular the scanner memory. For more information about these procedures, see the manual of your computer.
  4. Make sure that the latest Service Pack is installed.
  5. If your system has cards (SCSI) small computer system interface, contact the card manufacturer for updated Windows drivers. Try to disable sync negotiation in the SCSI BIOS, check the wiring and the SCSI ID of each device and confirming the proper termination.
  6. For devices (IDE) peripheral electronic integrated, set the built-in as only primary IDE port. Also, check each IDE device to the right setting master/slave/stand alone. Try to remove all IDE devices except for the hard drives.

  If the message appears during installation of Windows, make sure that the computer and installed devices are listed in the list of the products tested Microsoft Windows market.

  Comments

  Before upgrading to a new version of Windows, remove all third-party device drivers and system services and disable any antivirus. Contact software manufacturers for updates of these third-party tools.

  BCCode: 0a 0x0000000A<-- read="" this="">
  * 1025.html http://www.faultwire.com/solutions-fatal_error/IRQL-not-less-or-Equal-0x0000000A-

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

  If there is any RAID drivers they are very suspicious and/or drivers problems are very real prospects.
  Other possibilities are video and other drivers. Refer to the section of driver in my credits
  methods of troubleshooting blue screen below. BIOS, drivers low level chipset, memory and
  antispyway/antivirus/security programs can also cause this. Check the resolution of problems and when
  you get the pilot section refer to generic methods in next message and return to
  the troubleshooter if necessary.

  BCCode: D1 0x000000D1

  Cause

  A driver tried to access a pageable (or that is completely invalid) address while the IRQL was too high.

  This bug check is usually caused by drivers who used a wrong address.

  If the first parameter has the same value as the fourth parameter, and the third parameter indicates a runtime operation, this bug check was probably caused by a driver who was trying to run code when the code itself has been paginated outside. The possible causes for the error page are:

  • The function was marked as pageable and was operating at an IRQL higher (including obtaining a lock).
  • The function call was made to a function in another pilot, and that this driver has been unloaded.
  • The function was called by using a function pointer that was an invalid pointer.

  BCCode: d1 0x000000d1<-- read="" this="">
  * 1210.html? order = votes http://www.faultwire.com/solutions-fatal_error/Driver-IRQL-not-less-or-Equal-0x000000D1-

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

  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 "crashes and displays the information about all crashes in one
  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 and happy holidays!

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.