BSOD caused by the discache.sys driver

Similar Questions

• Problems caused by the nviddmkm.sys driver

  My computer turns off because of the file nviddmkm.sys (this according to my performance report). The nviddmkm.sys driver has been recently updated, and the problem with my computer began at this time.  I am running Windows 7 64 bit on my computer and don't know how to solve this problem.  How can I uninstall the driver and install one that will work properly?

  Assuming that it is the graphics drivers-
  It seems that the updates of Windows was allowed to update your graphics drivers.
  (the machine does not stop is rare however).
  It is better to setup Windows updates so it does not automatically install from the
  "optional" updates without your approval.
  Never use updates to Windows for graphics drivers in particular and also avoid a recent
  'optional' Update - KB 2670838 - as this will stop some (mostly older) games to launch
  If you are not connected to the internet.

  Download Nvidia drivers from the link below - use only the WHQL.  I suggest using
  the 310,90 vs the newer version, at least for now.
  If your computer is a DELL, HP, etc., it is sometimes better to get the drivers on their website
  for your model of PC.

  NVIDIA Driver Downloads - advanced search

  -In before to install the new drivers uninstall all components of the graphics Nividia
  drivers, including - PhysX, audio HD, 3D and updater - via programs and features.
  -Restart the computer before installing the new drivers.
  -If you continue to have problems doing the same thing again, but after restarting execution pilot Fusion to
  clean leftovers Nvidia graphics driver files.
  -Reboot again before installing the new driver.

  Treexy external page

  .

• 0x0000003b SYSTEM_SERVICE_EXCEPTION caused by the win32k.sys driver BSOD

  Hello

  I used Windows 7 earlier there were many BSOD so I downgraded to Win XP about 6 months back since he could not join the homegroup to another win 7 PC in my house so I decided to again installed Windows 7 after updating my BIOS. However Im getting BSOD even though less frequent than it would have been without update bios (I used to get BSODs during installation of win 7 before the update).

  

  I do not use any IEEE 1394 device.

  Details of my Pc:

  1 "AMD E350" APU + 'GPU AMD HD 6310' integrated

  2-4 GB of RAM

  3. Windows 7 Ultimate x 64

  4 MTS MBlaze ultra Modem

  Kindly help, I can't keep on using Windows XP!

  Kindly let me know if anything else it takes to help me with this.

  Hello

  Thanks for the update on the issue. I recommend you to download and install all the latest drivers from the manufacturer's Web site. As this problem generally arises because of the drivers.

  You can see the following link to visit the website of MSI support.

  http://www.msi.com/service/download/

  Hope this information helps.

• BSOD caused by NETIO. SYS

  Hi all

  I am running Windows 7 on a laptop Samsung series 7 NP700Z5A-S0AUS. Recently I've been making a large number of BSOD (as much as two or three a day) that appear to be caused by the netio.sys driver. You can download the most recent dump of my computer here file: https://dl.dropboxusercontent.com/u/488076/Blue%20Screen%20Dump.dmp
  I'm good with instructions and I am happy to provide any additional info, you may need. Any help will be greatly appreciated!
  Kind regards
  Jacob

  Hello

  For netio.sys errors updated network driver (NIC) and wireless (WiFi) drivers from the
  Site of the manufacturer of system/motherboard if embedded and the sites of manufacturers of real devices if they are separated
  devices. Check also for the update of the BIOS and the low level chipset drivers

• Cannot boot safe mode or any mode - hangs on the mup.sys driver

  Can someone help me. I did some research on the internet and see that it is a familiar problem. I have been using a usb and someone removed without doing safely - storage key my laptop then froze and the only thing I could do was turn it off at the power button.

  Now I can't do anything - it just goes to several times on the same page saying that there was a problem to choose a way to start - I chose alone and nothing - it loads until the mup.sys driver and then just goes to the same page again. I'm out of ideas.

  Can anyone help?
  I'm trying to avoid the recovery disk that I really want to lose my job yet, but realize that might have to happen, you mind I read reports that it even still hangs when you try this option.

  Thanks Rachel

  Hello

  AFAIK the mup.sys is placed in the folder C:\Windows\System32\drivers and it s responsible for the control and the start-up of the operation of the system at the lower level (control of the printer or the graphics card, etc.).

  If your computer loads all the way up to mup.sys then your HARD drive should work. If he died it would not even charge anything at all. It would not even try to load this file.
  It is likely that this file is corrupted just.

  If you re not able to run the Win operating system and use the System Restore tool, so I put t see any other possibility to use the Toshiba Recovery CD.
  To save important files, you can remove the laptop HARD drive and connect the HARD drive to another computer via the USB interface.

