Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030FB150, 0x0, 0xFFFFFFFFFFFFFFFF)

Similar Questions

• Vista error unknown Bugcheck Code: 7th. Parameters = 0xc0000005, 0x1, 0x8dd8dc00, 0x8dd8d8fc

  Laptop runs for about forty minutes and then stop without apparent reason, no matter if a program is running or not. Re-booting detects the error code (see above) and then (wish) automatically restore to a previous restore point, and all is well again until another forty minutes pass and then the whole process repeats.

  I ran a diagnosis, it closed by itself before diagnosis could finish. When I scan to find errors, it freezes at some point, every time and does not end.

  The laptop has been maintained by Dell for overheating and to self-extinguish last summer and I'm afraid that the hardware is damaged. Now I had to re - install Windows Vista and the error analysis never recovered or completed since that time.

  Windows automatically tries to find a solution, but nothing comes. Surely, this error code should be familiar to anyone.

  THX

  Hello

  The error could be the overheating problem that you had previously. Make sure that the device is sufficient
  ventilation now - add a small fan to test and make sure that the vents are disabled.

  This error is usually a driver problem and display adapter (video) driver is the most suspicious if she
  may be others. Antivirus/antispyware/security programs, equipment (heat) and major software problems
  can also cause the error. When you get to the section of the driver to use the Troubleshoot utility my generic
  methods in the next message and then return to the if necessary troubleshooting tool.

  Have you recently added hardware or drivers updated? Don't forget to look in Control Panel - Windows
  Updates to see if all drivers have been updated it. Other donor opportunities include the antivirus/anti-
  spyware/security programs.

  When you get to the pilot and sections of the memory of the troubleshooter check the following message to
  update drivers and memory test and then return to the troubleshooter if necessary.

  BCCode: 7F 0x0000007E

  Cause

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. To interpret it, you must identify which exception has been generated.

  Common exception codes are:

  • 0xc0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation has occurred.

  For a complete list of exception codes, see the Ntstatus.h file located in the directory Inc. of the Microsoft Windows Driver Kit (WDK).

  Solve the problem

  If you do not have to debug this problem, you must use certain basic troubleshooting techniques.

  • Make sure you have enough disk space.
  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
  • Try changing video cards.
  • Check with your hardware vendor for updates to the BIOS.
  • Disable the BIOS memory options such as implementing caching or shading.

  If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2 (the address of the exception) should identify the driver or function that caused the problem.

  If exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was launched with the /nodebug. switch. This problem should occur infrequently. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is booted with the Switch/DEBUG .

  In case of exception code 0 x 80000002, the trap frame provides additional information.

  If you do not know the specific cause of the exception, consider the following questions:

  • Hardware incompatibility. Ensure that any new hardware that is installed is listed in the list of the products tested Microsoft Windows market.
  • Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.

  If a driver is listed by name in the bug check message, disable or remove that driver. Disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, 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 to access the file.

  If the problem is associated with Win32k.sys, the source of the error may be a third-party remote control program. If this software is installed, you can remove the service by starting the computer by using the recovery and then Console by removing the offending system service file.

  Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x7E.

  You can also disable memory cache BIOS may try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

  The error that generates this message may occur after the first reboot during Windows Setup, or after installation is complete. A possible cause of the error is lack of disk space for installation and the system BIOS incompatibilities. For any problems during the installation of Windows that are associated with lack of disk space, reduce the number of files on the hard disk drive target. Search and delete temporary files that you do not have to have, files hidden Internet, application backup files and files saved .chk , which contain fragments of files on disk scans. You can also use an another hard disk drive with more free space for the installation. You can solve the problems of BIOS by upgrading the version of the system BIOS.

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

  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

  Here are a few ways to possibly fix the blue screen issue. If you could give the info from the blue screen that would be
  Help. Such as ITC and 4 others entered at the bottom left. And any other information such as STOP error
  codes 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," collisions
  Displays information on all the "crash" of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

  BlueScreens many are caused by old or damaged drivers, video drivers in particular, but there are other causes.

  You can follow these steps in the Safe Mode if necessary or the command prompt Vista DVD or Options of recovery if your
  system 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, 3rd party keyboard and
  smile, 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 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 - bicycle - Mark Twain said it is good.

• The computer was restarted after a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002a0c0f3, 0xfffff880031b68a8, 0xfffff880031b6100).

  Hello

  Here is the link of minidump:

  https://onedrive.live.com/redir?RESID=7E4C38313AC7A592%21104

  Could someone please analyze and help me with the problem. Please, I beg you! I have to study for my exams and would be very grateful if helped solve this problem as soon as possible.

  Thanks in advance! :)

  Hello

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

  This indicates that a system thread threw an exception who did not catch the error handler.

  Bugcheck 1000007E, {ffffffffc0000005, fffff80002a0c0f3, fffff880031b68a8, fffff880031b6100}

  1 argument specifies an access violation has occurred.

  0: kd > k
  Call child-SP RetAddr site
  fffff880'031b6ae0 fffff880'06862 c 80 nt! ExFreePoolWithTag + 0x43
  fffff880 '031b6b90 fffff880' 06fd27f0 MBAMSwissArmy + 0x7c80
  "fffff880'031b6b98 fffff8a0 ' 02883420 0xfffff880 ' 06fd27f0
  fffff880 '031b6ba0 00000000' 00000001'02883420 0xfffff8a0
  fffff880 '031b6ba8 fffff800' 02a7c5f8 0 x 1
  fffff880'031b6bb0 fffff880'06875 cd 0 nt! ExWorkerQueue + 0 x 58
  fffff880'031b6bb8 fffff880 of it 0685 507 the MBAMSwissArmy + 0x1acd0
  fffff880 '031b6bc0 fffff880' 06fd27f0 MBAMSwissArmy + 0 x 1507
  fffff880'031b6bc8 fffffa80 '068 3060 0xfffff880 d' 06fd27f0
  fffff880 '031b6bd0 fffff800 ' 41724765 0xfffffa80' 068 3060 d
  fffff880'031b6bd8 fffffa80 ' 00000001 0xfffff800' 41724765
  fffff880'031b6be0 fffff880' 0xfffffa80 0'00000001 cd 06875
  fffff880'031b6be8 fffff880'0687805 d MBAMSwissArmy + 0x1acd0
  fffff880 '031b6bf0 00000000' 00000043 MBAMSwissArmy + 0x1d05d
  fffff880'031b6bf8 fffff800'00000000 0 x 43
  fffff880 '031b6c00 fffffa80' 04aaf6e0 0xfffff800'00000000
  fffff880 '031b6c08 fffff880' 00f2377d 0xfffffa80'04aaf6e0
  fffff880 '031b6c10 fffffa80' 036b 1040 Wdf01000! FxWorkItem::WorkItemThunk + 0 x 195
  fffff880 ' 031b6c40 00000000 00000000 of ' 0xfffffa80 ' 036b 1040

  Malwarebytes is the cause of the accident, uninstall ASAP for troubleshooting purposes.

  Kind regards

  Patrick

