Error BAD_POOL_Header/Page_Fault

Similar Questions

• BSOD error "BAD_POOL_HEADER" so he was working on a program "final 2011"on my computer.

  I just got a message with the BSOD BAD_POOL_HEADER. I can reliably recreate the scenario; Like starting my computer, I opened a particular program (final 2011), and in this case. If my computer has been on already and I have done other things & I open the same program, it opens normally.

  This is the my computer created dmp file:

  https://www.dropbox.com/s/m4jx69a5z1rhpwi/010515-43805-01.dmp?DL=0

  Let me know if you need more information... I am running Windows 7 Home Premium 64 - bit SP1.

  Thank you in advance for your help!

  (Moved to programs)

  Hi Alex,

  Thanks for posting this request here, in the Microsoft Community.

  This might have caused due to all the files in the program of third party/PPP. I would suggest trying the following methods and check if it works for you.

  Method 1:

  Try the procedure described in the following Microsoft Help article and check if that helps. This article consists of the steps to solve the errors blue screen on your computer.

  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Warning: when running chkdsk on the drive hard if bad sectors are found on the disk hard when chkdsk attempts to repair this area if all available on which data may be lost.

  Method 2:

  Put the computer in a clean boot state, and check if the problem persists. This will help you determine which third party/PPP program is causing this problem.

  See the following Microsoft Support article to place the computer in a clean boot state.

  http://support.Microsoft.com/kb/929135 
  Note: After the boot minimum troubleshooting step, see the "How to reset the computer to start as usual after a clean boot troubleshooting" section in the link provided to return the computer to a Normal startup mode.

  After you have determined which third party/PPP program is causing this problem, try reinstalling the program/application and see whether this is due because of installation issue related or not.

  http://Windows.Microsoft.com/en-us/Windows/uninstall-change-program#uninstall-change-program=Windows-7

  http://Windows.Microsoft.com/en-us/Windows/install-program#1TC=Windows-7

  Please reply with the status of the issue so that we can better help you.