• Can someone send me the VMkbd.sys file?

  Hello everyone,

  I had problems with VMware Player v4 upgrade and only as a last resort, I had to do a manual uninstall to version 3.1.4. Unfortunately for me, I deleted by mistake the VMkbd.sys driver and now my machine works just fine but will not accept any keyboard input. Currently locked by the login screen Windows original (no keyboard, no password) and the local firewall is blocking the RDP, I would try to restore this file before reinstalling Windows.

  Can someone please be so kind and tell me how to get a copy of the file v3.1.4 VMkbd.sys VMware Player for Windows XP 32-bit?

  Thank you all for your help.

  try to extract the vmplayer - setup.exe

  start the installation with the parameter /e tempdir download

  You can find the file in tempdir then

• BSOD occurs when the inserted SD card. FASTFAT. SYS crashes.

  I have it happens almost everytime if the machine has been used for a while. Insertion of an SD (4 GB format Canon) a BSOD is virtually guaranteed. After a new start it works fine but disastrous otherwise since all the info is lost and nothing is closed.

  I watched the dump file and the FASTFAT. SYS is the cause of the accident. It is a very old driver in Windows 7 and there are several problems with it in many forums that goes back even to XP. There is no plant introduced by any other device or USB key/drive connected. Only the SD card.

  I thought that this may have be due to the USB controller is off for economy of energy, but even after the removal of capacity by enabling / disabling not to turn it off to save power to USB devices, that it always crashed the very next time I used what was days later. The system was that it is usually plugged.

  I can do the same thing on my old laptop with its internal player of multicast running Windows 7 32 bit, and there is no problem. The Thinkpad with Win 7 64 bit. I am always aware of a BSOD occurring dare I plug my camera card. This makes the port useless since I can't afford regular crashes and an external card reader may have to be used.

  After considerable effort and reload the drivers. I found the driver for the series 6.x installed version and not the version number that Lenovo States on the package information. By comparing the file SYS of two pilots in effect is the same, including the version number. In the end, I got the last being installed, but it is not what says Lenovo.

  Also, since all this time number uninstall anyway, I was able to force it to take. The SD card is no more crash the system. I used it several times since the announcement, then all the time before putting it together. It looks like all that fixes something, somewhere, somehow without rational reason for BSOD crashes.

