question of BSOD 0x3B

Similar Questions

• HP spectrum x 360 G1 H9W43EA: Question random BSOD HP spectrum x 360

  Nice day
  
  A few weeks ago my laptop had against accidental damage to the display. I immediately sent it in repairs to ensure IT Services in South Africa, they're a HP authorized repair center. They sent me a quote asserting that the RAM is faulty as well. What I gather from their bill after repairs, is that they have replaced the unit mother and display. So I took home, turn it on, 5 minutes later BSOD. It happens randomly and often now. I can't update to win 10. Before you send them, I never had problems.

  The laptop is still under warranty.
  
  I tried a full factory reset without success. Doesn't a scan of the memory with memtest86, it found no problem. I ran sfc/scannow and it found some corrupted files and fixed them but to no avail. I downloaded BlueSreenView and checked, google and tried some fixes, but all without success. Windows Update also bugs out. I uninstalled the AV, always of BSOD. I reinstalled a different AV, still BSOD.
  
  I think they may have given me a faulty motherboard, or somewhere, some drivers are broken.
  
  I transferred my Logs file found at: C\Windows\Logs to https://files.fm/u/r4wzfqhp

  I will send you my details teamview if you want to be as kind to help, however, the laptop any time BSOD.
  
  Thank you

  Hey

  Thanks for your reply.

  After much more research on Google I tried to analyze the event log which led me to believe that my computer had cancer. Random errors for a lot of things. Opening of my task scheduler has given a face full of error messages telling me that each task no longer exists.

  Finally, I tried a full recovery and redefinition of disc.

  This does not, gives me an error related to the FeatureByte of the motherboard.

  Turns out the technician who installed it has not changed the specific FeatureByte of motherboard in the BIOS of the new motherboard than the old motherboard they replaced. This led to both windows and my recovery is irrevocably corrupted disk (unless of course I changed the FeatureByte myself but it seems that you have need of the soul of a thousand children and owner HP EEPROM, programming material).

  I fixed that by completely reinstalling my windows with an old drive that I had to hang out (ISO, rufus, boot USB... image) and redownloading all of my HP drivers. Unfortunately I now don't have a recovery on my SSD partition, but it's a nuisance, with that I am ready to implement.

  I hope someone reads this and helps them solve the same problem.

  See you soon

• Phone L40 (PSL43E) Pro - upgrade to Windows 7 Vista Basic

  Hello

  I was throughout the forums and have not really found the answers I was looking for.

  I did a new install of Windows 7 on my L40 but I get questions with bsod, random blocks etc so I thought it was time I did something. When I did the installation initially he wasn't any official Windows 7 drivers download (which I see now there).

  I was wondering if someone had made the trip from Vista Basic to Pro 7?
  And if so if you upgrade the BIOS (like updating the BIOS description States it is for Windows Vista only?) and if there is anything that I might need to know (as I see that a few people have been complinaing to post the update of the dead motherboard?).

  Also, the expression "Value package" keeps popping up on the forum, I can see that there is a download of Windows 7 for this although the description to download again claims that it is for use with Windows Vista only?

  I'll be happy to write to the top a complete race for future reference is that I could get a few more "confirmed" information

  Any help would be appreciated.

  Hello

  To be honest I m L40 not owner but I installed Windows 7 on my old Win XP laptop and it works even if Windows 7 was not official published for this device.

  Usually nothing should be wrong, that you can download here the VAP for Win 7, which was released for other series of mobile most recent. The VAP does not depend on the series notebook its compatible with all models.

  There are also a lot of users in the Satellite L forum which has installed Win 7 on the L40 and it works correctly.

• Firefox hangs (?.) BSOD) (/ questions/971282)

  For this last month that my computer has been lock up intermittently during the night. I traced the
  Firefox worm 26 problem. Sometimes the cursor will slow down and then freeze while using Firefox. The computer is completely enclosed and necessary for a hard reset. I installed the latest beta 27. Now, Firefox crashes for the BSOD. I need to resolve this problem quickly. There are questions killer deal with all other browsers, but they all work and do not freeze.
  Windows 7 64 bit
  8G memory
  256 GB, 1 TB HD SS system disc
  Intel Q9950
  MB GIGABYTE.

  Blue screen crashes are rare and usually require an incompatibility with driver graphics card. Launch Firefox in its Safe Mode and disable hardware acceleration.

  Hold down the SHIFT key when you start Firefox

  In the small dialog box that appears, click on 'Start mode safe' (not Reset)

  The orange open Firefox button (or Tools menu) > Options > advanced

  In the mini ' General' tab, uncheck the box for "use hardware acceleration when available.

  While you are in the settings view, disable all non-essential or unrecognized modules on these two tabs:

  Firefox orange (or the Tools menu) button > addons > Plugins category
  
  Firefox orange (or the Tools menu) button > addons > Extensions category

  Typically, a link will appear above at least an extension disabled to restart Firefox. You can complete your work on the tab and click one of the links in the last step.

