BSOD ntsokrnl.exe + 75169?

Similar Questions

• How to fix the driver NTSOKRNL.exe and Atheros?

  I recently installed a clean version of Windows 7 Home Premium 64-bit SP1 and he immediately began to malfunction. I go back to the NTSOKRNL.exe and Athrx.sys drivers who, when they do not work it live with your computer, the cause of a malfunction and crashed to a bluescren. Let's all start, I contacted Microsoft to numerous amounts of time (7 times now) and all that they say to call microsoft and use their premium support that starts at $ 99 (which is out of the question I just don't have the money) I tried to call once and told them abuot the question, but they hung up when I said no. And even once when I contacted an agent via chat to support, and they kept insisting to call and I have to use the subscription for my repaired OS.

  This is quite unacceptable. I have a genuine version of Windows 7, my computer is also is no longer supported by HP, so I can't send it to their challenge because they want to pay $ 300 to do a clean installation using my version of windows 7. I would also like to make a formal complaint against Microsoft to charge customers who own Microsoft Windows and try to get help, but only are rejected due to the fact we have to pay for advanced support. What * is the following. My HP is a HP Pavilion dv7-3065dx that is a model of 2011-2012. Only, his warranty expired a year ago.

  I need help right away, because I can't use my laptop correctly, but also loss of data. For the first 5 attempts they tried to help me solve the problem, but after 5, they say I have to pay, even if Microsoft. I can also afford to use Geek Squad, or any other service to help me with my computer problem. All I want to do is repair Windows 7 without uninstall because it's a bad ISO (I used my friends since HP has no install disks)

  Sinceraly, an unhappy customer, SamGray_427

  Please, generate and download a copy of your information system (MSInfo32) file.

  How to get an information system (NFO) file for diagnosis and troubleshooting.

  https://knowledge.Autodesk.com/support/AutoCAD/troubleshooting/CAAS/sfdcarticles/sfdcarticles/obtaining-a-system-information-file-nfo-for-Diagnostics-and-troubleshooting.html

• BSOD, ntfs.sys and ntsokrnl.exe

  Hello, all.

  I have a user who has had multiple bluescreens than to the end. Initially, it started with the ntfs.sys driver crashing, but quickly turned to the subsequent accidents ntoskrnl. Started about a month apart, now much more frequent. I ran Dell startup diags, who spent all on board. I then updated / replaced every driver/chipset in the system and the BIOS. His current running Windows 7 Enterprise 64 bits in an environment of business and another user is to have what would be similar BSOD, but more specifically the ntfs.sys file. This is the discharge for the accidents. Any direction on where to take this would be greatly appreciated. Thank you!

  Thursday, March 5, 2015 18:55:01 this computer crashed
  crash dump file: C:\WINDOWS\Minidump\030515-11466-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7769A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF800047993D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, March 5, 2015 18:55:01 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: 0x9F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF800047993D0)
  Error: DRIVER_POWER_STATE_FAILURE
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  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, March 3, 2015 11:52:00 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\030315-11216-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7769A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039B4040, 0xFFFFF80000B9C3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, February 20, 2015 7:57:23 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\022015-11902-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8008B34060, 0xFFFFF80000B9C3D8, 0xFFFFFA8004BFDBD0)
  Error: DRIVER_POWER_STATE_FAILURE
  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 driver is in an inconsistent or invalid power state.
  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, February 18, 2015 12:03:26 AM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\021715-8236-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x79D8A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039C8040, 0xFFFFF80000B9C3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  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 17, 2015 11:48:29 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\021715-10374-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x79D8A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF80000B9C3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, January 13, 2015 18:26:12 GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\011315-20451-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x78A8A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039B4660, 0xFFFFF8000478D3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  On Monday, December 8, 2014 6:39:14 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\120814-15459-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0 x 4211)
  Verification of error code: 0 x 24 (0xFFFFF880089ECCE8, 0xFFFFF880089EC540, 0x1904FB, 0xFFFFF880016D21D9)
  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.

  The accident that produced this result is more than a month old, but I think that it always reflects exactly what the origins of the system to blue screen.

  1000009F error checking, {4, 258, fffffa80039b4660, fffff8000478d3d0}

  Failed to load image \SystemRoot\system32\DRIVERS\USA19Hx64.sys, 0n2 error Win32
  WARNING: unable to verify timestamp for USA19Hx64.sys
  ERROR: Module load completed but symbols can be loaded for USA19Hx64.sys
  WARNING: Unable to verify timestamp for win32k.sys
  ERROR: Module load completed but symbols can be loaded for win32k.sys
  Probably caused by: memory_corruption

  Follow-up: memory_corruption

  Loaded symbol image file: USA19Hx64.sys
  Image path: \SystemRoot\system32\DRIVERS\USA19Hx64.sys
  Image name: USA19Hx64.sys
  Timestamp: Thu Oct 30 15:52:45 2007 (47278B8D)

  USA19Hx64.sys, is a part of driver for Keyspan USB Serial Adapter ver: 3.7. Please update the driver, or uninstall the hardware/cable? If you can not.

  Keyspan® products.
  http://www.tripplite.com/LP/Keyspan/

  [Peripheral problem]

  Device PNP_Device_ID Error_Code
  Cisco Systems VPN Adapter for 64-bit Windows ROOT\NET\0000 this device is disabled.