• BSOD W530 frequently

  W530

  Type - 2441-BQ2

  SN - xxxxx

  SSD - SSDSC2BF240A4L - Driver ver - 1.75.02

  Intel Core I7-3940XM

  16 GB memory

  WIndows 7 Enterprise SP1 64 bit - load Corporate gold

  WhoCrashed are:

  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B80)
  Bugcheck code: 0x19 (0x3, 0xFFFFFA800CCB6340, 0xFFF1FA800CCB6340, 0xFFFFFA800CCB6340)
  Error: BAD_POOL_HEADER

  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x19 (0x3, 0xFFFFFA800CCB6340, 0xFFF1FA800CCB6340, 0xFFFFFA800CCB6340)
  Error: BAD_POOL_HEADER

  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B80)
  Bugcheck code: 0x1A (0xFFFFFA8003716490, 41790, 0 x 0 x 0, 0xFFFF)
  Error: MEMORY_MANAGEMENT

  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B80)
  Bugcheck code: 0x1A (0xFFFFFA8003716430, 41790, 0 x 0 x 0, 0xFFFF)
  Error: MEMORY_MANAGEMENT

  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B80)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CC4F5B, 0x0, 0xFFFFFFFFFFFFFFFF)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"

  This was probably caused by the following module: tcpip.sys (tcpip + 0x5E532)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88001C5E532, 0x0, 0xFFFFFFFFFFFFFFFF)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"

  This was probably caused by the following module: ntfs.sys (Ntfs + 0x1F15)
  Verification of error code: 0 x 24 (0xC08A5, 0 x 0 0 x 0 0 x 0)
  Error: NTFS_FILE_SYSTEM

  Comment to Moderator: Order number deleted to protect members of wrongdoing.

  A ran diags Lenovo memory and found one of the four modules is bad. It is fine if it's the only installed but will not play nice with others. Any place that I use, under the cover on the bottom or the keyboard. STIL under warranty then new module commissioned.

• Need help multiple BSOD

  Hey all,.

  I have several BSOD errors.  I reinstalled win 7 after having a BSOD error different loading windows.  I did the format of the hard drive, so it must be cool.

  I have updated all the drivers, including the BIOS.  Any help is appreciated because I'm banging my head on the wall here :)

  OneDrive .dmp and error logs

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Wednesday, September 17, 2014 21:03:57 this computer crashed
  crash dump file: C:\Windows\Minidump\091714-35646-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA0000, 0xFFFFF80002CBA22B, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, September 17, 2014 21:03:57 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA0000, 0xFFFFF80002CBA22B, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, September 17, 2014 7:58:58 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091714-38984-02.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 18 (0xFFFFFA800A2BA2B0, 0 x 0, 4 x 0, 0xFFFFFFFFFFFFFFFF)
  Error: REFERENCE_BY_POINTER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the reference of an object count is illegal for the current state of the object.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, September 17, 2014 17:26:14 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\091714-58141-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA8000, 0xFFFFFA8008A24BB0, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, September 17, 2014 17:20:10 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\091714-39780-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA0000, 0xFFFFF80002C5622B, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, September 17, 2014 17:16:05 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\091714-38984-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA8000, 0xFFFFFA80081DCBB0, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, September 17, 2014 4:10:54 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091714-36114-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF80002D1236E, 0xFFFFF8A003BCB000, 0x0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  10:35:38 AM GMT on Wednesday, September 17, 2014 crashed your computer
  crash dump file: C:\Windows\Minidump\091714-42837-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFA8000, 0xFFFFFA80080FDBB0, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Not a problem, thanks.

  KMODE_EXCEPTION_NOT_HANDLED (1e)

  This indicates that a kernel-mode program generated an exception which did not catch the error handler.

  Bugcheck 1E, {ffffffffc0000005, fffff80002cba22b, 0, fffa0000}

  0: kd > fffff80002cba22b ln
  (fffff800'02cba1ec)   nt! RtlImageNtHeaderEx + 0x3f |  (fffff800'02 ca 9108) nt! MiDoReplacement

  The exception is produced in nt! RtlImageNtHeaderEx + 0x3f.

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

  1. AppleCharger.sys is listed and charged, which is the driver GIGABYTE on / off Charge. See here for more information - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

  Very annoying software, so please uninstall ASAP!

  2 remove and replace Norton with Microsoft Security Essentials for purposes of troubleshooting temporary, as it is most likely cause conflicts:

  Removal of Norton- https://support.Norton.com/SP/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;JSESSIONID=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&PVID=f-home

  MSE - http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

  3 navigate to services.msc and disable the nVidia Streaming Service card and then restart the computer.

  Kind regards

  Patrick

• Bluescreens sometimes occurs error BUgcheck 1E

  I'm having a problem with a program, Eve Online.

  Sometimes it works fine, but most of the time, it causes my system to blue screen.  It is never something useful in the dumps that I looked through using WhoCrashed.

  I have another problem; my PC flat out REFUSES to do anything about it but the minidumps.  I tried to change it in the advanced system properties and in the registry.  It won't do anything else than the minidumps.

  Hi Noel,

  According to the details given by you, I see you get "KMODE_EXCEPTION_NOT_HANDLED" with Bugcheck code: 0x1E. This error message indicates that an error condition has been detected by the kernel and Windows could not continue running because of this error condition. Please write us with the following details.

  What is the brand and model of your computer?

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

  Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

  http://msdn.Microsoft.com/en-us/library/Windows/hardware/ff557408 (v = vs. 85) .aspx

  Make sure that you have installed the latest drivers from the manufacturer's website.

  Let us know the status of the issue.