• Blue screen BSOD caused by mrxsmb.sys or ntoskml.exe or l1c62x64.sys?

  Hello

  I frequently have some BSOD and after analysis with Whocrashed, there were 15 BSOD. See belong

  But I can't find where the problem:

  Mrxsmb.sys: I noticed that there are a lot of this file on my computer in C:\Windows\system32\drivers (27/04/2011 04:40 - 154Ko) as well as in several starting directory by C:\windows\winsxs\amd64_microsoft* different date & time, but the same size. There is also a variant of like mrxsmb10.sys and mrxsmb20.sys file.

  I read that this may be due to a malware. What do you think about this?

  l1c2x64.sys: I've already checked the driver and the driver is already uptodate on the website of the manufacturer of the computer.

  Ntoskrnl.exe: this is a file of the kernel and I prefer not to change anything...

  My laptop is a Lenovo G500s Win7 pro 64-bit

  Thank you for your help

  Monday, February 16, 2015 11:48:49 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\021615-22729-01.dmp
  This was probably caused by the following module: mrxsmb.sys (mrxsmb + 0x42C9)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 20016, 7, 0xFFFFFA800C973170)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\drivers\mrxsmb.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Windows NT SMB Minirdr
  Bug control description: This indicates that the current thread is doing a bad pool request.
  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, February 16, 2015 11:48:49 GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: l1c62x64.sys (L1C62x64 + 0x84A6)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 20016, 7, 0xFFFFFA800C973170)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\drivers\l1c62x64.sys
  product: series Qualcomm Atheros Ar81xx PCI-E Gigabit Ethernet Controller
  company: Qualcomm Atheros Co., Ltd..
  Description: Qualcomm Atheros Ar81xx series PCI-E Gigabit Ethernet Controller
  Bug control description: This indicates that the current thread is doing a bad pool request.
  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: l1c62x64.sys (series of Qualcomm Atheros Ar81xx PCI - E Gigabit Ethernet Controller, Qualcomm Atheros Co., Ltd.).
  Google search: Qualcomm Atheros Co., Ltd. BAD_POOL_CALLER

  Saturday, February 14, 2015 15:34:19 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\021415-18876-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x74EC0)
  Bug check code: 0xC5 (0 x 2, 0 x 0, 0xFFFFF6800008E332, 0xFFFFF800037BDB15)
  Error: DRIVER_CORRUPTED_EXPOOL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the system attempted to access invalid memory at IRQL level too high.
  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.

  Friday, February 13, 2015 12:09:20 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\021315-19359-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x74EC0)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030005, 7, 0xFFFFFA800DF82A30)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the current thread is doing a bad pool request.
  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, January 20, 2015 12:00:23 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012015-21418-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030008, 7, 0xFFFFFA800CDBF260)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the current thread is doing a bad pool request.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sunday, January 18, 2015 15:55:30 GMT your computer crashed
  crash dump file: C:\Windows\Minidump\011815-24304-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bugcheck code: 0x19 (0 x 22, 0 x 80000, 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.

  Saturday, January 17, 2015 15:19:45 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\011715-32463-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bug check code: 0xC5 (0 x 2, 0 x 0, 0x5FFF2, 0xFFFFF8000380C9BF)
  Error: DRIVER_CORRUPTED_EXPOOL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the system attempted to access invalid memory at IRQL level too high.
  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.

  Monday, June 1, 2015 11:56:22 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\010615-31902-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Verification of error code: 0 x 50 (0 x 1, 0xFFFFF800037F82F2, 0xFFFFF8E0033429BC, 0 x 5)
  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, December 16, 2014 12:01:14 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\121614-26956-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030008, 7, 0xFFFFFA800D29FE20)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the current thread is doing a bad pool request.
  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 16, 2014 11:49:21 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\121614-30716-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xC2 (0 x 0x109B, 0 x 4030008, 7, 0xFFFFFA800D1BE090)
  Error: BAD_POOL_CALLER
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that the current thread is doing a bad pool request.
  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.

  Lammens

  I told you, that crashed was incorrect.  9 of them have been associated with your TplinkUDSMBus.sys 3 years and more

  (Print server relationship is a function built into your router. It allows you to share your printer with computers connected to the router of KCODES COMPANY) the driver information may or may not be correct but your must be removed or if you absolutely need it updated to a version

  

