BSOD, ntoskrnl.exe, happens a few times a day

[Seeme]

Hello, I'm getting a BSOD several times a day, it's a system that I purchased from CYBERPOWER, and it's been getting BSOD pretty frequently. I can't pinpoint any specific cause. It happens pretty randomly, some times when not much going on, and sometimes when I have a lot of things open.

 

[rajdeepak singh]

Run a disk check of system drive
right click at your drive having windows and goto to tools tab and click check now in error checking,in check disk options makes sure to select both file system error and attempt recovery of bad sectors and hit start.It will ask you schedule a disk check at restart accept and restart the pc and wait for disk check to complete.

After that type cmd in start menu and run it as administrator,
type the following command and run to do a windows file integrate check and repair.

sfc /scannow

Post any error found.

 

[Seeme]

I ran both scans, and did not come up with any errors

 

[Seeme]

got another BSOD today

 

[koolkat77]

It seems that VmWare software is contributing to your BSODs. Please uninstall it while we troubleshoot. Please also uninstall GIGABYTE On/Off Charge driver/software. It is a known cause to BSODs.

AppleCharger.sys            Wed Nov  2 08:46:00 2011

   Information

Download

and install Revo Uninstaller.

• Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

------------------------
Reduce the start-up items, Antivirus software is basically whats required.

• Remove Startup Programs in Windows 7
• Clean Startup in Windows 7

------------------------
Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
• Help protect your PC with Microsoft Security Essentials
• Malwarebytes Free

   Note

:info: Do not start the trial version of MalwareBytes

You may also take a look at:

• Good & Free System Security Combination

Follow these-

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

------------------------
Update the driver below to its latest version available.
e1c62x64.sys Fri Mar 16 09:57:28 2012 Intel(R) 82579V Gigabit Network Connection driver
Driver Reference Table - e1c62x64.sys
------------------------
Upload a screenshot using:

• CrystalDiskInfo:tip: For how to upload a screenshot or file, read here

Test your Hard Drive(s) by running:

• Hard Drive Diagnostic Procedure

------------------------
Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Keep us Posted.

BSOD BUGCHECK SUMMARY

[FONT="Lucida Console"]Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Aug 28 18:17:57.618 2013 (UTC + 6:00)
System Uptime: 0 days 4:37:41.834
BugCheck 3B, {c0000005, fffff80002cc9d9c, fffff8800d8f2910, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vmware-vmx.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Aug 28 13:38:38.740 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:07.956
BugCheck C4, {83, 5354414d, 8, 53544}
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Probably caused by : AppleCharger.sys ( AppleCharger+1df0 )
BUGCHECK_STR:  0xc4_83
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Aug 23 20:14:39.542 2013 (UTC + 6:00)
System Uptime: 0 days 9:59:59.370
BugCheck 3B, {c0000005, fffff80002cdad9c, fffff8800910e910, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vmware-vmx.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Aug 16 11:45:42.716 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:00.932
BugCheck 19, {20, fffffa80204be0c0, fffffa80204be1e0, 4120003}
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+c92a )
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Aug 16 11:43:50.597 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:15.409
BugCheck C5, {fffff81002e626b0, 2, 0, fffff80002e07a4e}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+192 )
BUGCHECK_STR:  0xC5_2
PROCESS_NAME:  vmware.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Aug 16 00:01:28.938 2013 (UTC + 6:00)
System Uptime: 0 days 10:55:04.951
BugCheck 3B, {c0000005, fffff80001ccdd9c, fffff88010856910, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vmware-vmx.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Aug 15 13:05:34.820 2013 (UTC + 6:00)
System Uptime: 0 days 22:26:54.833
BugCheck 3B, {c0000005, fffff80001c8dd9c, fffff88010478910, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vmware-vmx.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Wed Aug 14 14:37:50.445 2013 (UTC + 6:00)
System Uptime: 0 days 23:51:30.069
BugCheck 3B, {c0000005, fffff80001cd6d9c, fffff8800f43f910, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vmware-vmx.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[Seeme]

Going to work on these issues and then I'll post back with an update.