• Various blue screen of death windows 7, Asus laptop

  Experts/dear Microsoft community,

  Recently I had some problems with my laptop. I tried reformatting and everything but nothing seems to solve the problem long term, brief (2-3 days)

  My computer crashes (blue screen of death), whenever I play big games online. Games such as Company of Heroes, or Dota 2, etc. If I don't play these games solo (offline) I have no problems. Also all other programs work perfectly.

  I have a feeling that it has to do with my Asus laptop drivers, I tried to update, restore and re - install, but without result.

  To tell you that as the scenario for the crash: I start the game, I log on online, join a game. Then after 20 to 25 minutes of play online with no loss of FPS, it auto-shutsdown the game with absolutely no message, followed with an accident soon after, sometimes immediately.

  Here's the accident report I got the program: Whocrashed

  Look forward to hearing your suggestions.

  Concerning

  computer name: ICRASHEVERYWEEK
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  Material: N61Ja, ASUSTeK Computer Inc..
  CPU: GenuineIntel Intel (r) Core i5 CPU M 430 @ 2.27 GHz Intel586, level: 6
  4 logical processors, active mask: 15
  RAM: 4140355584 total
  VM: 2147352576, free: 1929850880

  --------------------------------------------------------------------------------
  Crash Dump Analysis
  --------------------------------------------------------------------------------

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Friday, November 7, 2014 22:01:49 this computer crashed
  crash dump file: C:\Windows\Minidump\110714-44912-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x5996A0)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, November 7, 2014 22:01:49 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  Bug control description: this bug check indicates that a system thread threw an exception that the error handler did not.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, November 7, 2014 18:29:29 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-17737-01.dmp
  This was probably caused by the following module: athrx.sys (athrx + 0x1C4F76)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005E67F76, 0xFFFFF880035A7438, 0xFFFFF880035A6C90)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\athrx.sys
  product: Atheros CB42/CB43/MB42/MB43 network card driver
  company: Atheros Communications, Inc.
  Description: Atheros Extensible wireless device driver
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
  Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

  Friday, November 7, 2014 18:27:43 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-14570-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x1421E5)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005B4A1E5, 0xFFFFF88003E795E0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION

  Friday, November 7, 2014 6:26:57 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-15194-01.dmp
  This was probably caused by the following module: atikmdag.sys (0xFFFFF88005B20B5B)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF88005B20B5B, 0xFFFFF8A0024CF000, 0x0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. PAGE_FAULT_IN_NONPAGED_AREA

  Friday, November 7, 2014 17:57:41 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\110714-49280-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x899D90)
  Bugcheck code: 0xBE (0x12F9A6860, 0xFFFFF880035BC560, 0xFFFFF880062ACD90, 0xE)
  Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: sounds if a driver attempts to write to a memory segment read-only.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. ATTEMPTED_WRITE_TO_READONLY_MEMORY

  Friday, November 7, 2014 17:55:49 this computer crashed
  crash dump file: C:\Windows\Minidump\110714-16692-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000395AA49, 0xFFFFF8800AB310C0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, November 1, 2014 8:24:12 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110114-17550-01.dmp
  This was probably caused by the following module: rdyboost.sys (rdyboost + 0x2C476)
  Bug check code: 0x1000007E (0x0, 0xFFFFF880035248B8, 0xFFFFFFFFC0000005, 0xFFFFF88003524110)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\rdyboost.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: driver for ReadyBoost
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Saturday, November 1, 2014 8:22:52 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\110114-18142-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, October 15, 2014 9:09:56 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\101514-50856-01.dmp
  This was probably caused by the following module: athrx.sys (athrx + 0xF9D77)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880051BED77, 0xFFFFF880033A7708, 0xFFFFF880033A6F60)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\athrx.sys
  product: Atheros CB42/CB43/MB42/MB43 network card driver
  company: Atheros Communications, Inc.
  Description: Atheros Extensible wireless device driver
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
  Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

  --------------------------------------------------------------------------------
  Conclusion
  --------------------------------------------------------------------------------

  13 dumps were found and analysed. Only 10 are included in this report. 2 third party drivers have been identified to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  athrx.sys (Atheros Extensible, Atheros Communications, Inc. wireless device driver.)
  atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

  If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

  Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  Analysis of Dump 1Crash
  --------------------------------------------------------------------------------

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-17004-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
  Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
  Error: CID_HANDLE_DELETION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug control appears very rarely.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheck + 0x0)
  Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
  Error: CID_HANDLE_DELETION
  Bug control description: this bug control appears very rarely.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 12:15:52 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\101314-17784-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x2EDF95)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003145F95, 0xFFFFF88004650448, 0xFFFFF8800464FCA0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 11:09:34 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-14320-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xA (28, 0 x 2, 0 x 0 x 0, 0xFFFFF80002F21D80)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 2:53:45 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-46987-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0x0, 0x0, 0xFFFFF88002DA2910)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sunday, September 28, 2014 17:57:12 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\092814-16926-01.dmp
  This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0xC0A1)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.
  Google search: Microsoft Corporation KMODE_EXCEPTION_NOT_HANDLED

  Monday, September 22, 2014 6:50:05 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092214-42525-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1A (0xFFFFF780C0000000, 0x1DEE, 0 x 5003, 0x420700003BD8)
  Error: MEMORY_MANAGEMENT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  --------------------------------------------------------------------------------
  Conclusion
  --------------------------------------------------------------------------------

  7 dumps were found and analysed. A third-party driver has been designated to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)

  If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

  Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  PC! PK

  These two were related to the material.  Specifically of the RAM.  Please run memtest

  

