Quote: Originally Posted by vibasu
Basic Info about my Computer:
Windows 7 Home Service Pack x64
The original installed OS on the laptop
OEM (came pre-installed)
The laptop was first booted in August 2010
I haven't reinstalled the OS
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
Files that help describe the problem:
I followed all the BSOD Posting instructions too, everything should be in order. Please let me know when the fix is available, I really appreciate all the help and work everyone has put in. Thanks!
Blamed on Netio.sys, it usually means your malware app. I would remove McAffe and replace with Microsot Security essentials at least to test. How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe) Microsoft Security Essentials - Free Antivirus for Windows
The BCC suggests
Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-d...tml#post356791
What you're looking for will be in one of the following categories:
a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
So, check the drivers
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests
Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/
Try this free stress test: Free Software - GIMPS
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.