Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Windows 7 BSOD (maybe a driver error)


03 Feb 2010   #1

Windows 7
 
 
Windows 7 BSOD (maybe a driver error)

As you probably guessed, like the other thousands of threads I just saw before I added to it all (lol), BSOD hit my Windows 7 laptop. I've come down it to be a driver problem, I think.
Quote:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0 Product: 768_1
So, I'll just post up my minidump files and to whoever finds the problem, Thank you! and to all who took the time to look through it thanks to you all as well.


My System SpecsSystem Spec
.

04 Feb 2010   #2
Microsoft MVP

 
 

The dump files blame netw5v64.sys - a component of your Intel wireless adapter.
Please download a fresh copy of the driver from the Intel Download Center (http://downloadcenter.intel.com/Default.aspx).
Then uninstall the current wireless drivers through Control Panel...Programs...Uninstall a program
Then install the freshly downloaded drivers and see if that fixes the BSOD's.

Also, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall/remove:
Quote:
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Code:
regi.sys     Mon Apr 16 11:19:10 2007 - InterVideo regi.sys driver
SFEP.sys     Fri Aug 03 01:35:53 2007 - Sony Firmware Extension Parser driver
Summary of the BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Feb  1 01:17:24.870 2010 (GMT-5)
System Uptime: 1 days 23:12:41.774
BugCheck D1, {4, 2, 0, fffff88004244c9f}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+dc9f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:09:28.424 2010 (GMT-5)
System Uptime: 0 days 1:03:59.328
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:27:34.623 2010 (GMT-5)
System Uptime: 0 days 0:07:31.527
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:35:40.548 2010 (GMT-5)
System Uptime: 0 days 0:07:32.452
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:53:57.182 2010 (GMT-5)
System Uptime: 0 days 0:17:41.086
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 22:00:49.888 2010 (GMT-5)
System Uptime: 0 days 0:06:19.792
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
My System SpecsSystem Spec
04 Feb 2010   #3

Windows 7
 
 

Thank you so much for helping! I already re-installed the new wifi driver, so, hopefully, that'll fix it. So thanks again and if I have any more problems, I'll be sure to check these forums.
My System SpecsSystem Spec
.


06 Feb 2010   #4

Windows 7
 
 

Ok I had posted about the more recent BSODs of the 0x0000001e error and such below
Quote:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0 Product: 768_1
So someone on my last thread said to update my netw5v64.sys file, which I did. Worked perfectly for a few hours. Then another dreaded BSOD appeared 0x1000007e. Attempting to look into the problem with the debugger and such, I get another BSOD again but this time of the 1st problem I had the 1e error. So it feels like I'm back to square one -_- So if anyone can help my poor nooby, BSOD-magnet self then it will be much appreciated. I will be attaching all the dump files thus far just in case if the problem wasn't solved in the files I included before.

2nd error:
Quote:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
bug check code: 0x1000007e
parameter 1:ffffffff`c0000005
parameter 2:fffff880`04a24943
parameter 3:fffff880`097763e8
parameter 4: fffff880`09775c40
caused by: NETw5s64.sys
More BSOD's:
Quote:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 19
BCP1: 0000000000000003
BCP2: FFFFFA8004C72410
BCP3: FFFFFA8004C72410
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Ok so these BSODs are getting really annoying, is it possible a re-format could get rid of them or just temporarily delay them from attack me again? And for the new error its a Pool_Corruption error if that helps anybody. So again for anybody who can help me with these dreaded BSODs, thank you and good luck to all attempting!
My System SpecsSystem Spec
06 Feb 2010   #5
Microsoft MVP

 
 

Yes, a reformat could possibly get rid of them - but there's no guarantee that, after all that work, you'll still have the BSOD's.

The majority of the BSOD's blame the network driver NETw5x64.sys. You've updated this driver - so that leaves a bunch of other possibilities:
- the Network card is damaged
- the motherboard is damaged
- your wireless router and/or modem is damaged
- there is some other software interfering with the networking (such as an Internet Security application or a firewall of some sort).

I have noticed traces of both an AVG program and a Norton/Symantec program on your system. Do you have both of these installed? Please uninstall all antivirus/antispyware/Internet Security/Security Center applications from your system and then follow this:
Quote:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: Download and run the Norton Removal Tool
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
Still waiting on the memory dumps to finish running. Will be back as soon as they're done.....
My System SpecsSystem Spec
06 Feb 2010   #6
Microsoft MVP

 
 

While we're waiting, try running Driver Verifier to see if it'll force the name of the offending driver. Please run it using these directions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
06 Feb 2010   #7
Microsoft MVP

 
 

Dump files are finished. The regi.sys file from InterVideo is still present and outdated as is the SFEP.sys file from Sony. Please update them, the SFEP.sys has caused issues for me in the past.

Update the above drivers (or remove them)
Do the thing that I mentioned previously with the AVG and Norton/Symantec programs
Then run the Driver Verifier.

Summary of all 25 BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Feb  1 01:17:24.870 2010 (GMT-5)
System Uptime: 1 days 23:12:41.774
BugCheck D1, {4, 2, 0, fffff88004244c9f}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+dc9f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:09:28.424 2010 (GMT-5)
System Uptime: 0 days 1:03:59.328
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:27:34.623 2010 (GMT-5)
System Uptime: 0 days 0:07:31.527
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:35:40.548 2010 (GMT-5)
System Uptime: 0 days 0:07:32.452
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 21:53:57.182 2010 (GMT-5)
System Uptime: 0 days 0:17:41.086
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  2 22:00:49.888 2010 (GMT-5)
System Uptime: 0 days 0:06:19.792
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb  3 01:46:05.260 2010 (GMT-5)
System Uptime: 0 days 3:44:16.164
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb  3 02:01:03.711 2010 (GMT-5)
System Uptime: 0 days 0:14:24.615
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+e1b7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb  3 02:54:16.152 2010 (GMT-5)
System Uptime: 0 days 0:21:18.056
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb  3 23:58:32.882 2010 (GMT-5)
System Uptime: 0 days 1:42:15.662
BugCheck 3B, {c0000005, fffff88005adea88, fffff88009039590, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+22ca88 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wlanext.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 00:17:21.079 2010 (GMT-5)
System Uptime: 0 days 0:18:16.983
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 01:29:35.164 2010 (GMT-5)
System Uptime: 0 days 1:11:15.943
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff880058d9943, fffff8800ac333e8, fffff8800ac32c40}
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 02:05:31.729 2010 (GMT-5)
System Uptime: 0 days 0:34:54.633
BugCheck 19, {21, fffffa8006a87000, 2020, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+299d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 03:19:37.518 2010 (GMT-5)
System Uptime: 0 days 1:13:37.297
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 06:59:39.975 2010 (GMT-5)
System Uptime: 0 days 3:38:57.879
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 07:18:58.417 2010 (GMT-5)
System Uptime: 0 days 0:18:20.321
BugCheck 19, {21, fffffa80062e0000, 2020, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+2c0a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 07:39:43.833 2010 (GMT-5)
System Uptime: 0 days 0:19:46.612
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 08:12:44.287 2010 (GMT-5)
System Uptime: 0 days 0:32:02.191
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 09:02:45.256 2010 (GMT-5)
System Uptime: 0 days 0:49:01.160
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 20:32:48.959 2010 (GMT-5)
System Uptime: 0 days 0:30:48.863
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 23:12:41.057 2010 (GMT-5)
System Uptime: 0 days 2:24:10.836
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88004a24943, fffff880097763e8, fffff88009775c40}
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 23:19:05.319 2010 (GMT-5)
System Uptime: 0 days 0:05:50.223
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 00:05:05.935 2010 (GMT-5)
System Uptime: 0 days 0:45:30.839
BugCheck 19, {3, fffffa8004c72410, fffffa8004c72410, 0}
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 00:45:53.113 2010 (GMT-5)
System Uptime: 0 days 0:40:16.017
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88004b0b943, fffff88007c8c3e8, fffff88007c8bc40}
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 01:31:07.809 2010 (GMT-5)
System Uptime: 0 days 0:44:38.713
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88004ae4943, fffff880093833e8, fffff88009382c40}
Probably caused by : NETw5s64.sys ( NETw5s64+e943 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
My System SpecsSystem Spec
08 Feb 2010   #8
aem

Windows 7 Ultimate 64Bit
 
 

Quote   Quote: Originally Posted by SilverCherudim View Post
As you probably guessed, like the other thousands of threads I just saw before I added to it all (lol), BSOD hit my Windows 7 laptop. I've come down it to be a driver problem, I think.
Quote:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Hey i just noticed the Build version...2.007683 ? Is this the latest?
My System SpecsSystem Spec
09 Feb 2010   #9

Windows 7
 
 

Yes, it is the latest verison, or at least to my limited knowlegde.
I want to say that I think my laptop is working fine
because no BSoD in an entire full day (yayz!),
but you can never know with computers these days. lol.
Anyway, I have fixed the AVG/Norton problem, unistalled
the InterVideo Driver, and updated the SFEP.sys file.
So, if anything goes wrong again, I'll post again here.
So thank you's to usasma for the continuous and great help,
and to aem for effort to input and help out.
My System SpecsSystem Spec
Reply

 Windows 7 BSOD (maybe a driver error)




Thread Tools



Similar help and support threads for2: Windows 7 BSOD (maybe a driver error)
Thread Forum
BSOD when start windows, error 0x0000006b,caused by driver ntoskrnl.ex BSOD Help and Support
BSOD: Windows Driver Framework Violation - error 0x0000010D BSOD Help and Support
BSOD driver error BSOD Help and Support
Solved BSOD ON Driver IRQL_NOT_LESS_OR_EQUAL ERROR BSOD Help and Support
BSOD driver ntoskrnl.exe error BSOD Help and Support
BSOD driver display error BSOD Help and Support
Video Driver BSOD error BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:52 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33