• BSOD of ntoskrnl.exe and other issues

  It is a new construction, new CPU/motherboard, etc, have a new video card. Three hard drives are in my system (1 SSD and HDD 2). I don't really know where to start to look at what may be the issue. I thought it was the video card, so I replaced it, but I still get similar questions.

  The BSOD is sporadic and the question doesn't seem to be the same thing every time, but ntoskrnl.exe has developed a couple of times. What are the possible problems that I might have?
  Here's what WhoCrashed said on the more recent accidents:
  Friday, February 8, 2013 4:59:24 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\020713-8751-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x33F79)
  Bugcheck code: 0xA (0xFFFFF88042F698C0, 0xFFFFF80002AD574F, 0x2, 0 x 1)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: Advanced Micro Devices, Inc..
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
  Google search: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL

  Friday, February 8, 2013 4:59:24 AM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0xA (0xFFFFF88042F698C0, 0xFFFFF80002AD574F, 0x2, 0 x 1)
  Error: IRQL_NOT_LESS_OR_EQUAL
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, February 7, 2013 21:41:43 this computer crashed
  crash dump file: C:\Windows\Minidump\020713-8564-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)
  Verification of error code: 0 x 50 (0 x 8, 0xFFFFFFFFFFFFFFFF, 0xFFFFFFFFFFFFFFFF, 0x0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, February 5, 2013 11:53:09 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\020513-9063-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)

  
  Verification of error code: 0 x 50 (0 x 8, 0xFFFFF80006BC3FF6, 0xFFFFF80006BC3FF6, 0 x 2)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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 30, 2013 3:26:32 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012913-9110-01.dmp
  This was probably caused by the following module: dxgkrnl.sys (dxgkrnl + 0 x 2333)
  Bugcheck code: 0xD1 (0xD, 0x301A460, 0x6FD35E33, 0x1)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\dxgkrnl.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics Kernel
  Bug control description: This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Monday, January 28, 2013 10:35:18 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012813-8314-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)
  Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002AE3305, 0xFFFFF8800DEEA090, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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 26, 2013 4:26:54 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012513-9500-01.dmp
  This was probably caused by the following module: hal.dll (hal + 0 x 5472)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\hal.dll
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Hardware Abstraction Layer DLL
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Friday, January 25, 2013 05:35:47 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012413-11622-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0x3B (0xFFFFF80002A91846, 0xFFFFF8800CCB9600, 0xC0000096, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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 23, 2013 05:06:04 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012213-9328-01.dmp
  This was probably caused by the following module: pci.sys (pci + 0x25F1)
  Bugcheck code: 0xA (0 x 4722, 0xFFFFF80002ACEF85, 0 x 2, 0 x 1)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\pci.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Plug-and - Play PCI enumerator
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Dan you have 5 different causes there. May be an indication of Malware.
  To eliminate this possible cause, please download the free version of Malwarebytes.

  Update immediately.
  Do a full scan of the system
  Let us know the results at the end.
  
  http://www.Malwarebytes.org/products

• Some rather illusory BSOD and crashes on windows 7.

  So for the past month I have been doing some strange crashes and BSOD that have been in every sense. I've been on Reddit and impossible to get a solution, I have reformatted, which does not set it. I've been on with the technical support of Microsoft support chat and can not get a definitive answer (they spend hours and a symptom of trouble then send me on my way). Accidents and the BSOD happen a crapton all in one day, it's good for several days, then it's a crapton while a new day. I just assumed it was graphics so I uninstalled and reinstalled. No solution. I assumed it was ram, so I change RAM, using just a single chip, get chips on other computers, including the chip switch is in what location, perform a test of memory, no solution.

  Apart from just BSOD I have therefore also get those pips weird screen that blur the screen and resemble a classic movie scene where a security monitor is hacked. Or sometimes I can be working away and suddenly the computer starts up without ever giving any warning or anything.

  Here are the BSOD logs that I have. He did TONS more than that, but more often it does not really give me a journal later.

  Crash Dump Analysis

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Thursday, October 6, 2016 10:33:43 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: unknown (0xFFFFF80002D38344)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D38344, 0xFFFFF880067AAD40, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error.
  Google search: SYSTEM_SERVICE_EXCEPTION

  Thursday, October 6, 2016 20:18:22 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\100616-25740-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70150)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 3, 2016 17:22:27 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\100316-48391-01.dmp
  This was probably caused by the following module: atikmpag.sys (atikmpag + 0x780C)
  Bug check code: 0 x 116 (0xFFFFF8800490080C, 0xFFFFFA8007F784E0, 0 x 2, 0 x 0)
  Error: VIDEO_TDR_ERROR
  file path: C:\Windows\system32\drivers\atikmpag.sys
  product: AMD driver
  company: Advanced Micro Devices, Inc..
  Description: multi-vendor AMD driver miniport
  Bug control description: This indicates that an attempt to reset display driver and recover a timeout failed.
  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: atikmpag.sys (AMD several suppliers Miniport Driver, Advanced Micro Devices, Inc.).
  Google search: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

  Saturday, September 24, 2016 9:53:06 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092416-62416-01.dmp
  This was probably caused by the following module: atikmpag.sys (atikmpag + 0x780C)
  Bug check code: 0 x 116 (0xFFFFF8800453A80C, 0xFFFFFA800D828010, 0 x 2, 0 x 0)
  Error: VIDEO_TDR_ERROR
  file path: C:\Windows\system32\drivers\atikmpag.sys
  product: AMD driver
  company: Advanced Micro Devices, Inc..
  Description: multi-vendor AMD driver miniport
  Bug control description: This indicates that an attempt to reset display driver and recover a timeout failed.
  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: atikmpag.sys (AMD several suppliers Miniport Driver, Advanced Micro Devices, Inc.).
  Google search: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

  Thursday, September 22, 2016 6:59:12 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092216-29250-01.dmp
  This was probably caused by the following module: tcpip.sys (tcpip + 0x52A73)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  path to the file: C:\Windows\system32\drivers\tcpip.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: driver TCP/IP
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Tuesday, September 20, 2016 17:47:17 this computer crashed
  crash dump file: C:\Windows\Minidump\092016-62213-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x5A88)
  Verification of error code: 0 x 24 (0xFFFFF8800A5E5A48, 0xFFFFF8800A5E52A0, 0x1904FB, 0xFFFFF880012A94E4)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Monday, September 19, 2016 5:38:40 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091916-39905-01.dmp
  This was probably caused by the following module: unknown (0xFFFFF880013E86E4)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error.
  Google search: KMODE_EXCEPTION_NOT_HANDLED

  Hello

  Although there may be other factors at play that video drivers ATI are involved as well
  Check with Support ATI, their drivers and documentation online and ask for their
  Forums about known problems.

  AMD/ATI - assistance and pilot - search
  http://support.AMD.com/us/psearch/pages/psearch.aspx?type=2.4.2&product=2.4.2.3.9&ContentType=GPU+download+detail&OSType=Windows+8+Preview+-+32-bit+Edition&keywords=&items=20

  Download the Catalyst Drivers here
  http://game.AMD.com/us-en/drivers_catalyst.aspx

  ATI - Forums
  http://forums.AMD.com/game/categories.cfm?CATID=260&forumid=11

  ATI - Support and drivers
  http://support.AMD.com/us/pages/AMDSupportHub.aspx

  However, given that you re-installed Windows there must be a hardware or BIOS.
  driver Chipset or other very low level driver problem. So anything you can update and
  use the other methods below.

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

  Resolution in Windows 7 stop errors (blue screen) - has a section because if you
  may or may not start Windows.
  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Vista and Windows 7 updated drivers love then here's how update largest. References to the Vista also apply to Windows 7.

  It's my generic how updates of appropriate driver: (updating the video/display driver and BIOS)

  This utility, it is easy see which versions are loaded: run DriverView - see
  Hide Microsoft drivers - updated those without drain in their names. (Also update BIOS and drivers from the chipset.)

  -Free - DriverView utility displays the list of all device drivers currently loaded on your system. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created the driver and more.
  http://www.NirSoft.NET/utils/DriverView.html

  For drivers, visit manufacturer of emergency system and of the manufacturer of the device that are the most common. Control Panel device - graphics card configuration-manager - note the brand and complete model of your graphics driver - double-click - tab - write version information. Now, click the driver update (this can do nothing as MS is far behind the certification of drivers) - then do a right click - Uninstall - REBOOT it will refresh the driver stack.

  Repeat for network - card (NIC), Wifi network, sound, mouse, and keyboard if 3rd party with their own software and drivers and the other main device drivers you have.

  Now go to the website of the manufacturer of system (Dell, HP, Toshiba as examples) (restoration), then site of the manufacturer of the device (Realtek, Intel, Nvidia, ATI, for example) and get their latest versions. (Review of the BIOS, Chipset and software updates on the site of the manufacturer of the system while there).

  Download - SAVE - go to where you put them - right click - RUN AD ADMIN - REBOOT after each installation.

  Always check in the Device Manager - tab drivers version you install actually shows up. This is because some restore drivers before the most recent is installed (particularly that audio drivers) so install a driver - reboot - check that it is installed and repeat if necessary.

  Repeat to the manufacturers - BTW on device at the DO NOT RUN THEIR SCANNER - manually check by model.

  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

  Installation and update of drivers under Windows 7 (updated drivers manually using the methods above is preferable to ensure that the latest drivers from the manufacturer of system and device manufacturers are located)
  http://www.SevenForums.com/tutorials/43216-installing-updating-drivers-7-a.html

  If you update the drivers manually, then it's a good idea to turn off the pilot facilities in Windows updates, that leaves is to Windows Update, but it will not install the drivers who are generally older and cause problems. If updates offers a new driver and then hide it (right click on it), then go get new ones manually if you wish.

  How to stop Windows 7 automatically install drivers
  http://support.Microsoft.com/kb/2500967

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

  Tests of memory intercept all errors, such as memory do not match (possible even for poles that seem identical) and how faster memory is placed in system behind the slower memory. Also is it better to Exchange also sticks in and out to check for those, even if all the tests of memory do not show a problem.

  To test the RAM here control - run 4 + hours or so.<-- best="">
  www.memtest.org

  For the Windows Memory Diagnostic tool.

  Start - type in the search-> memory box - find top - right click - Memory Diagnostics tool follow RUN AS ADMIN instructions

  Windows Vista: How to scan / test your memory with Windows Vista memory or RAM
  Diagnostic tool
  http://www.shivaranjan.com/2007/11/01/Windows-Vista-how-to-scan-test-your-RAM-or-memory-with-Windows-Vista-memory-diagnostic-tool/

  How to run the diagnostic tool memory in Windows 7
  http://www.SevenForums.com/tutorials/715-memory-diagnostics-tool.html

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

  After doing ALL the updates you canand if the problem persists, run
  DriverVerifier.

  Driver Verifier can help find some BSOD problems:

  Using Driver Verifier to identify issues with Windows drivers for users advanced
  http://support.Microsoft.com/kb/244617

  How to solve the problems of driver in Windows Vista or 7. (8/8.1 and 10)
  are essentially the same).
  http://www.WinVistaClub.com/T79.html

  Using Driver Verifier
  https://msdn.Microsoft.com/en-us/library/Windows/hardware/ff545448%28V=vs.85%29.aspx?f=255&MSPPError=-2147217396

  WINDOWS key + X - RUN - type-> auditor/reset press ENTER to disable

  BlueScreenView lets you know if there is a driver specified in the error message.
  Also check with MyEventViewer when the blue screen.

  If DriverVerifier creates a minidump download and post the link here so that we can
  analyze it.

  I hope this helps.
  --------------------------------------------------------------------------------------------
  Rob Brown - Microsoft MVP<- profile="" -="" windows="" and="" devices="" for="" it :="" bicycle="" -="" mark="" twain="" said="" it="">