• Random BSOD win32k.sys 0x3b

  Hello!

  Bought a new computer and installed Win7 64. I do not get on a BSOD a week and it seems to be completely random when it happens. So far, I tested with memtest86, Furmark and chkdsk without error.

  You can find the dump files 3 here:

  https://www.dropbox.com/sh/7vt2ruxojpqn3hc/DKvxcxqbSG

  I've updated the drivers video (Beta, nothing more recent), chipset drivers and installet SP1 without result.

  Let me know if you need more information.

  Much appreciated!

  Hello

  All attached files of the DMP are bug check SYSTEM_SERVICE_EXCEPTION (3B) .

  This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  
  This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.

  Bugcheck 3B, {c0000005, fffff96000144283, fffff8800b1a0020, 0}

  5: kd > fffff96000144283 ln
  (fffff960'001441e0)   win32k! HmgLockEx + 0xa3 |  (fffff960'0014432 c) win32k! RGNOBJ::vSet

  The exception is produced in win32k! HmgLockEx.

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

  1. AsIO.sys is listed and loaded which is Asus PC Probe / AI Suite. Please uninstall all software of Asus/bloatware as soon as POSSIBLE.

  2. make sure you have the latest video card drivers. If you are already on the latest graphics card drivers, uninstall and install a version or a few versions behind the last to make sure this isn't a last number one driver. If you have already experienced with the driver of the card later and earlier versions, please try the driver beta for your card.

  3 if you're still crashing after all the above, please run Memtest for no. LESS than ~ 8 going on (several hours):

  Memtest86 +:

  Download Memtest86 + here:

  http://www.memtest.org/

  Which should I download?

  You can either download the ISO pre-built you want to burn to a CD and then boot from the CD, or you can download the automatic installer of the USB. What this will do is format your USB drive, make a boot device and then install the necessary files. Both do the same job, it's just you that you choose, or you have available (be it CD or USB).

  Note that some older generation motherboards do not support USB boot, your only option is CD (or floppy if you really wanted to).

  How Memtest works:

  Memtest86 writes a series of test patterns for most of the addresses of memory, reads the written data and compares it to find errors.

  The default pass is 9 different tests, varying in the modes of access and test data. A tenth test, bland, is selectable in the menu. He wrote all the memory with zeros, then sleeps 90 minutes before checking to see if the bits have changed (perhaps because of refresh problems). This is repeated with all those for a total time of 3 hours by pass.

  Many chipsets can report RAM speed and timings by SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclockee, Memtest86 can test that memory is free of error with these faster settings.

  Some hardware is able to report the status of the "PAT" (PAT: active or PAT: disabled). This is a reference to the Intel performance acceleration technology; There may be the BIOS settings that affect this aspect of memory synchronization.

  This information, if it is available for the program, can be displayed via a menu option.

  Other questions, they can most likely be answered by reading this excellent guide here:

  http://Forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

  Kind regards

  Patrick

• Satellite S50t-B block - question BSOD

  Hello world. Portable fairly new (purchased a renovated version of manufacturing a month ago) which has recently been crashing in a really weird way, when you play Dota 2. No BSOD or anything, just straight down. What usually happens is that I start the game, enter the gameplay (former title screen loading etc.), 25-30 minutes in the game and it crashes.

  The strange thing is that it happens only under certain conditions. The setting of the battery must be set to high performance and the charger must be plugged. Accidents never happen when the machine is running on battery alone.

  I downloaded the event log if it helps (crash 41 s are the unexpected stops)Admin.zip

  Looks like it's overheating. Try to remove the dust from the vent using compressed air.