• Recurrent BSODS even after the repair facility. Hardware failure? Driver conflict? Help, please!

  I was troubleshooting my BSOD for about a week and I need help.

  Here's where I am. I cleaned the chassis and reinstall all components. Then I ran memtest for 8 passes without error. Then I got Majorgeeks through my dieting rigorous anti-malware. And there is no malware on the computer.  I could not find any obvious driver conflict. So I ran SFC/scannow and it found some errors, he couldn't fix. So I finally did a repair installation to see if file system cleaning would eliminate blue screens.

  I always get a BSOD.

  Which leaves me with what? A bad GPU? Unknown driver conflict? Bad motherboard?

  Here comes bluescreenview log for you to look over. If someone could help me please clarify, I'd appreciate it really any help I can get.

  Thank you.

  ==================================================
  Dump file: 073014-27892 - 01.dmp
  Crash time: 30/07/2014-15:26:46
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x0000000a
  Parameter 1: 00000000'00000088
  Parameter 2: 00000000'00000002
  Parameter 3: 00000000'00000001
  Parameter 4: fffff800'03656666
  Caused by the pilot: NDProxy.SYS
  Caused by the address: NDProxy.SYS + c8856a
  File description: NDIS Proxy
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.17514 (win7sp1_rtm.101119 - 1850)
  CPU: x 64
  Plant address: ntoskrnl.exe + 75bc0
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\073014-27892-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 286 280
  Dump of file time: 30/07/2014-15:27:42
  ==================================================

  ==================================================
  Dump file: 073014-27892 - 01.dmp
  Crash time: 30/07/2014-15:26:46
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x0000000a
  Parameter 1: 00000000'00000088
  Parameter 2: 00000000'00000002
  Parameter 3: 00000000'00000001
  Parameter 4: fffff800'03656666
  Caused by the pilot: NDProxy.SYS
  Caused by the address: NDProxy.SYS + c8856a
  File description: NDIS Proxy
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.17514 (win7sp1_rtm.101119 - 1850)
  CPU: x 64
  Plant address: ntoskrnl.exe + 75bc0
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\073014-27892-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 286 280
  Dump of file time: 30/07/2014-15:27:42
  ==================================================

  ==================================================
  Dump file: 080114 43243 - 01.dmp
  Crash time: 08/01/2014 12 h 22:50
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x0000000a
  Parameter 1: 00000000'00000088
  Parameter 2: 00000000'00000002
  Parameter 3: 00000000'00000001
  Parameter 4: fffff800'036 has 3666
  Caused by the driver: vga.sys
  Caused by the address: vga.sys + 2a7f56a
  Description of the file: VGA/Super VGA video driver
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7600.16385 (win7_rtm.090713 - 1255)
  CPU: x 64
  Plant address: ntoskrnl.exe + 75bc0
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\080114-43243-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 285 832
  Dump of file time: 01/08/2014-12:24:17 AM
  ==================================================

  ==================================================
  Dump file: 080114-29359 - 01.dmp
  Crash time: 01/08/2014-16:14:11
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x0000000a
  Parameter 1: 00000000'00000088
  Parameter 2: 00000000'00000002
  Parameter 3: 00000000'00000001
  Parameter 4: fffff800'03663666
  Caused by the driver: USBPORT. SYS
  Caused by the address: USBPORT. SYS + 1156 has
  File description: driver Port USB 1.1 & 2.0
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7600.16385 (win7_rtm.090713 - 1255)
  CPU: x 64
  Plant address: ntoskrnl.exe + 75bc0
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\080114-29359-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 286 344
  Dump of file time: 01/08/2014-16:15:09
  ==================================================

  ==================================================
  Dump file: 080414-142319 - 01.dmp
  Crash time: 08/04/2014-21:24:14
  Bug Check String: IRQL_NOT_LESS_OR_EQUAL
  Bug check code: 0x0000000a
  Parameter 1: 00000000'00000088
  Parameter 2: 00000000'00000002
  Parameter 3: 00000000'00000001
  Parameter 4: fffff800'03662666
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 75bc0
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.18409 (win7sp1_gdr.140303 - 2144)
  CPU: x 64
  Plant address: ntoskrnl.exe + 75bc0
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\080414-142319-01.dmp
  Number of processors: 6
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 286 544
  Dump of file time: 04/08/2014-21:25:25
  ==================================================

  Thank you!

  IRQL_NOT_LESS_OR_EQUAL (a)

  This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.

  This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high. The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

  Bugcheck A, {88, 2, 1, fffff80003662666}

  0: kd > k
  Call child-SP RetAddr site
  fffff800'00b9c038 fffff800'03681169 nt! KeBugCheckEx
  fffff800 '00b9c040 fffff800' 0367fde0 nt! KiBugCheckDispatch + 0 x 69
  fffff800'00b9c180 fffff800'03662666 nt! KiPageFault + 0 x 260
  fffff800 '00b9c310 fffff800' 03685df3 nt! KeInsertQueueApc + 0x42
  fffff800 '00b9c370 fffff880' 04a96f16 nt! IopfCompleteRequest + 0xb63
  fffff800 '00b9c460 fffff880' 04a64fb7 usbhub! UsbhPdoInternalDeviceControl + 0x4fe
  fffff800 '00b9c4b0 fffff880' 014da2b0 usbhub! UsbhGenDispatch + 0 x 57
  fffff800 '00b9c4e0 00000000' 001eed06 ffusb2audio + 0x52b0
  fffff800 '00b9c4e8 fffff880' 016884ba 0x1eed06
  fffff800 '00b9c4f0 fffff800' 0368c85c tcpip! TcpPeriodicTimeoutHandler + 0 x 714
  fffff800 '00b9c570 fffff800' 0368c6f6 nt! KiProcessTimerDpcTable + 0x6c
  fffff800 '00b9c5e0 fffff800' 0368c5de nt! KiProcessExpiredTimerList + 0xc6
  fffff800 '00b9cc30 fffff800' 0368c3c7 nt! KiTimerExpiration + 0x1be
  fffff800 '00b9ccd0 fffff800' 036798ca nt! KiRetireDpcList + 0 x 277
  fffff800'00b9cd80 00000000 00000000' nt! KiIdleLoop + 0x5a

  ffusb2audio.sys (driver of USB 2.0 audio Focusrite) refers to an invalid memory (0000000000000088).

  0: kd > lmvm ffusb2audio
  start end module name
  "fffff880 ' 014 d 5000 fffff880 ' 014e7000 ffusb2audio T (no symbol)
  Loaded symbol image file: ffusb2audio.sys
  Image path: ffusb2audio.sys
  Image name: ffusb2audio.sys
  Timestamp: Wed Oct 13 11:40:18 2011

  Very old driver, I recommend just completely uninstall the software and remove the device (if any).

  Kind regards

  Patrick