• Frequent BSOD and PC freezes - Windows 7

  I have been faced with frequent BSOF and freezes for a few years now.  I reinstalled Windows 7 a couple of times. passed the ID of event several times. update BIOS and drivers hardware and program; and ran many tests, including hardware.   Windows and all programs are completely up to date.

  There is no particular model the breaks down: for some time the BSOD's happened only rarely (once a week or less) and the PC froze more frequently. Lately, the BSOD is back, more recently, several times a day.  In general, it occurs in the morning, the PC works well until the user logs out and logs in after awhile. the problem is repeated then - this was the case for weeks when the PC froze (no BSOD).  Now that the BSOD is more common, it can occur sequentially several times and then not happen for some time.

  I have read on this subject extensively and frequently performs WhoCrashed and WinDbg. I pulled out ready to be shared on SkyDrive MSInfo32 reports as well as the exported file.

  I am a very experienced user who can easily set up and adjust a PC without any difficulty, but I'm not a computer expert and have little equipment and system of profound knowledge. In the various reports, I was see a variety of driver issues, which some I fixed already (video ATI, Symantec), yet the new come (today, it seems, HP printer drivers).  For the most part, the following modules are involved: ntfs.sys, ntoskrnl.exe and ntkrnlmp.exe (and an 'unknown' module, too) by all that there are which is the source of the problems.

  Details of PC are:

  Name of the operating system Microsoft Windows 7 Professional
  Version 6.1.7601 Service Pack 1 Build 7601
  System manufacturer Dell Inc.
  Model Studio XPS 9100 system
  System Type x 64-based PC
  Processor Intel Core i7 CPU X 980 to 3.33 GHz, 3334 Mhz, 6 Lossnay, 12 or logical processors
  BIOS Version/Date Dell Computer Corporation A04, 10/21/2010
  SMBIOS Version 2.6
  Windows directory C:\Windows
  System directory C:\Windows\system32
  Boot Device \Device\HarddiskVolume1
  The local United States
  Hardware Abstraction Layer Version = "6.1.7601.17514".
  Physical memory (RAM) installed 12.0 GB
  12.0 GB total physical memory
  8.05 GB available physical memory
  43.2 GB total virtual memory
  40.0 GB available virtual memory

  This is a pretty powerful machine, but there is no acceleration or other extreme material uses.  It is gently used and is in ideal desktop (running low time, under the supervision of Core Temp).

  The programs are for the most part, the fair standard PC: MS Office 2010, Adobe CS5 Design, Norton Internet Security, EaseUS backup, software to print HP, iTunes, Roxio Easy CD, Firefox and more.  All are completely up to date.
    
  I am including below the exit of WhoCrashed and is happy to share the rest of the information in the hope that someone can help me solve the problem.

  Thank you very much!
  JF

  =========

  Thursday, December 12, 2013 12:41:43 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFFA800D240000, 0xFFFFF80002EC1360, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, December 11, 2013 11:51:44 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\121113-29499-01.dmp
  This was probably caused by the following module: unknown_module_00000000'00000000.sys (Unloaded_Unknown_Module_00000000'00000000 + 0x31ABB8)
  Bugcheck code: 0x7F (0 x 8, 0 80050033, 0x6F8, 0xFFFFF88001435F2A)
  Error: UNEXPECTED_KERNEL_MODE_TRAP
  Bug control description: this bug check indicates that the Intel CPU generated a trap and the kernel could not catch this trap.
  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: unknown_module_00000000'00000000.sys.
  Google search: unknown_module_00000000'00000000.sys UNEXPECTED_KERNEL_MODE_TRAP

  On Tuesday, December 10, 2013 10:17:45 this computer crashed
  crash dump file: C:\Windows\Minidump\121013-46145-01.dmp
  This was probably caused by the following module: symefa64.sys (SYMEFA64 + 0x48F6)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880012868F6, 0xFFFFF8800AE6BA10, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  path: C:\Windows\system32\drivers\NISx64\1501000.012\SYMEFA64. SYS
  product: EPT
  company: Symantec Corporation
  Description: Symantec Extended File Attributes
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: symefa64.sys (Symantec Extended File attributes, Symantec Corporation).
  Google search: Symantec Corporation SYSTEM_SERVICE_EXCEPTION

  On Tuesday, December 10, 2013 18:49:46 this computer crashed
  crash dump file: C:\Windows\Minidump\121013-38625-01.dmp
  This was probably caused by the following module: atikmpag.sys (atikmpag + 0x745C)
  Bug check code: 0 x 116 (0xFFFFF8800B53E45C, 0xFFFFFA8011A4D010, 0 x 2, 0 x 0)
  Error: VIDEO_TDR_ERROR
  file path: C:\Windows\system32\drivers\atikmpag.sys
  product: AMD driver
  company: Advanced Micro Devices, Inc..
  Description: multi-vendor AMD driver miniport
  Bug control description: This indicates that an attempt to reset display driver and recover a timeout failed.
  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: atikmpag.sys (AMD several suppliers Miniport Driver, Advanced Micro Devices, Inc.).
  Google search: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

  On Tuesday, December 10, 2013 11:26:48 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\121013-40217-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0xE29A)
  Bugcheck code: 0xE3 (0xFFFFFA800CE76640, 0xFFFFFA800DE857F0, 0xFFFFFA800DE85730, 0x3)
  Error: RESOURCE_NOT_OWNED
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates that a thread attempted to release a resource, he was not the owner.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Sunday, December 8, 2013 2:55:44 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\120813-39639-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0 x 4688)
  Verification of error code: 0 x 24 (0xFFFFF8800A7E89E8, 0xFFFFF8800A7E8220, 0x1904FB, 0xFFFFF88001467D9C)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Saturday, December 7, 2013 10:11:43 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\120713-41839-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF8800BBF4210, 0 x 0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, November 27, 2013 2:19:37 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\112613-27440-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xA (18, 0 x 2, 0 x 0 x 0, 0xFFFFF80002EB78C7)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, November 16, 2013 3:28:52 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\111513-25708-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003189E61, 0xFFFFF88004005AB0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, October 1, 2013 11:06:55 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\100113-39936-01.dmp
  This was probably caused by the following module: acpi.sys (ACPI + 0x1D30F)
  Bugcheck code: 0xA5 (0x80000000, 0x1000, 0x0, 0x80000000)
  Error: ACPI_BIOS_ERROR
  file path: C:\Windows\system32\drivers\acpi.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: ACPI for NT driver
  Bug control description: this bug check indicates that the BIOS Advanced Configuration and Power Interface (ACPI) computer is not fully compliant with the ACPI specification.
  This is likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Tuesday, August 27, 2013 4:21:11 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\082713-46769-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0 x 148760)
  Bugcheck code: 0x7A (0xFFFFFFFFC0000185, 0x1A83D1860, 0xFFFFF6FC4000AC28, 0xFFFFF88001585760)
  Error: KERNEL_DATA_INPAGE_ERROR
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Conclusion
  12 dumps were found and analysed. 3 third-party drivers have been identified to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  atikmpag.sys (AMD several Miniport Driver, Advanced Micro Devices, Inc. vendors.)
  symefa64.sys (Symantec Extended File attributes, Symantec Corporation)
  unknown_module_00000000'00000000.sys

  [PLEASE NOTE: THE FIRST TWO, SUPRA, HAVE BEEN UPDATED AND REPORTED PROBLEMS HAVE NOT BEEN RETURNED SINCE.]

  If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

  Read the GENERAL WARNINGS for the failures of the system troubleshooting section for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  JF, what you call (connection, has not detected and having to re - connect) sounds exactly like what is the cause. Software imaging and backup are a big problem with external drives that are constantly removed then reconnected because the backup program has trouble communicating with the device when this happens constantly, probably corruption occurs.

  The only thing I can recommend is to remove all of your software backup and using outside on his own for a while. If you fall, you know it's the conflicted backup software once again and you have some shopping to do for a good backup software that will not cause problems.

  -#2001--MS antimalware - failed to update signature

  ^^ This happens sometimes, you have to just manually force updates by the client.

  -#11--disk - "the driver detected a controller on \Device\Harddisk3\DR11 error.

  ^^ Happens when you constantly connect and disconnect a device, even if it's to be ejected properly. Harddisk3\DR11 is probably your external.

  -#2--kernel - EventTracing - "Session"Circular kernel context Logger"was able to start with the following error: 0xC0000035.

  ^^ It may be a few causes, see this thread on technet for troubleshooting.

  -#41 (critical)-"the system has rebooted without stop properly first. "This error can be caused if the system unresponsive, crashed or unexpected power loss.

  ^^, This was caused by the system of freezing rather than close properly.

  Kind regards

  Patrick