• BSOD - ntoskrnl.exe Critical_process_died 0x000000ef

  Got BSOD problems on windows 2012 R2 server, Viewer bliuescreen points to critical_process_dies - ntpskrnl.exe

  DMP file is linked here https://onedrive.live.com/redir?resid=CE9C8B0A89BD1546! 111 & authkey =! ABWSymb0WgE6tJA & ithint = the file % 2cdmp

  Please notify

  These accidents were related to the corruption of memory (probably caused by a driver).

  Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

  If you are overclocking anything reset by default before running these tests.
  In other words STOP! If you don't know what it means that you're probably not  
  
  
  
  
  1-Driver Verifier (for full instructions, see our wiki here)
  2-Memtest. (You can learn more about running memtest here)

• BSOD ntoskrnl.exe + 72 0x0000009f DRIVER_POWER_STATE_FAILURE has 40

  I almost brand new HP ProBOOK 450 G2 with Windows 7 Enterprise, just noticed today the first Memory Dump, thought then to ask... like the laptop is under warranty... laptop computer is on battery power and the battery is dead so saw the light flashing 'orange' and he got the memory dump and he came down, the battery was finished It happened... but its still not the right way to go then... I have through the app "BlueScreenView" about something, but he could not say exactly... searched thing many error BSOD here in the office, but none had the same error, sharing so if someone is kind enough to help.

  Dump file 050415-21028 - 01.dmp
  Time of the accident 04/05/2015-11:01:32
  Bug Check String DRIVER_POWER_STATE_FAILURE
  Bug check code 0x0000009f
  Parameter 1 00000000'00000003
  Parameter 2 fffffa80'07f37a10
  Parameter 3 fffff800'048943 d 8
  Parameter 4 fffffa80'08da0010
  Caused by the driver Ntoskrnl.exe
  Caused by the address ntoskrnl.exe + 72 has 40

  DMP file: http://1drv.ms/1K9FKRC

  Thanks in advance

  ONE

  This phenomenon was related to rtlane.sys NDIS Driver of Realtek Semiconductor Corporation.  I remove the current driver and install the latest driver available.

• 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
  ---------

• Please help me solve this BSOD ntoskrnl.exe, ntkrnlmp.exe

  Hello

  I have problems with my new computer since I bought it, it started giving problems. Now this BSOD. I am totally frustrated with it. Please help me get rid of this questions.
  Here is the link of the minidump file:
  https://SkyDrive.live.com/redir?RESID=1F218460C89B0917%21114
  I guess that the culprit is wireless driver. With the old version of the wireless driver, I got another BSOD, so I uninstalled and installed the most recent version. Still problem persists.
  With whoCrashed, I found this information:
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  CPU: GenuineIntel Intel (r) Core i7-3610QM CPU @ 2.30 GHz Intel586, level: 6
  8 logical processors, active mask: 255
  RAM: 8469991424 total
  VM: 2147352576, free: 1902690304

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

  Dumps are enabled on your computer.

  Tuesday, December 23, 13 9:36:04 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\122313-27736-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 72680)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
  Error: DRIVER_POWER_STATE_FAILURE
  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 driver is in an inconsistent or invalid power state.
  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, December 23, 13 9:36:04 CEST your computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8007539060, 0xFFFFF80000B9C3D8, 0xFFFFFA800FE606B0)
  Error: DRIVER_POWER_STATE_FAILURE
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  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.

  Please help me. Thanks in advance.

  Apvmz

  This phenomenon was related to the device driver wireless Extensible athrx.sys of Atheros Communications, Inc.  Yours is almost 2 years so not the most recent.

  I would like to re - install the latest driver available