• Windows 7 64 bit Ultimate - BSOD error: BAD_POOL_HEADER error checking code: 0x19, 0 x (22...

  Hello

  Just, I started my PC and got the BSOD:

  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033

  More information about the problem:
  BCCode: 19
  BCP1: 0000000000000022
  BCP2: FFFFF8A004ED6000
  BCP3: 0000000000000001
  BCP4: 0000000000000000
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 256_1

  Files helping to describe the problem:
  C:\Windows\Minidump\123014-32307-01.dmp
  C:\Users\Admin\AppData\Local\Temp\WER-43025-0.SysData.XML

  Here are the 2 files above in a ZIP archive:

  https://onedrive.live.com/redir?RESID=68C615C9C1A0C11E%21303

  Thank you for your help.

  Thank you.

  I have not yet done, but have done the following:

  -Deletion of Symantec Endpoint Protection 11 and installed v12 instead.

  -Removal of Adobe Air

  -Skype upgrade to the latest version

  -Removal of the redundant Brother printer driver (I sold it some time ago).

  -Clean the event log: http://jacobytech.net/forum/index.php?topic=124.0

  -Ran Microsoft FixIt to remove the error from the event ID 10. not not help, therefore the manual vbs script method that worked:

  https://support.Microsoft.com/kb/2545227?WA=wsignin1.0

  So far, the event log appears to show almost no questions, he showed and the system runs a lot faster.

  I'll let it run this way for a while and continue debugging if the BSOD comes to visit again.

  Re-post here if everything changes.

  See you soon.

  P.S., Also used sysinternals autoruns to disable some redundant drivers that displays errors in Event Viewer, as they have been previously uninstalled already.

  EDIT January 6, 2015:

  One more thing I did, leaving the port USB3 Wifi USB dongle on a USB2 port, leaving all taken them vacant USB3.

  It has also solved the problem of verifier.exe giving the black screen.

  I suspect that the question was actually related to port USB3/pilot (turd).

• BSOD, error: BAD_POOL_HEADER

  Hi all

  My laptop restarts randomly with a mistake that we called BAD_POOL_HEADER.
  I'm not much of a gamer, BSOD occurs when im reading PDF, editing documents, watching movies.
  I know that I had this problem when I brought my lappy, but it has increased since the week last 2.

  In my event log, I saw so many critical mistakes [kernell power ID:41, task category event: 63].
  I couldn't event 8.1 update, whenever it crashed when I tried to do an update. So I stopped to do an update.

  And now since this morning I have no why, my processor and disk % use maximum.

  I thought it will decrease thereafter, but they do not.

  I hope someone can find a solution to my problem.
  Thanks in advance.

  My minidumps and PC info is uploaded here

  [www.mediafire.com/download/oizjjj8uz1kokj7/MiniDumps.zip]

  Loki

  Devi this handler simply checks against a list.  You have no old drivers.

  This accident has been verified and connected to the driver volsnap.sys volume shadow copy update of Microsoft Corporation to win 8.1 should solve the problem.  I would also like to run a file system check to verify the operating system

  Please run a check of system files (SFC) 

  
  

  All instructions are in our Wiki article below...
  If you have any questions please ask us for .

  File System check (SFC) Scan and repair system filesone

  Old drivers

  NTIDrvr.sys 19/04/2010 21:37:59
  UBHelper.sys 06/07/2010 12:19:26 AM
  mwlPSDFilter.sys 25/03/2011 03:12:11
  mwlPSDNServ.sys 25/03/2011 03:12:13
  mwlPSDVDisk.sys 25/03/2011 03:12:23
  GEARAspiWDM.sys 03/05/2012 15:56:17

• Error BAD_POOL_HEADER in Windows 8

  Hello

  Recently I did a fresh install of windows 8 after running a problem (not related), but before I did I saved a few things that I wanted to keep on an external hard drive, one of whom was my folder Fonts that I had loads of custom in there fonts.

  Last night I tried to reinstall these fonts first by moving them to my hard drive on my desktop, and then removing simply the folder of fonts in the Windows on the C: drive folder, as expected a message flashed by saying me it y x amount of fonts with the same name and asked if I would like to replace or ignore these elements. I chose to replace them, maybe in hindsight I should have chosen to ignore them.

  Because now when I double click to go into my fonts folder, I get the blue screen with the message BAD_POOL_HEADER and restart my laptop. It is good otherwise, it's just when I click to go to the fonts folder.

  So the next thing I tried (perhaps foolishly) was to delete the folder fonts, with my plan is to replace it with one of my external hard drive. However what is called TrustedInstaller wouldn't let me remove completely, although it had apparently 2 067 files. Hoping that this solves the problem, I double click to go to the fonts folder and low & here's, I still have the blue screen issue...

  Any ideas? All comments appreciated. :)

  Hello

  You seem to be knows a mistake similar, as reported in this this thread.

  Try to rebuild the cache of police:

  Rename the FNTCACHE. DAT (in C:\Windows\System32 folder).

  Rename the FNTCACHE. DAT to something like FNTCACHE.old

  Restart the computer and let Windows re - create the FNTCACHE. DAT