• Report of the BSOD caused by ntoskrnel.exe on the new generation.

  Hey guys! I recently built a new PC! Everything was fine for a few hours until I had a BSOD. For several days, I get several BSOD. When I use bluescreenview, he said each BSOD was caused by the driver notskrnle.exe (I have no idea what it is). Research in the topic suggested driver problems, corrupted files Windows or bad RAM. I've updated all the drivers that I know and I installed Windows 8 to own, twice. I could really use some help because this issue is frustrating.

  Here are my specs:

  Motherboard: AsRock H170 Pro4S

  RAM: 2 x G.SKILL NT Series 8 GB

  SSD: SanDisk SSD 240 GB more

  PSU: EVGA 750 GQ 80 + gold

  HARD drive: Seagate 1 TB HDD Desktop and WM10EFRX (that's my old HD from my old PC about 3 years)

  CPU: Intel i5 - 6600 k 3.5 GHz

  CPU cooler: Cooler Master 212 EVO Hype

  Graphics card: Sapphire Radeon NITRO R9 390

  Wi - Fi card: TP-LINK TL-WDN4800

  Here are the two most recent dump files:

  https://www.dropbox.com/s/zkmw8edn26pw192/022616-21828-01.dmp?DL=0

  https://www.dropbox.com/s/70gs9vxbkvzo4gx/022616-8828-01.dmp?DL=0

  I appreciate any help you have. Thank you!

  These are associated with atikmdag.sys ATI Radeon driver in Kernel Mode.

  Completely, remove the current (or software) driver and install the latest driver available.  For instructions on how to do read everything to update the drivers of my partner JMH3143 http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149 here

• Uninstall the Microsoft IPMI driver (IPMIdrv.sys) on Server 2008 R2

  Hello
  Several sources mention that the driver IPMI from Microsoft and Intel IPMI driver should not be loaded at the same time. If the two drivers are installed, the resource contention problems cause unreliable operation.
  I want to use the Intel driver and tried to uninstall the Microsoft IPMI driver (IPMIdrv.sys), but all my efforts have failed so far.
  Obvious way seems to be to start device, go to "System devices" Manager, "Microsoft generic compatible peripheral IPMI" right-click, select Properties, and on the driver tab, click on "Uninstall". When I do that, I don't get an error message, but when the reboot of the machine, "Microsoft generic compatible peripheral IPMI" reappears.
  I've also tried using DevCon.exe, but I got the same result as before. I also tried a few 'dirty' things, but they don't work as well.
  I am aware that I can choose to stop (disable through Device Manager) the Microsoft IPMI driver, but I really wish to uninstall completely (the evidence being IPMIdrv.sys should not appear when driverquery command is executed).
  Also, I can see in the Device Manager, Microsoft Generic IPMI compatible device properties -> resources -> list of the conflicting devices:
  Range of input/output, CA 0, 2 - 0CA 2 used by:
  Motherboard resources
  Range of input/output, CA 0, 3 - 0CA 3 used by:
  Motherboard resources
  Does have a meaning?
  Intel has published a document entitled the IPMI driver conflicts resolution in Windows Server 2003 R2, but as its name suggests, it is intended to Server 2003 R2, and the mentioned techniques do not work for Server 2008 R2.
  The pointers will be greatly appreciated.
  Thank you
  CD

  Hello

  It is better suited for the IT Pro TechNet public. Please ask your question in the Forum on TechNet Support. You can follow the link to your question:

  http://social.technet.Microsoft.com/forums/en-us/winservergen/threads

  Hope this information helps.

• Driver power state failure; BSOD; Cannot open the minidump files

  Two weeks, my computer with Vista has started giving me a BSOD with status message driver failure.  I found the minidump files, but cannot open them.  The BSOD usually occurs after the computer has entered a sleep or hibernation.  I have not added any equipment to the computer and Norton 360 when I scan computer everything seems OK.  It is August 10, 19, then 23, also.  Don't know what the cause of the problem. Is there general reasons that could cause this or is - associated virus or what?

  Thank you

  Hello

  Check this thread for more information using BlueScreenView, MyEventViewer and other methods
  to troubleshoot the BlueScreens - top 3 answers (now 4).

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

  You can use BlueScreenView to stick the BSOD info in a message here.

  NOTICE - report HTML all THE ELEMENTS or right-click on a BSOD line and select the same. Then, copy and
  Paste the lines in a message here. Make sure and check the file name section. Also check the time
  in MyEventViewer for more information as possible.

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

  Check out these utilities to see if information may be collected:

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

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

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

  MyEventViewer can be verified at the time of the blue screen (BSOD) within a second or so of the
  time of the BSOD to provide more information about the possible cause - see TIP.

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
  Set it for a bit before and after the time of the BSOD.
  http://www.NirSoft.NET/utils/my_event_viewer.html

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

  AppCrashView - free - a small utility for Windows Vista and Windows 7 that displays the details of all the
  application goes down has occurred in your system. The information breaks down is extracted from the .wer
  the files created by the Windows Error Reporting (WER) of the operating system component of each
  time that an accident has occurred. AppCrashView also allows you to easily record the list of accidents to
  text/html/csv/xml file.
  http://www.NirSoft.NET/utils/app_crash_view.html

  I hope this helps.

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

• What are the causes of error - OR-XNET: the NOR-XNET driver is no longer can communicate with the device.

  Hello

  I use X-NET-PCI8512, OS: Windows 7, C++ (middle of the QT interval).

  I'm pooling of card data (StreamIn member function) to ~ 100 Hz. card reading time (ReadStatus) to ~ 100 Hz.

  After about 40 min (depends on the amount of data in) I get this error:

  (Hex 0xBFF630B2) The NOR-XNET driver cannot communicate with the device. Solution: Make sure that the device was not removed from the computer.

  What are the causes of this error?

  Thanks in advance,

  Aviad

  Hello aviadCielo,

  When you get this error, what does do to make it work again? If you restart your program, start all this work?

  Secondly, what version of NOR-XNET do you use? It's maybe a software problem that could be resolved by upgrading to NOR-XNET 1.6.

  Finally, can you reproduce this problem with a simple program? If so, you can join the program you use?

• Is there a current threat to Windows causing the crashed hard drive?

  I received a call from someone who said he was from Windows support who wants to help me protect my computer from a 'infection' which would cause the crashed hard drive.  Is this real or a scam?

  Hello

  It's a scam.

  Microsoft does not contact you unless YOU have made prior arrangements with them to do.

  There is an article in the link I'm you provide at the end of this one

  Read this Information from Microsoft:

  "Avoid scams to phone for tech support.

  http://www.Microsoft.com/security/online-privacy/avoid-phone-scams.aspx

  Don't be fooled of unsolicited calls. Don't provide personal information.

  Here are some of the organizations that cyber criminals claim to come:

  • Helpdesk Windows

  • Windows repair center

  • Microsoft technical support

  • Microsoft technical support

  • Windows Support Group Technical Department

  • Microsoft Research and Development Team (team of Microsoft R & D)

  Either these so-called "Microsoft" Tech companies want to sell you a worthless software, or remote access to your computer to try to steal your credit card and bank information and also achieve an identity theft on you.

  See you soon.

• the Windows vista firewall authorization driver is missing, the cause of the problem that the firewall cannot be activated? How to fix?

  Recently my fireall cannot be activated? I tried manually put on throughout the service, no luck. Then, I checked the firewall authorization driver is absent, it is the cause of the problem that the firewall cannot be activated? How to fix?

  Hi James,

  Thank you for your e-mail. I solved the problem using System Restore.