• Different random BSOD, ntoskrnl.exe

  Hello

  I am getting random BSOD in ntoskrnl.exe + 75c00
  Can occur at any time and not necessarily in charge. I tried testing my ram, hard drives to find errors & ran sfc/scannow without error.
  I downloaded the minidumps on skydrive @ https://skydrive.live.com/#cid=539E2424E35481DA&id=539E2424E35481DA%21105
  A big thank you to all those who can help.

  Brett

  Two different causes.  First and foremost your Kaspersky.  I would like to delete and replace it with MSE

  Kaspersky is a common cause of BSOD.

  
  

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

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

  Second is related to keyscrambler.sys KeyScrambler keyboard driver.  I remove if not required or update to the latest if it is.

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

• BSOD ntosrnl.exe

  Hello

  I get the blue screen every time im trying to run the game called no. Mans sky.

  I have very good PC that can handle very good games without problem.

  There is more information

  Thanks in advance :^)

  082916-20014 - 01.dmp

  2016-08-29 23:20:29

  SYSTEM_SERVICE_EXCEPTION

  0x0000003B

  00000000' c0000005

  fffffa80'0676 d 658

  fffff880'0d8edc90

  00000000 00000000'

  Ntoskrnl.exe

  Ntoskrnl.exe + 6f400

  NT kernel & system

  Microsoft® Windows® operating system

  Microsoft Corporation

  6.1.7601.23418 (win7sp1_ldr.160408 - 2045)

  x 64 ntoskrnl.exe + 6f400

  C:\Windows\Minidump\082916-20014-01.dmp

  4

  15

  7601-407-560

  2016-08-29 23:22:02

  Hello

  Bugcheck 3B {c0000005, fffffa8006722658, fffff880109fcc90, 0}

  Probably caused by: ntkrnlmp.exe (nt! KiSystemServiceHandler + 7 c)

  Ntkrnlmp.exe is a component of Windows which means than anything else he has led astray.

  fffff880'048 c 3200 * WARNING: unable to verify timestamp for BHDrvx64.sys
  ERROR: Module load completed but symbols can be loaded for BHDrvx64.sys
  BHDrvx64 + 0xac200

  fffff880'03d532f4 * WARNING: unable to verify timestamp for SRTSP64. SYS
  ERROR: Module load completed but symbols could not be loaded for SRTSP64. SYS
  SRTSP64 + 0X2A2F4

  These two are parts of Norton/Symantec and are the cause, the part of the cause, or help to hide the real cause.

  1. if you need to uninstall Norton/Symantec, then run the removal tool to avoid problems causing remains. Use Windows Defender, which in Windows 8/8.1 and 10 is a complete antivirus. Despite all the hype there WD media has proved to be a superstar in the protection and compatibility.

  Norton Removal Tool
  https://support.Norton.com/SP/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us?product=home&PVID=f-home&version=1

  List of tools to clean/uninstall anti-malware programs
  http://answers.Microsoft.com/en-us/protect/wiki/MSE-protect_start/list-of-anti-malware-product-removal-tools/2bcb53f7-7ab4-4EF9-ab3a-6aebfa322f75

  Uninstallers (removal tools) for common antivirus software
  http://KB.eset.com/esetkb/index?page=content&ID=SOLN146

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

  2. check with Support MSI, their documentation online and drivers, and
  Ask problems known in their forums. Also do the same at Nvidia.
  Updated BIOS, drivers of low level chipset and on-board major and
  separate device drivers (see methods of updating driver below).

  BiosVersion = V10.8
  BiosReleaseDate = 11/12/2014
  SystemManufacturer = MSI
  SystemProductName = MS-7817
  BaseBoardManufacturer = MSI
  BaseBoardProduct = B85M-E45 (MS-7817)
  BaseBoardVersion = 2.0

  Support MSI
  http://www.msi.com/index.php?func=service

  MSI - Downloads (drivers and BIOS)
  http://www.msi.com/index.php?func=downloadindex

  MSI - Forums
  http://Forum-en.msi.com/

  MSI - Service
  http://us.msi.com/index.php?func=service

  MSI - Live Update online
  http://www.msi.com/index.php?func=downloadindex

  MSI - Contacts - USA - North America value
  http://www.msi.com/index.php?func=HTML&name=aboutus

  3. check with Nvidia Support, their drivers and documentation online and ask questions in their forum about known issues. Update the driver and if no video latest don't exist, it may be necessary to return to an older stable version.

  NVIDIA - drivers - use OPTION 1 to manually enter your info driver to get the most recent drivers.
  http://www.nvidia.com/download/index.aspx?lang=en-us

  NVIDIA Support - check with the support that she might be a known issue
  http://www.nvidia.com/page/support.html

  NVIDIA forums - also check for the forums it might be a known issue or others likely to have
  http://forums.nvidia.com/

  4 run memory tests (see below).

  5 use ALL methods in the troubleshooters below if necessary.

  6 after DriverVerifier is run by ALL preceding if necessary to see if it can indicate a
  CAUSE (see DriverVerifier below).

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

  Fix blue screen errors
  http://Windows.Microsoft.com/en-us/Windows-10/troubleshoot-blue-screen-errors

  BCCode: 3B 0x0000003b

  3B is usually a graphic driver (display driver video adapter), other possibilities
  include, but are not limited to programs antivirus/antispyware/security and even
  memory (mapping).

  Try to remove and replace all the memory cards and cables (both ends where possible)-actually delete and replace - not just in the warm (on a PC) and clean the dust bunnies and vents. On a laptop on everything that can be done is to reinstall the memory and clean the vents. (Of course remove ALL power before opening the case).

  BCCode: 3B 0x0000003b<-- read="" this="">
  http://www.faultwire.com/solutions-fatal_error/system-service-exception-0x0000003B-* 1074.html

  
  Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION<-- read="" this="">

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

