New
#1
Computer BSOD Randomly
Hi my computer lately has started to BSOD randomly. I cant seem to link it to anything in particular. Any help is appreciated thank you.
Hi my computer lately has started to BSOD randomly. I cant seem to link it to anything in particular. Any help is appreciated thank you.
Welcome to the forum cowman435,
Reduce items at start-up:
Perform a clean boot:
Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-
xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
Driver Reference Table - xusb21.sys
PxHlpa64.sys Wed Oct 21 00:08:42 2009 (4ADDFCAA)
Sonic CD/DVD driver (used by many different CD/DVD programs)
Driver Reference Table - PxHlpa64.sys
LGVirHid.sys Tue Nov 24 07:36:48 2009 (4B0B38B0)
Logitech Gamepanel Virtual HID Device Driver
Driver Reference Table - LGVirHid.sys
LGBusEnum.sys Tue Nov 24 07:36:48 2009 (4B0B38B0)
Logitech Keyboard
Driver Reference Table - LGBusEnum.sys
btath_rcp.sys Thu Jun 24 12:17:21 2010 (4C22F871)
Atheros Bluetooth Driver
Driver Reference Table - btath_rcp.sys
btath_flt.sys Thu Jun 24 12:17:38 2010 (4C22F882)
Atheros Bluetooth Driver
Driver Reference Table - btath_flt.sys
btath_bus.sys Thu Jun 24 12:17:43 2010 (4C22F887)
Atheros BlueTooth driver
Driver Reference Table - btath_bus.sys
btath_hcrp.sys Tue Jun 29 15:30:43 2010 (4C29BD43)
Atheros Bluetooth Driver
Driver Reference Table - btath_hcrp.sys
evolve.sys Sat Aug 7 10:47:00 2010 (4C5CE544)
Echobit Evolve Virtual Miniport (Ethernet) driver
Driver Reference Table - evolve.sys
jraid.sys Tue Aug 10 15:28:44 2010 (4C611BCC)
JMicron RAID Driver
Driver Reference Table - jraid.sys
ICCWDT.sys Wed Aug 18 14:27:45 2010 (4C6B9981)
IIntel(R) Watchdog Timer Driver
Driver Reference Table - ICCWDT.sys
AsIO.sys Tue Aug 24 07:53:02 2010 (4C7325FE)
Asus PCProbe Utility
Driver Reference Table - AsIO.sys
btath_lwflt.sys Mon Sep 13 14:26:54 2010 (4C8DE04E)
Atheros Bluetooth Driver
Driver Reference Table - btath_lwflt.sys
e1c62x64.sys Wed Sep 22 03:34:15 2010 (4C9924D7)
Intel(R) 82579V Gigabit Network Connection driver
Driver Reference Table - e1c62x64.sys
HECIx64.sys Wed Oct 20 05:33:43 2010 (4CBE2AD7)
Intel Management Engine Interface
Driver Reference Table - HECIx64.sys
AiChargerPlus.sys Mon Nov 8 12:48:26 2010 (4CD79D3A)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Driver Reference Table - AiChargerPlus.sys
NvStreamKms.sys Wed Apr 30 06:59:44 2014 (53604B00)
nVidia Streaming Kernel service - may cause BSOD in Win8.1 systems (found in May 2014). Date/TimeStamp: Tue Apr 29 20:59:44 2014 (53604B00)
Driver Reference Table - NvStreamKms.sys
To perform a clean install of a driver, follow this tutorial:
Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
Remove Avast! for testing purpose.
Recommended antivirus software for Windows 7 based on stability compared to others:-
- Microsoft Security Essentials Download | Free Spyware Protection
- Malwarebytes - The Free version
- Good & Free Security Combination
WarningDo not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:
Run a Hard Drive test:
Run Disk Check on your hard disk for file system errors and bad sectors on it:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.3. Test the next stick of RAM (stick #2) in the next motherboard slot.*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.InformationErrors are sometimes found after 8 passes.
TipDo this test overnight, before going to bed.
Code:Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144 Debug session time: Fri Jun 6 01:25:25.935 2014 (UTC + 6:00) System Uptime: 0 days 8:47:30.747 BugCheck 1A, {41790, fffffa8000906b70, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 ) BUGCHECK_STR: 0x1a_41790 PROCESS_NAME: chrome.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144 Debug session time: Thu Jun 5 03:01:34.613 2014 (UTC + 6:00) System Uptime: 0 days 4:54:12.800 BugCheck 50, {fffffba009927beb, 0, fffff800034b48b5, 7} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b ) BUGCHECK_STR: 0x50 PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Thank you for the response, It was one of the sticks of RAM, it failed Memtest almost immediately.