• Ntoskrnl.exe BSOD at random

  I get a BSOD caused by ntoskrnl.exe or ntfs.sys, with a lot of different bugs 0x0f and 0x0A 0x01E. I used WhoCrashed to help me find what it was, but in no avai.

  Here at random, take a few minutes to a few hours.
  Here are the logs of WhoCrashed

  Thursday, November 10, 2011 2:48:45 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-26130-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
  Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Thursday, November 10, 2011 2:48:45 AM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
  Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Thursday, November 10, 2011 2:18:09 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-19515-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x212A3)
  Verification of error code: 0 x 24 (0xFFFFF88008DD4708, 0xFFFFF88008DD3F70, 0 x 190477, 0xFFFFF80002EA5C84)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Thursday, November 10, 2011 2:05:19 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-22682-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70590)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, November 9, 2011 11:39:15 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-20638-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0xA (0xFFFFF880029ED988, 0xFFFFF80002D205F1, 0x2, 0x0)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, October 27, 2011 7:49:38 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-25162-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0xD1 (0xFFFFF8808327B1DA, 0xFFFFF880042A41EA, 0x2, 0 x 1)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, October 27, 2011 3:11:46 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102611-21106-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70600)
  Bugcheck code: 0x3B (0xC0000005, 0x1, 0x0, 0xFFFFF88009B94300)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Let me know if I need to download the DPM

  Hello

  Doubt that its windows for millions would have the same questions.

  If you think that your Windows installation disc is damaged, try these as a test.

  This will give you a method to make and install from another disk as a test.

  Windows 7 Enterprise - 90 day trial
  http://TechNet.Microsoft.com/en-us/evalcenter/cc442495.aspx

  They will help make you the ERD that are bootable.

  If you need to repair disks - these help repair Windows not re-install.
  Often an ERD will help you when the recovery disk does not work.

  Download Windows 7 system recovery discs - charge now $9.75 for ISO
  images to make the discs.
  http://NeoSmart.net/blog/2009/Windows-7-system-repair-discs/

  How to create a Windows 7 - free system repair disc
  http://www.SevenForums.com/tutorials/2083-system-repair-disc-create.html

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

  These make it bootable Linux disks with many public services:

  Hiren Boot CD
  http://www.hirensbootcd.org/

  Rescue Kit Trinity
  http://trinityhome.org/home/index.php?wpid=1&front_id=12

  System Rescue CD
  http://www.SysRescCd.org/Main_Page

  Knoppix
  http://www.Knoppix.NET/

  Scan a Windows PC for viruses from a Ubuntu Live CD
  http://www.howtogeek.com/HOWTO/14434/scan-a-Windows-PC-for-viruses-from-a-Ubuntu-Live-CD/

  Use Ubuntu Live CD to backup files from your Windows computer dead
  http://www.howtogeek.com/HOWTO/Windows-Vista/use-Ubuntu-Live-CD-to-backup-files-from-your-dead-Windows-computer

  I hope this helps.

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