• Windows 8 unexpected Kernel Mode trap BSOD (ntoskrnl.exe)

  Hello, I got the blue screen that gives me the error code: UNEXPECTED_KERNEL_MODE_TRAP (ntoskrnl.exe). I have had this problem since I got my computer, but it happens that all the other day. I tested my RAM with memtest and everything was good. I also use on all drivers updated. I recently installed "WhoCrashed" hoping to get more information as to what was causing this error. Here's the report;

  Thursday, June 26, 2014 6:31:37 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\062614-28703-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x153FA0)
  Bugcheck code: 0x7F (0 x 8, 0xFFFFF802935ABE70, 0xFFFFF80293592FF0, 0xFFFFF80291C5AB6E)
  Error: UNEXPECTED_KERNEL_MODE_TRAP
  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 Intel CPU generated a trap and the kernel could not catch this trap.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Any help will be much appreciated.

  Thank you

  Ryan

  Ryan

  The DMP was inconclusive pointing to memory.  My gut says it's Symantec.  I would like to do two things.  Run the driver verifier and remove Symantec and use the built in Defender.

  These accidents were related to the corruption of memory (probably caused by a driver).

  Please run these tests to check your memory and find which driver is causing the problem.

  
  

  If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

  
  

  Since then, it is more likely to be a pilot run everything first.

  1-Driver Verifier (for full instructions, see our wiki here)

  
  

  If the auditor does not have the issue we move to it.

  2-Memtest. (You can learn more about running memtest here)

  
  

  If you cannot start after you have enabled the auditor reboot in safe mode

  In Vista & victory (F8)

  When win 8 http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-Windows-8-the-easy-way/

  
  

  Co-written by JMH3143

  .

• BSOD ntoskernel.exe and other things

  So for the 6 last month or two, I suffered from BSOD in windows 8.  I never had these problems under windows 7.  I ran Windows memory for 6-8 hours diagnostic tool without a single error. I have 32 GB of RAM, but problems did not begin to show until the path after that I installed these bars of memory.  in any case

  I had a memory of different errors.  I enclose all my files to dump.  This is probably my last try to fix the BSOD on Windows 8, all in all I love the system, it is fast and great ussually, less the BSOD big kitten... I would maybe go back to Win 7 just because of this.
  System Specs:
  AMD FX 8350 4.0 GHz
  ATI 6970 @ stock
  SSD OCZ Vertex 3 with 1.25 firmware (latest)
  Series of fatality ASROCK 990FX v1.90 BIOS (Latest)
  1 TB Seagate HARD drive
  850 watt XFX PSU
  Eventually, I have noticed that some updates may cause these errors... Whenever the system broke down for me played a game, a lot of times Guild Wars 2, sometimes of the League of legends although rare.
  now to find a way to download files.
  The files are here: https://skydrive.live.com/redir?resid=721D30CA0DCAF2A0! 123 & authkey =! AEzyZpzUF5pzxSk
  I added the dump files in a zip

  Thanks for the update and information. Looks like we found the culprit.

  Kind regards

  Patrick