• Question on fix BSOD

  Hello, a few months ago that I posted that on an approved portable Skype which even comes with Skype, update to version 6.16 caused immediate BSOD hangs at startup of Skype. In addition to the fact that it is ridiculous, how one program (one that is developed by a team of Microsoft, who) can cause an error that is gushing enough to cause an error of kerner, it is also not possible to disable auto-update notifications.

  He had already taken place I clicked update instead of close, and it becomes boring majorly.

  I would like to ask what is the status of a fix for this.

  If you use a Compaq/HP computer, try to go through the Microsoft drivers following instructions provided by HP to solve the problems of webcam:

  http://community.Skype.com/T5/Windows-desktop-client/BSOD-on-startup-and-installation/m-p/3561465/hi...

• Questions of Compaq Presario CQ60 with restore settings factory, sticked on a blue screen (BSOD, no)

  Hello, I have to get my usual laptop fixed, so I decided to get out of my Presario CQ60, which I have not used in 4-5 years. The operating system is Windows Vista Basic and I want to perform a restore factory settings (I don't mind losing the data on it) and upgrade to Windows 7 Home Premium. So far I tried to do a restore to factory settings by pressing F11 several times to start, and I get to a screen that says "Windows loading files", which leads to a black screen. After what seems like a long time, a blue screen appears where I have control of my cursor (not the Blue Screen of Death) and nothing has changed since. I will update with any changes, because things seem to happen after letting it go for a while, but for now any suggestions on what to do? Let me know if I've left out any information. Thank you!

  Hello

  We can not help you with this problem of factory settings.

  Press F11 at STARTUP is the method that HP plans to use.

  http://h10025.www1.HP.com/ewfrf/wc/document?cc=us&LC=en&DLC=en&docName=c00809678#n405

  1. Turn off the computer if it is not already turned off.
  2. Disconnect any external devices such as printers, USB drives and memory cards.
  3. Turn on the computer and immediately press the F11 key several times , about once a second, until the Recovery Manager opens.
  4. In the Recovery Manager welcome screen, click Next .
  5. On the Microsoft System Restore screen, select No , and then click Next .
  6. On the System Recovery screen, select Yes , and then click Next to continue the recovery process.

  etc.

  And that is the recovery Partition and the process which they installed during the manufacturing process, not Microsoft HP

  You will need to contact HP or ask questions in the forums to Support HP about this problem.

  http://h30434.www3.HP.com/

  @@@@@@@@@@@@@@@@@@@@@@@@

  And I don't think that it will be suitable for the upgrade to Windows 7 Home Premium as being Vista Basic, the material it will not suitable or sufficient to run Windows 7 properly and I have no idea if HP even wrote Windows 7 drivers for it.

  Before you buy Windows 7 after Vista fixed:

  Go to your computer / computer laptop manufacturer Web site and see if Windows 7 drivers are available for your make and model computer / laptop.

  If this is not available, Windows 7 will not properly work for you.

  Run the "Windows 7 Upgrade Advisor.

  http://www.Microsoft.com/en-US/Download/details.aspx?ID=20

  Check if your specifications are compatible for Windows 7:

  "Windows 7 system requirements"

  http://Windows.Microsoft.com/en-us/Windows7/products/system-requirements

  "Windows 7 Compatibility Center" for software and hardware:

  http://www.Microsoft.com/Windows/compatibility/Windows-7/en-us/default.aspx

  Windows 7 upgrade paths:

  http://TechNet.Microsoft.com/en-us/library/dd772579 (v = ws.10) .aspx

  «Installation and reinstallation of Windows 7»

  http://Windows.Microsoft.com/en-us/Windows7/installing-and-reinstalling-Windows-7

  See you soon.

• Question BSOD

  Greetings,

  I had problems with the sudden appearance of BSOD. They occur every week or so. I checked on the BSOD search wiki article and resolve, but I don't have the knowledge of how to say with certainty what is causing my problems. For this reason I ask helpful and well-informed community members to try to help me with my problem.

  OneDrive link with the required files: https://onedrive.live.com/?authkey=%21AJUdqylc60Lf4oc&id=B55EDF1286CEA183%21264&cid=B55EDF1286CEA183

  I will be really grateful for your help!

  Best regards

  Kristian

  Your video driver is the cause of the crash.

  First remove the other oldest:

  AMD clean uninstall utility - AMD.com

  Restart and

  Install the most recent on the manufacturer's Web site, I can give you if you want to specify the make and model (I could not decode the language of the information system)

• Sudden BSoD. Kernel Power event 41 task 63. And other questions...

  While many may be called from a previous thread, I have made, my monitor that's happened wobbly with will power during the boot. I have not solved this issue, by the by, but think it's time for a new monitor.

  However, today when I went to go do something else while leaving the start the computer to the top, I came back and (while the screen was still ongoing and disable this monitor because), I noticed he had a BSoD. I couldn't read anything on this screen because of the screen, so I restarted the computer (what makes the monitor stop acting in place). Entered the event viewer and had found it to be an event 41 task 63. Whatever it may be. So that's what I see in the critical error XML view:

  -

  -

   

    41

    2

    1

    63

    0

    0 x 8000000000000002

   

    153812

   

   

    System

    Xenomic

   

   

  -

    0

    0 x 0

    0 x 0

    0 x 0

    0 x 0

    fake

    0

   

   

  I don't know what it means at all, but what I'm collecting, event 41 is related to the PSU? But if it is the power supply, what block of POWER of the MONITOR (which I guess would be the problem as the monitor was going to power he has) or power supply of the current COMPUTER (which I really hope is not the case)? Or is it something else entirely?

  In addition to all this, I noticed that everytime I start the computer and run Core Temp to check the temperature, I often find it starts at about 50-60 degrees and rest around there until some good long minutes (about 20-40 minutes) before it comes down to temperatures that are easier to manage (30-40 degrees). I guess that's just the Tower need ventilated, but that would be linked to the sudden BSoD on boot to the top?

  Hello

  Thanks for posting your query in Microsoft Community.

  The problem may be caused for various reasons and to diagnose the problem, we can try the following methods and check.

  Method 1: Start the computer Safe Mode and check if the problem persists. If the problem does not persist in safemode, turn on your computer in a clean boot state and check.

  Step 1: Start the computer in Safe Mode

  Safe mode is an option of troubleshooting for Windows that starts your computer in a limited State. Only basic files and drivers needed to run Windows are started. The words Safe Mode appear in the corners of your monitor to identify which Windows mode you are using.

  Please refer to: start your computer in safe mode

  Step 2: Perform a clean boot in order to avoid any conflict of third party software.

  To help resolve the error and other messages, you can start Windows by using a minimal set of drivers and startup programs. This type of boot is known as a "clean boot". A clean boot helps eliminate software conflicts.

  Place your system in the clean boot state helps determine if third-party applications or startup items are causing the problem. You must follow the steps in the article mentioned below to perform a clean boot.

  How to perform a clean boot in Windows

  Note: see 'How do I reset the computer to start normally after a boot minimum troubleshooting' to reset the computer starts normally after troubleshooting.

  Method 2: Please refer to the article below and try the advice given to solve the problem.

  Resolve stop (blue screen) error in Windows 7

  Hope this information is useful. Please feel free to answer in the case where you are facing in the future other problems with Windows.

• Windows 7 BSOD ntoskrnl.exe question

  Hello.  I'm having the same problem as the next person - http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/ntoskrnlexe-1040b-e58d2-6d5be/ea3a3e93-69bd-47c7-9f31-ddb723120912.  I ran Driver Verifier and then encountered the problem of not being able to access my laptop normally.  I disabled the driver verifier now.

  I redid my laptop about 3 times in the hope of solving my BSOD problem, but it is ongoing.

  Any help is appreciated.

  David Martinez

  THE

  They are related to your video driver.  I would like to begin by updating to the latest driver that yours is ~ 1 year.

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

  Loading dump file [C:\Users\Ken\Desktop\052814-20592-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol of validation of the path summary *.
  Location of response time (ms)
  Deferred SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Symbol search path is: SRV * H:\symbols* http://msdl.microsoft.com/download/symbols
  Executable search path is:
  Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  By: 7601.18409.amd64fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0xfffff800'02e63000 PsLoadedModuleList = 0xfffff800'030 was 6890
  The debugging session: 14:44:02.483 Wed 28 may 2014 (UTC - 04:00)
  System Uptime: 0 days 0:02:46.482
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ..................................................
  Loading user symbols
  Loading unloaded module list
  ....
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  BugCheck C4, {c0, fffffa800a546340, f6, fffff8800f2b9879}

  WARNING: Unable to verify timestamp for nvlddmkm.sys
  ERROR: Module load completed but symbols can be loaded for nvlddmkm.sys
  Probably caused by: nvlddmkm.sys (nvlddmkm + 9a 879)

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

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

  DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
  A device driver attempting to corrupt the system has taken.  It comes
  because the driver was specified in the registry as being suspect (by the)
  Administrator) and the kernel has allowed substantial control of this driver.
  If the pilot attempts to corrupt the system, looking for bugs, 0xC4, 0xC1, and 0xA
  Be one of the most commonly seen crashes.
  Arguments:
  Arg1: 00000000000000f6, handle user SEO as the core.
  Arg2: 00000000000000c 0, the value of Handle referenced.
  Arg3: fffffa800a546340, address of the current process.
  Arg4: fffff8800f2b9879, address inside the pilot making the incorrect reference.

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

  BUGCHECK_STR: 0xc4_f6

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

  Nom_processus: rundll32.exe

  CURRENT_IRQL: 0

  ANALYSIS_VERSION: 6.3.9600.17029 (debuggers (dbg). 140219-1702) amd64fre

  LAST_CONTROL_TRANSFER: from fffff800033654ec to fffff80002ed8bc0

  STACK_TEXT:
  "" fffff880 ' 0 c 315308 fffff800 ' 033654ec: 00000000 ' 000000 c 4 00000000' 000000f6 00000000'000000 c 0 fffffa80 ' a 0, 546340: nt! KeBugCheckEx
  "" fffff880 ' 0 c 315310 fffff800 ' 0337abf4: 00000000 ' 000000 c 0 fffffa80 ' 0a 546340 00000000'00000004 fffff880'0 c 317000: nt! VerifierBugCheckIfAppropriate + 0x3c
  fffff880 ' 0 c 315350 fffff800' 03132890: fffff8a0 '000016-0 fffff880' 0c3155a0 fffff880 '0 c 315700 fffff880' 0c 315930: nt! VfCheckUserHandle + 0x1b4
  "fffff880 ' 0 c 315430 fffff800 ' 031a95b5: 00000000 '00000000 fffff880' 00000001 fffffa80 '06067f30 fffff8a0' 05c08a00: nt! : NNGAKEGL: 'string' + 0x2027e
  "fffff880 ' 0 c 315500 fffff800 ' 02ed7e53: fffffa80 '0aa1e060 fffff880' 0c3158b8 00000000'00000002 00000000'00000000: nt! NtQueryValueKey + 0 x 115
  "" fffff880 ' 0 c 315690 fffff800 ' 02ed4410: fffff800 ' 03369 d 96 fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928: nt! KiSystemServiceCopyEnd + 0x13
  fffff880 '0 c 315898 fffff800' 03369d 96: fffff880 ' 0f2b9879 fffff880 '0 c 315930 fffff880' 0c 315928 fffff800 ' 02ed4410: nt! KiServiceLinkage
  "fffff880 '0c3158a0 fffff880' 0f2b9879: fffff880 ' 0c3168ca fffff880 ' 0 c 315970 fffff880 ' 0c3168b8 fffffa80 ' 0591ff18: nt! VfZwQueryValueKey + 0 x 76
  fffff880 '0c3158f0 fffff880' 0c3168ca: fffff880' 0591ff18 fffff880 '0c3168b8 fffffa80' 0 c 315970 00000000 00000000': nvlddmkm + 0x9a879
  fffff880'0c3158f8 fffff880'0 c 315970: fffff880 '0c3168b8 fffffa80' 0591ff18 00000000 00000000' fffff880 0'c 315920: 0xfffff880'0c3168ca
  "fffff880 ' 0 c 315900 fffff880 ' 0c3168b8: fffffa80'0591ff18 00000000 00000000' fffff880 ' 0 c 315920 fffff980' 00000000: 0xfffff880'0 c 315970
  "fffff880 ' 0 c 315908 fffffa80 ' 0591ff18: 00000000 '00000000 '0c 315920 fffff980'00000000 00000000 fffff880' 000000 c 0: 0xfffff880'0c3168b8
  fffff880'0 c 315910 00000000 00000000': fffff880 '0 c 315920 fffff980' c 0 00000000 00000000'000000 ' 00280026 fffffa80: 0xfffffa80'0591ff18

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  nvlddmkm + 9 has 879
  fffff880'0f2b9879 3d340000c0 cmp eax, 0C0000034h

  SYMBOL_STACK_INDEX: 8

  SYMBOL_NAME: nvlddmkm + 9 has 879

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nvlddmkm

  Nom_image: nvlddmkm.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75

  FAILURE_BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

  BUCKET_ID: X64_0xc4_f6_nvlddmkm + 9 has 879

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:x64_0xc4_f6_nvlddmkm + 9 has 879

  FAILURE_ID_HASH: {0c031110-986a-b405-c565-3ead8c9b6e45}

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

• Windows 7 DMP files included BSOD Please Help!

  For last 1-2 weeks have BSOD on my pc. I reinstalled Windows 7 Home Premium several times. A few days after each re - install Win 7 I start receving BSOD. I formatted my disk, partitions, etc. I just need to solve these BSOD. I've included below DMP and Dump WhoCrashed logs files. In these papers he suggests that my drivers could be the cause of crashes of theses. Let me know what is wrong in the comments below.

  Thank you

  Mike Read

  DMP files:
  https://onedrive.live.com/redir?RESID=40F0655702713F9A%21176

  Data sheet:
  Motherboard:
  -All Series, ASUS, ASUSTeK COMPUTER Inc., Z87.-k.
  CPU:
  -GenuineIntel Intel (r) Core i5 - 4670 K CPU @ 3.40 GHz Intel586
  Graphics card:
  -GeForce GTX 660 ti
  RAM:
  -8 GB company unknown.<-------Ran memtest="" 86="" on="" this="" ram,="" no="">
  Hardrives:
  -C = disk 128 GB SanDisk SSD drive
  -Drive(Gaming/storage) E = TOSHIBA 2 to 7200 RPM 64 MB cache

  WhoCrashed reports:

  Saturday, may 10, 2014 3:55:02 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-5023-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xA (0xFFFFF6FCC8078408, 0xFFFFF80002CE089A, 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.

  Saturday, may 10, 2014 3:36:38 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-10405-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0 x 4211)
  Verification of error code: 0 x 24 (0xFFFFF8800B088068, 0xFFFFF8800B0878C0, 0x1904FB, 0xFFFFF80002DBEB05)
  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, may 10, 2014 3:33:49 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-28782-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 34 (0x55F, 0xFFFFFFFFC0000420, 0 x 0 0 x 0)
  Error: CACHE_MANAGER
  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 problem has occurred in the file system cache manager.
  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.

  Saturday, may 10, 2014 3:29:40 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-5912-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1A (0xFFFFFA800339B0A0, 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.

  Saturday, may 10, 2014 2:49:28 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-54974-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1A (0xFFFFFA80033A5C30, 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.

  Saturday, may 10, 2014 2:40:44 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-8829-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1A (0xFFFFFA8003335C10, 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.

  Saturday, may 10, 2014 2:37:22 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-5506-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ABDAC5, 0xFFFFF88009801810, 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, may 10, 2014 2:32:51 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\050914-7753-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1A (0xFFFFFA8003389BE0, 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.

  Hello

  We have three controls compatible bug:

  MEMORY_MANAGEMENT (1A)

  This indicates that an error occurred serious memory management.

  Error checking 1A, {41790, fffffa800339b0a0, ffff, 0}

  - Parameter 1 of the bug check is 41790 indicating a page table was corrupted.
  

  3: kd > dt nt! _MMPFN fffffa800339b0a0
  + 0 x 000 u1:
  + 0 x 008-u2:
  + 0 x 010 PteAddress: 0xfffff6fb'40000050 _MMPTE
  + 0 x 010 VolatilePteAddress: 0xfffff6fb'40000050 empty
  + lock 0 x 010: 0n1073741904
  + 0 x 010 PteLong: 0xfffff6fb'40000050
  + 0 x 018 u3:
     + 0x01c UsedPageTableEntries: 0xffff
  + 0x01e VaType: 0 ''
  + 0x01f ViewCount: 0 "
  + 0 x 020 OriginalPte: _MMPTE
  + 0 x 020 AweReferenceCount: 0n128
  + 0 x 028 u4:

  UPTE has fallen below zero, which implies usually a driver caused the corruption (or faulty RAM memory).

  System_service_exception (3B)

  This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  
  This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.

  Bugcheck 3B, {c0000005, fffff80002abdac5, fffff88009801810, 0}

  3: kd > fffff80002abdac5 ln
  (fffff800'02abdac5)   nt! ExpInterlockedPopEntrySListFault16 |  (fffff800'02abdad0) nt! ExpInterlockedPopEntrySListEnd16

  The exception is produced in nt! ExpInterlockedPopEntrySListFault16.

  PAGE_FAULT_IN_NONPAGED_AREA (50)

  This indicates that invalid system memory was referenced.

  Bug control 0 x 50 usually occurs after the installation of a faulty hardware or installation failure of material (usually associated with defective RAM, either main memory, L2 RAM or RAM video cache).

  Another common cause is a defective system service installation.

  Antivirus software can also trigger this error, as can a corrupted NTFS volume.

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

  Run Memtest for NO LESS than ~ 8 going on (several hours):

  Memtest86 +:

  Download Memtest86 + here:

  http://www.memtest.org/

  Which should I download?

  You can either download the ISO pre-built you want to burn to a CD and then boot from the CD, or you can download the automatic installer of the USB. What this will do is format your USB drive, make a boot device and then install the necessary files. Both do the same job, it's just you that you choose, or you have available (be it CD or USB).

  Note that some older generation motherboards do not support USB boot, your only option is CD (or floppy if you really wanted to).

  How Memtest works:

  Memtest86 writes a series of test patterns for most of the addresses of memory, reads the written data and compares it to find errors.

  The default pass is 9 different tests, varying in the modes of access and test data. A tenth test, bland, is selectable in the menu. He wrote all the memory with zeros, then sleeps 90 minutes before checking to see if the bits have changed (perhaps because of refresh problems). This is repeated with all those for a total time of 3 hours by pass.

  Many chipsets can report RAM speed and timings by SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclockee, Memtest86 can test that memory is free of error with these faster settings.

  Some hardware is able to report the status of the "PAT" (PAT: active or PAT: disabled). This is a reference to the Intel performance acceleration technology; There may be the BIOS settings that affect this aspect of memory synchronization.

  This information, if it is available for the program, can be displayed via a menu option.

  Other questions, they can most likely be answered by reading this excellent guide here:

  http://Forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

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

• 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

• ZBook 17 G3: G3 Thundberbolt 3 dock of Zbook 17 questions

  Has anyone gotten the 200W 3 Thunderbolt Zbook dock and all managed to make it work?  I recently took delivery (a few months late) and cannot operate.  When I plug it (and I made sure each driver I have is also present on the HP site), I start running in a series of questions.

  • Device Manager indicates an unknown device which is shown with an id of vid_174c & pid_3074, which should be a hub 3074 ASMedia superspeed, but none that I try to get the drivers not installed works for this device.
  • All of the USB ports on the laptop stop responding
  • My connected monitors appear, but in Device Manager, I see two copies of the monitors connected through the dock, and each has an exclamation point that the device drivers are not installed.
  • My ethernet seems to work fine
  • Try to install any sort of updated drivers (found in various places on the web) results ASMedia a BSOD
  • The laptop will be bad shut down or restart with the cable in place.  Forcing a hard stop (power button for several seconds) sometimes results the laptop is able to start and other times it simply crashes to the POST screen.
  • Unplug the docking cable, while the laptop is booted up only shows nothing unplugged.  a reboot is required (usually a hard reboot) to get actually the mobile register that the dock is disconnected.
  • Similarly, sometimes after a restart, the laptop will not register when I plug the dock, unless I have successfully completed a cycle of full restart where the laptop is connected to windows without the dock, and then been rebooted (no hard restart) and connected in a second time.

  My current setup is a proc xeon 64 GB of RAM and the graphics card NVidia M4000M (running in only discreet mode via the BIOS settings).  The only ones I haven't installed drivers are Intel video drivers, because I have disabled hybrid graph.

  I'll add a link to the other thread, which has been more active lately, essentially dealing with the same issues.  In this way, we have at least a place to continue the discussion...

  http://h30434.www3.HP.com/T5/business-notebooks/HP-Zbook-Thunderbolt-3-dock-USB-ports-not-working/TD-p/5613457