• Windows 7 BSOD - ntoskrnl.exe (nt + 0x7F1C0)

  I have this problem since April, 2012

  HP support suggested that I should reinstall windows 7. I did some time at the beginning of August, but the problem persists.
  Help, please! Otherwise, I'll keep change the OS with a Microsoft OS No.
  Here are the dumps:
  (Local) information system
  computer name: RADU-PC
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i5 CPU M 520 @ 2.40 GHz Intel586, level: 6
  4 logical processors, active mask: 15
  RAM: 4145868800 total
  VM: 2147352576, free: 1943330816

  Crash Dump Analysis
  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Sat 29-Sep-12 12:56:36 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-34632-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sat 29-Sep-12 12:56:36 GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: bcm42rly.sys (BCM42RLY + 0 x 1280)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003344E30, 0xFFFFF8800AEE8C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\drivers\bcm42rly.sys
  product: Broadcom iLine10 (TM) PCI network card
  company: Broadcom Corporation
  Description: Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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: bcm42rly.sys (Broadcom iLine10 (TM) PCI network adapter Proxy Protocol Driver, Broadcom Corporation).
  Google search: bcm42rly.sys Broadcom Corporation SYSTEM_SERVICE_EXCEPTION

  Sat 29-Sep-12 12:47:59 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-34772-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003347E30, 0xFFFFF8800BCDCC70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &

  
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sat 29-Sep-12 12:39:07 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092912-35552-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000333CE30, 0xFFFFF88008D9CC70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Fri 28-Sept-12 07:30:24 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092812-35630-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003389E30, 0xFFFFF8800C0C5C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Fri 28-Sept-12 07:20:56 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092812-58531-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003349E30, 0xFFFFF8800ACA9C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Play 27 Sept - 12 22:01:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\092712-21606-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x1A (0xFFFFFA8000532F50, 41790, 0 x 0 x 0, 0xFFFF)
  Error: MEMORY_MANAGEMENT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Play 27 Sept - 12 09:26:28 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092712-30108-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x19 (0 x 22, 0 x 20000000000000, 0x0, 0x0)
  Error: BAD_POOL_HEADER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a pool header is corrupt.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem. This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  The sea 26-Sept-12 07:12:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\092612-19734-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x5A88)
  Verification of error code: 0 x 24 (0xFFFFF8800996BAE8, 0xFFFFF8800996B340, 0x1904FB, 0xFFFFF88001231A74)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Mar 25 - Sep - 12 20:55:48 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092612-22354-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7F1C0)
  Bugcheck code: 0x7A (0xFFFFFFFFC0000005, 0xFFFFFA8004646060, 0x1, 0xFFFFF680000B1000)
  Error: KERNEL_DATA_INPAGE_ERROR
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  The game 20-Sept-12 15:08:27 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092012-53929-01.dmp
  This was probably caused by the following module: win32k.sys (win32k + 0xC6A12)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116A12, 0xFFFFF8800AC5B130, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\win32k.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Multi-User Win32 Driver
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Wednesday, August 7, 12 10:29:53 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\080712-41917-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x71F00)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF8000311445B, 0xFFFFF8A00B2DF000, 0 x 2)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, August 7, 12 10:08:21 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\080712-53305-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x1A50F3)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002DBB0F3, 0xFFFFF880031A18B8, 0xFFFFF880031A1110)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  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.

  If you are overclocking STOP

  You may be able to get the DMP files without crashing by booting in SafeMode (F8) with networking.

  Please follow these instructions to collect data against crashes and upload them here, to your Skydrive or a service such as Rapidshare file sharing.

  http://www.SysNative.com/forums/showthread.php/68-blue-screen-of-death-%28BSOD%29-posting-instructions-Windows-8-7-amp-Vista?p=303&viewfull=1#post303

  http://SysNative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe

  To allow us to help you with symptoms BSOD on your computer, download the contents of your folder "\Windows\Minidump".

  The procedure:

  * Copy the contents of \Windows\Minidump to another location (temporary) somewhere on your machine.
  * Zip up the contents of this folder
  Please, upload to skydrive or a file sharing service and put a link to them in your next post.

  Go to start > search/run > cmd > msinfo32 and include it in the upload

  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.

  http://www.SysNative.com/forums/showthread.php/325-BSODs-but-no-dump-files

  http://www.osronline.com/article.cfm?article=545

  Please also go to start > run > msinfo32 and record the results.  Send it with the DMP files, thank you.