• Black screen of death - NETIO. SYS and ntoskrnl.exe please help

  (I don't know if this is the right topic)

  Hello community,

  So I bought a new game PC 3 days and I have problems with BSOD I get + 3 times per day and I have no idea systems and things.

  Tell me everything you know aslong it's fixable.

  I checked BlueScreenView and those are addresses in stock:

  NETIO. SYS + 39d3e network subsystem i/o

  Ntoskrnl.exe + 75169 & NT Kernel System

  I have no idea on minidumps, nor how to open them and these things, please explain the problem to him and ask me what to know first.

  Thank you.

  FRozXY

  I would contact the two just to be sure but I think I understand the ram should be replaced and replacement ram shouldn't cancel you guarantee

• Blue Screen iaStor.exe. 0 x 00008086

  original title: BSOD iaStor.exe. 0 x 00008086

  I tried to help a friend with their computer that constantly BSOD with the above error code.  Any suggestions as to what is the cause? This is a major problem? I can send files if necessary dmp.

  http://ojutdq.Bay.livefilestore.com/y1pfeuBD1ybofk64r4eVU9tj4D9RH8QV7gEPgehK64yhDZ62OdQZVSFRAD_9BOMtKnxquf_fF5UKlUyaLrYYf-R1Gio3G2g046E/minidump.zip?download&PSID=1

  Start in safe mode and install the driver here. "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• Several BSOD in an interval of two hours due to 'atikmdag.sys' and NTFS.sys with BlueScreenView

  Hello

  So I have recently reinstalled Windows 7 and I got those BSOD in an interval of two hours. The space between the first and the second was almost an hour and a half and the space between the second, third and fourth was five minutes from each other. I'll post the DMP files for anyone to look at to see what you make of it... I used them for BlueScreenView check and in the two first, I found "tcpip.sys" in the third, I found "NTFS.sys" and the fourth, I found "atikmdag.sys" contributing... I also noticed that one particular exe file appeared in all four defective BSOD "ntoskrnl.exe". Could someone help with this? Another thing I noticed, I don't seem to have problems with Safe Mode with networking.

  The four dump files in RAR herefile.

  I think you have brewing here is conflict between AVAST and Malwabytes Pro. You can have more than one AV product with real-time protection (RTP) real installed.

  Please uninstall Malwarebytes and reinstall the free version without the feature of RTP, or completely uninstall AVAST (preferred) and uninstall and reinstall the full version of Malwarebytes Pro.

  AVAST uninstall utility.

  https://www.avast.com/uninstall-utility

  Note: Regardless of the above, you decide to keep and reinstall, you must upgrade to the latest virus definitions and run a scan completes. Why? Because, as long as the conflict exists on your system, it is less certain that he would have been, with only on AV product installed.

  In addition, please if possible update or uninstall the following drivers:

  xnacc.sys Fri Jul 13 20:01:05 2009 (4A5BCAC1): http://sysnative.com/drivers/driver.php?id=xnacc.sys

  netr28x.sys Wed Feb 25 22:02:09 2009 (A 49, 60631): http://sysnative.com/drivers/driver.php?id=netr28x.sys

  LV302V64 LV302V64. SYS Sat Jul 26 11:09:08 2008 (488B3E14): http://sysnative.com/drivers/driver.php?id=LV302V64.SYS

  LVUSBS64 LVUSBS64.sys Sat Jul 26 11:06:36 2008 (488B3D7C): http://sysnative.com/drivers/driver.php?id=LVUSBS64.sys

  HECIx64.sys my Jul 02 18:14:58 2012 (4FF21D62): http://sysnative.com/drivers/driver.php?id=HECIx64.sys

  It would be certainly beneficial to update your system to the latest service pack (SP1) available if you don't have it already done.

  Steps to take before installing Windows 7 SP1 and Windows Server 2008 R2 SP1 starting from Microsoft Download Center.
  http://support.Microsoft.com/kb/2505743

  Learn how to install Windows 7 Service Pack 1 (SP1).
  http://Windows.Microsoft.com/en-us/Windows7/install-Windows-7-Service-Pack-1

  Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932)
  http://www.Microsoft.com/en-US/Download/details.aspx?ID=5842

  Troubleshoot installation of Service Pack 1 (SP1) for Windows 7 or Windows Server 2008 R2
  http://Windows.Microsoft.com/en-us/Windows7/troubleshoot-problems-installing-Service-Pack