• Message says: "Windows could not load correctly" then he got the error: "0xa0000001.

  So I recently got these computer errors on my laptop. The pixels on the screen start to panic and it still restarts my computer.

  The first time, he started was when I was playing a game called League of Legends and it worked perfectly fine on my laptop, and he had always run around 70 fps. I played this game for a long time. Then, in the middle of an online game the screen flipped out and restarted my PC! He sent me a message saying: "your PC has encountered a problem :(. "

  After it restarts my laptop and then after restarting the pixels on the screen start to panic again and it restarted. After that restart again once he sent me a message saying he will "fix the problem on my PC. I clicked on 'Repair' and then it restarted again. After the restart he freaked out again and then it restarted and it gave me a message saying "your PC will convert at an early stage when it doesn't have this problem. This can remove files that have been installed recently. So, I allowed it do and after 3 hours of waiting he brought me to an earlier stage if my laptop was not the problem. He only come back in a few hours. Then the next day, I decided to try again in League of Legends, it was working fine and it launched the game. I was running on my normal fps then he started trolling and it fell to 12 frames per second and the screen flipped out again and then my computer restarted. Once restarted, it it worked fine after 5 minutes it restarted again, and then he gave me a message saying: "Windows could not load correctly" then he said I got the error: "0xa0000001. I turned on my PC and my screen has panic when he started, and then it restarted again give the same message and tell you have the error: 'DRIVER_OVERRAN_STACK_BUFFER '. It came on again and it was worse still panic then it restarted and it gave me the same message saying that you have the error: "BAD_POOL_HEADER". It restarts and several times with lit the screen always freak out so I decided to just remove the plug and ask for help. I went on the computer of my brother and sought a solution for these errors. Turns out Im not the only one to these errors. They say that '0xa0000001' error is caused primarily by an AMD graphics card and my graphics card is an AMD graphics card. The solution for this error is to uninstall the graphics card and reinstall it directly from the manufacturer's website. I could have made this solution and corrected my graphics card, but there is a problem. Whenever I turn on my laptop the pixels panic and sometimes the screen turns black and then it restarts. I can't access anything whatsoever, and he keeps just restarting. Please help me and tell me how to fix my phone :( I really need a solution to this problem.

  Please answer quickly :(

  Thank you

  There is an old saying that if it ain't broke, don't fix it.

  It works again.

  Read this information

  You need to get the Driver of your laptop computer software or a hardware manufacturer, not through Windows Update (with the exception of Microsoft put updated material), as Microsoft normally does nor those have the most recent drivers available as Microsoft leverages the hardware manufacturer 3rd party to provide them.

  Go to the website for your laptop or manufacturing equipment > Driver and Software Support Section > search your laptop or material style number > then your operating system > locate the correct drivers > download and install.

  ______________________________________________________

  But this is no guarantee that this won't happen again.

  Also, it would be that the game hardware requirements are higher than supports the hardware in your laptop.

  It could also be due to lack of graphic material.

  All you can do is search for the latest drivers and play games that require only a material that has your Lapyop.

  See you soon.

• BSOD W530 frequently

  W530

  Type - 2441-BQ2

  SN - xxxxx

  SSD - SSDSC2BF240A4L - Driver ver - 1.75.02

  Intel Core I7-3940XM

  16 GB memory

  WIndows 7 Enterprise SP1 64 bit - load Corporate gold

  WhoCrashed are:

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

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

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

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

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

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

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

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

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

• My Windows 7 keeps freezing or crashing randomly (BSOD)

  I am on Windows 7 Ultimate and my laptop Compaq Presario CQ61 guard randomly freezing or crashing. It got so bad now that yesterday, I was only able to apply some of the tools such as Fix It in Mode safe, now I can start my laptop and it works but freezes usually about 15 minutes.

  This is a report generated by «WhoCrashed»

  All pilots seem to be uptodate.

  (Local) information system

  computer name: xxx - PC
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  Hardware: Compaq Presario CQ61 Notebook PC, Hewlett-Packard, 3069
  CPU: GenuineIntel Pentium (r) Dual-Core processor T4400 @ 2.20 GHz Intel586, level: 6
  2 logical processors, active mask: 3
  RAM: 3119435776 total

  Crash Dump Analysis

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Tuesday, April 21, 2015 3:45:55 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: win32k.sys (win32k! EngTextOut + 0 x 26)
  Bugcheck code: 0x7A (0xFFFFFFFFC0000185, 0x460938C0, 0xFFFFFFFFC07F2E10, 0xFFFFFFFFFE5C2004)
  Error: KERNEL_DATA_INPAGE_ERROR
  file path: C:\Windows\system32\win32k.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Multi-User Win32 Driver
  Bug control description: this bug check indicates that the data page of the kernel of the required paging file cannot be read into memory.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Saturday, September 13, 2014 8:36:36 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091314 -.dmp
  This was probably caused by the following module: athr.sys (athr + 0x428A5)
  Bugcheck code: 0xD1 (30, 0 x 2, 0 x 0 x 0, 0xFFFFFFFF938618A5)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\
  Friday, September 12, 2014 9:08:40 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\091214-
  Wednesday, June 25, 2014 8:17:18 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\062514-
  Monday, June 23, 2014 8:55:18 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\062314-
  Thursday, June 5, 2014 19:8:15 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\060514-
  Sunday, May 11, 2014 8:42:17 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\051114 -.dmp
  This was probably caused by the following module: ntkrnlpa.exe (nt + 0 x 120996)
  Bugcheck code: 0x19 (0x3, 0xFFFFFFFF88A94620, 0xFFFFFFFF88A94620, 0x3A51)
  Error: BAD_POOL_HEADER
  path: C:\Windows\system32\ntkrnlpa.
  Wednesday, April 9, 2014 14:48:52 this computer crashed
  crash dump file: C:\Windows\Minidump\040914-

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

  Igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
  ATHR.sys (Atheros Extensible, Atheros Communications, Inc. wireless device driver.)
  dlkmd.sys (DisplayLink WDDM KMD, DisplayLink Corp.)

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

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

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

  PJ

  Still on the same pilot (HIDCLASS. (SYS).  You have still 2 malware apps (Isafe & AVG) assets.  I remove them both and using MSE instead

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

• 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

  

• Blue screen-pool header

  Windows crashes after 20-30 minutes

  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  Material: N5050, Dell Inc., Inspiron 01HXXJ
  CPU: GenuineIntel Intel (r) Core i3 - 2350M @ 2.30 GHz Intel586 CPU, level: 6
  4 logical processors, active mask: 15
  RAM: 4198785024 total
  ======================================================================

  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: unknown (0x00000000)
  Bugcheck code: 0x19 (0x20, 0xFFFFFA8005DFF970, 0xFFFFFA8005DFF990, 0 x 4020009)
  Error: BAD_POOL_HEADER
  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.
  A third-party driver has been identified as the likely cause of the system error.
  Google search: BAD_POOL_HEADER

  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

  .

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

• Get the following blue screen on startup error: STOP: 0x0000007E, BAD_POOL_HEADER STOP: 0 x 00000019, IRQL_NOT_LESS_OR_EQUAL STOP 0x0000000A

  Original title: XP questions

  I am running WIndows XP Pro SP3 on a Dell Optiplex gx270s and get several error messages stop "Blue screen" intermittent and different at startup (for protect my computer). Prompt notification Windows found problems with the file system and run CHKDSK/F. I am unable to do so as I can not find my administrator password (also necessary if you plan to run from my XP installation disc). Windows Fix - It Center, running 'Folder & troubleshooting' reports icons randomly change the icons but no resolves not. I didn't notice the icons change and do not if this is related to Stop what error messages at startup, I've been doing. Running a disk check during start-up and Diagnostics IDE are not problems. It lasts for quite awhile and I've delayed just deal with it because it is not always the case. A lot of program installs / uninstalls and Microsoft Updates since its start if the system restore wouldn't do me any good. Before reinstalling the operating system, what are my options? Is there a way to reset my ' Administor password ", or better yet does not require one, (it is a personal computer for personal use only and I don't remember why a password has been assigned)?

  Here are some of the error messages:

  STOP: 0x0000007E (OxC0000005, 0x89AD8000, 0xA579CCB4, 0xA579C9BO)

  BAD_POOL_HEADER

  Technical information:

  STOP: 0 X 00000019 (0X00000020, 0X89D5FDA0, 0X89D5DC8, 0X0A050002)

  IRQL_NOT_LESS_OR_EQUAL

  STOP 0X0000000A

  (0x6750300C, 0 x 0, 00000002 00000000, 0x804FFDB6)

  Hello

  You did changes to the computer before this problem?

  The administrator password cannot be reset.

  See the following article for more information: Microsoft's strategy concerning lost or forgotten passwords

  In the following troubleshooting steps may help you resolve this problem.

  How to troubleshoot a Stop error 0x0000007E in Windows XP
  http://support.Microsoft.com/kb/330182

  FIX: Error Message When you connect a scanner or a digital camera to a computer that is running Windows Vista or Windows XP Service Pack 2: "BAD_POOL_HEADER STOP"
  http://support.Microsoft.com/kb/934177

  You receive an error message "Stop 0x0000000A" in Windows XP
  http://support.Microsoft.com/kb/314063

• My Vista 64-bit Ultra system crashed with error messwage "BAD_POOL_HEADER". What does that mean.

  It worked normally, I weppe away for a few meals and goes to a blue screen with these three words as my only clue. Someone at - it ideas.

  Hello

  1. When you get this blue screen error normally, while using the computer, or work on a specific application?

  2. don't you make changes to the computer until the problem occurred?

  There are a number of causes of BSOD BAD_POOL_HEADER, the most frequent causes are bad drivers associated with the video/sound/network problems HARD drive, memory problems and also card motherboard/BIOS can sometimes cause it.

  I suggest you try the steps from the link below, which you would have to resolve stop (blue screen) error in Windows 7.

  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Hope this information is useful.

• How can I fix my computer of these blue screen of death error: KMODE_EXCEPTION_NOT_HANDLED BAD_POOL_HEADER & MEMORY_MANAGEMENT

  Last week, I updated my Windows 8 computer after that it had been updated to 8.1 because the computer was crashing so frequently. However, I continued to receive several blue screen error of death (KMODE_EXCEPTION_NOT_HANDLED, BAD_POOL_HEADER & MEMORY_MANAGEMENT).

  These have taken place when I watch movies via Amazon instant video or power video chat with my family. I guess I need to update a driver, but I don't know how to determine which driver to date.

  Is there an easy way to find out what the cause of the problem? What should I do?

  Here are my computer specs:

  HP Pavilion

  Windows 8

  Processor: AMD A8 - 5545 M APU with graphics HD Radeon (TM) 1.70 GHz

  RAM: 8.00 GB (7.22 GB usable)

  Operating system 64-bit, x 64 based processor

  I'm working on getting a shared online memory minidump file. I have problems with that.

  Yes, he did delete it. You can try a first auto repair (insert the installation DVD before the race) - http://www.bleepingcomputer.com/tutorials/http-wwwbleepingcomputercom-tutorials-automatically-repair-windows-8-with-automatic-repair-/

  Kind regards

  Patrick

• Error BSOD BAD_POOL_HEADER "based EQUALITY DRIVER_IRQL_NOT_LESS_OR MEMORY_MANAGEMENT"

  Original title: Win7 - several daily BSOD.

  Several times a day I'm especially crashed with a BSOD, but it freezes sometimes "simply".  I did a disk check and a memory test.  I can go back to last August, but I suspect that will not work, because it hangs in Mode safe and even crashes if I run Linux on a CD.

  I see a different reason for each accident, in the window that opens after the re-login, the BSOD is not always tell me why, but they were all multiple:

  BAD_POOL_HEADER
  DRIVER_IRQL_NOT_LESS_OR-EQUAL
  MEMORY_MANAGEMENT
  PFN_LIST_CORRUPT

  I received this "ROM" only once to a BSOD: "win32k.sys attempt to write in ROM.

  But I got a warning ROME to each logon for the weeks severak.  RAID screen said: "WARNING: have the option ROM cannot be invoked"and it "feels" simply as a problem of memory SINGLE stock holding still during the last weeks. " (Click to open an email in Outlook can get me the circle of rotation as long as 30 seconds)  This alert has disappeared as I was trying to bugs BSOD.

  All my files are in a unique OneDrive zip archive.  I've included the STOP codes that I get when reconnected (txt file), the dmp and xml files... two zips and a text file in a single archive.  There are fewer than I expected with so many accidents in the txt file.

  http://1drv.Ms/1jYLCAi

  Thank you

  Mike

  You probably face some form of a conflict between Norton and the module (Vipre AV gfibto.sys) listed below, and this can lead to problems of corruption... See if you can remove the two and replace Norton with Microsoft Security Essentials.

  Norton Removal Tool
  https://support.Norton.com/SP/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

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

  8aeb6000 8aeb7a80 gfibto gfibto.sys Thu Sep 01 21:29:13 2011 (4E603169)
  http://SystemExplorer.NET/file-database/file/gfibto-sys

  8aeb6000 8aeb7a80 gfibto T (no symbol)
  Loaded symbol image file: gfibto.sys
  Image path: gfibto.sys
  Image name: gfibto.sys
  Timestamp: Thu Sep 01 21:29:13 2011 (4E603169)
  CheckSum: 0000DF11
  ImageSize: 00001 has 80
  Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4