• Blue screen under windows7 64 bit

  Hello.

  I love playing games and watching movies on my computer. but now, when I installed windows 7 XP

  am I just a blue screen when I run a game or a movie, I can look at a time and then I get the blue screen.

  I have used whochrased so I get this:

  Sat 12.12.2009 20:49:52 crashed your computer
  This was probably caused by the following module: ladfdhp2amd64.sys
  Bugcheck code: 0xBE (0x80000001A3E00121, 0xFFFFF880068BD2E0, 0xFFFFF8800446C394, 0xB)
  Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  Empty the file: C:\Windows\Minidump\121209-27814-01.dmp
  file path: C:\Windows\system32\drivers\ladfdhp2amd64.sys
  product: Logitech G35 Headset
  company: Logitech
  Description: filter DPL2/DHP2 driver

  Sat 12.12.2009 18:33:47 crashed your computer
  This was probably caused by the following module: ntoskrnl.exe
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Empty the file: C:\Windows\Minidump\121209-32588-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  Sat 12.12.2009 18:12:29 crashed your computer
  This was probably caused by the following module: usbport.sys
  Bugcheck code: 0xD1 (0 x 0 0 x 2, 0 x 0, 0xFFFFF88003E86B40)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  Empty the file: C:\Windows\Minidump\121209-35474-01.dmp
  file path: C:\Windows\system32\drivers\usbport.sys
  product: Operativsystemet Microsoft® Windows®
  company: Microsoft Corporation
  Description: USB 1.1 & 2.0 portdrivrutin
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  On Fri 11.12.2009 23:36:04 your computer crashed
  This was probably caused by the following module: dxgmms1.sys
  Bugcheck code: 0xD1 (0 x 0, 2 x 2, 0 x 0, 0xFFFFF8800455ADBD)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  Empty the file: C:\Windows\Minidump\121209-27284-01.dmp
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  On Fri 11.12.2009 19:39:53 crashed your computer
  This was probably caused by the following module: dxgmms1.sys
  Bugcheck code: 0xD1 (0 x 2, 0 x 1, 0 x 1, 0xFFFFF8800455AEC4)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  Empty the file: C:\Windows\Minidump\121109-20155-01.dmp
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  On Fri 11.12.2009 16:08:26 crashed your computer
  This was probably caused by the following module: ntoskrnl.exe
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Empty the file: C:\Windows\Minidump\121109-21590-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  On Fri 11.12.2009 15:52:47 crashed your computer
  This was probably caused by the following module: usbport.sys
  Bugcheck code: 0xD1 (0 x 801, 0xFFFFF88003DB953F, 0 x 2, 0 x 1)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  Empty the file: C:\Windows\Minidump\121109-23478-01.dmp
  file path: C:\Windows\system32\drivers\usbport.sys
  product: Operativsystemet Microsoft® Windows®
  company: Microsoft Corporation
  Description: USB 1.1 & 2.0 portdrivrutin
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  On Fri 11.12.2009 15:46:23 crashed your computer
  This was probably caused by the following module: usbaudio.sys
  Verification of error code: 0 x 50 (0x0, 0xFFFFF880010C256B, 0xFFFFFA7FA922EC17, 0 x 7)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\121109-22604-01.dmp
  file path: C:\Windows\system32\drivers\usbaudio.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: USB Audio class driver
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  On Fri 11.12.2009 15:37:56 your computer crashed
  This was probably caused by the following module: c:\windows\system32\drivers\eamon.sys
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800280574B, 0xFFFFF88009579C70, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  Empty the file: C:\Windows\Minidump\121109-23556-01.dmp
  file path: C:\Windows\system32\drivers\eamon.sys
  product: ESET Smart Security
  company: ESET
  Description: Amon monitor

  On Fri 11.12.2009 15:05:41 your computer crashed
  This was probably caused by the following module: material
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002C3E780, 0xFFFFF880069EEA90, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  Empty the file: C:\Windows\Minidump\121109-25880-01.dmp

  14:13:28 on Fri 11.12.2009 crashed your computer
  This was probably caused by the following module: ntoskrnl.exe
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Empty the file: C:\Windows\Minidump\121109-21637-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  The game 10.12.2009 17:55:14 crashed your computer
  This was probably caused by the following module: ladfdhp2amd64.sys
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003A8CD3F, 0xFFFFF88008818B50, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  Empty the file: C:\Windows\Minidump\121009-32853-01.dmp
  file path: C:\Windows\system32\drivers\ladfdhp2amd64.sys
  product: Logitech G35 Headset
  company: Logitech
  Description: filter DPL2/DHP2 driver

  The game 10.12.2009 17:48:48 your computer crashed
  This was probably caused by the following module: mouclass.sys
  Bugcheck code: 0xBE (0x80000001A3E2B121, 0xFFFFF880009B0260, 0xFFFFF880049F025D, 0xA)
  Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  Empty the file: C:\Windows\Minidump\121009-30295-01.dmp
  file path: C:\Windows\system32\drivers\mouclass.sys
  product: Operativsystemet Microsoft® Windows®
  company: Microsoft Corporation
  Description: Musklassdrivrutin
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  The game 10.12.2009 17:44:31 your computer crashed
  This was probably caused by the following module: watchdog.sys
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800197633F, 0xFFFFF880021AF9E0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  Empty the file: C:\Windows\Minidump\121009-29421-01.dmp
  file path: C:\Windows\system32\drivers\watchdog.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: watchdog driver
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  The game 10.12.2009 16:04:27 crashed your computer
  This was probably caused by the following module: ntoskrnl.exe
  Bugcheck code: 0xD1 (0xFFFFF88058050F58, 0xFFFFF88058050F58, 0x2, 0 x 8)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  Empty the file: C:\Windows\Minidump\121009-31168-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  The game 10.12.2009 15:44:39 crashed your computer
  This was probably caused by the following module: mouclass.sys
  Bugcheck code: 0xBE (0x80000001A3EF2121, 0xFFFFF80000BA22C0, 0xFFFFF88003BB22D0, 0xA)
  Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  Empty the file: C:\Windows\Minidump\121009-26691-01.dmp
  file path: C:\Windows\system32\drivers\mouclass.sys
  product: Operativsystemet Microsoft® Windows®
  company: Microsoft Corporation
  Description: Musklassdrivrutin
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  10.12.2009 game 14:55:50 your computer crashed
  This was probably caused by the following module: dxgmms1.sys
  Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFFA800520B810, 0xFFFFF88004542F81, 0x0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  Empty the file: C:\Windows\Minidump\121009-23166-01.dmp
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  10.12.2009 game 14:17:06 your computer crashed
  This was probably caused by the following module: mouclass.sys
  Bugcheck code: 0xBE (0x80000001A3F68121, 0xFFFFF88002F222C0, 0xFFFFF88003BEC2D0, 0xA)
  Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  Empty the file: C:\Windows\Minidump\121009-21621-01.dmp
  file path: C:\Windows\system32\drivers\mouclass.sys
  product: Operativsystemet Microsoft® Windows®
  company: Microsoft Corporation
  Description: Musklassdrivrutin
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  10.12.2009 game 14:06:41 your computer crashed
  This was probably caused by the following module: mouhid.sys
  Bugcheck code: 0xD1 (0 x 110000, 0xFFFFF880044CD8C2, 0 x 2, 0 x 1)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  Empty the file: C:\Windows\Minidump\121009-22854-01.dmp
  file path: C:\Windows\system32\drivers\mouhid.sys
  product: Operativsystemet Microsoft® Windows®
  company: Microsoft Corporation
  Description: Filterdrivrutin for HID-mus
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  We sea 9.12.2009 18:01:21 crashed your computer
  This was probably caused by the following module: hidparse.sys
  Bugcheck code: 0xD1 (0 x 0, 97 x 2, 0 x 1, 0xFFFFF88004E28D42)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  Empty the file: C:\Windows\Minidump\120909-29827-01.dmp
  file path: C:\Windows\system32\drivers\hidparse.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Hid Parsing Library
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  We sea 9.12.2009 14:35:59 your computer crashed
  This was probably caused by the following module: ntoskrnl.exe
  Bug check code: 0 x 101 (0 x 31, 0 x 0, 0xFFFFF88002F63180, 0 x 2)
  Error: CLOCK_WATCHDOG_TIMEOUT
  Empty the file: C:\Windows\Minidump\120909-248259-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system setup may be incorrect, perhaps the culprit may be another driver on your system which cannot be identified at this time.

  I would like an answer so that I can start playing games I watch movies and do not get a blue screen

  I think that the best way to follow this on is to use a test called Driver Verifier tool.

  If the tool detects a problem, your machine will crash again.  If all goes well with this permit, it will allow you to easily identify the bad driver.

  Enable the driver verifier
  (1) open a command prompt
  (2) type "check/standard/all" (without the quotes)
  (3) restart your machine.
  (4) use the computer again, until it breaks down (I hope it will be soon :)

  After the crash & restart, go to safe mode.  http://windowshelp.Microsoft.com/Windows/en-us/help/323ef48f-7b93-4079-a48a-5c58eec904a11033.mspx

  Disable the driver verifier
  (1) open a command prompt
  (2) type "auditor/Reset" (without the quotes)
  (3) restart your machine.

  After that you have broken a few times, copy the minidumps on above mentioned same sharing.

  Thank you
  Mark you want to know if your hardware current & software will work with Windows 7? Click on these links: *Windows 7 Upgrade Advisor * *Windows 7 Compatibility Center*.

• BSOD with error code Bugcheck: 0xD1

  Original title: the dreaded BSOD.

  Hi, finally bite the bullet and ask for help.

  Establish an office a few years back who worked perfectly without any problem, a couple of years, I decided it was time to upgrade and replaced the motherboard, RAM and graphics card with a clean install of Windows 7. He ran very well with some heavy for a week or two games and then the first BSOD came, nothing thought and turned down my graphics settings and tried to play again and then he started blue screening 5 minutes of any game. After many graphics driver reinstall (with driver sweeper), memtest runs and HD check blue screens have continued and I finally gave up on it.

  Fast forward 2 years, I made another attempt on the desktop, 10 hours of updates Windows and updates of pilot followed a complete with MSE analysis and I booted up Fallout New Vegas, the game ran perfectly for 2 days and then blue screens started.

  Help please!

  Processor: AMD Phenom II x 4 955

  RAM: 2x2gb Crucial

  Mobo: Asus M4A785TD-V Evo

  OS: Windows 7 64-bit

  PSU: Corsair CX500

  GPU: Gigabyte Nvidia GTX460

  No overclocking

  Information System

  Minidumps

  DriverView

  WhoCrashed reports

  Friday, April 18, 2014 11:18:08 GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0xAA2A)
  Bugcheck code: 0xD1 (24, 0 x 2, 0 x 0 x 0, 0xFFFFF88004172A2A)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  Bug control description: This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Thursday, April 17, 2014 22:38:20 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\041714-27861-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FABB05, 0xFFFFF88007EB6E30, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware 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, April 17, 2014 22:09:37 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\041714-68921-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 50 (1, 0xFFFFF80002E86E49, 0xFFFFF88006C3D000, 0 x 0 x 0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thank you!

  I would remove the stick that failed and operate the system for a few days.

  Kind regards

  Patrick

• BlueScreen code Bugcheck: 0 x 124

  Bug check code: 0 x 124 (0x0, 0xFFFFFA8004658028, 0xB2000000, 0x5) error: WHEA_UNCORRECTABLE_ERROR

  Hello

  something on the 0 x 124 control bug is here:

  http://msdn.Microsoft.com/en-us/library/ff557321 (v = vs. 85) .aspx

  This bug check indicates that a fatal hardware error occurred. This bug check uses the error provided by the Architecture (Windows Hardware) WHEA error data.

  LC