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: Win 7 BSOD

20 Nov 2010   #1
b82a

Windows 7 Ultimate x64
 
 
Win 7 BSOD

Hi! I've got a problem with my pc. When i boot my PC its shows me different BSOD's, when i restart - all good, but its annoying to restart PC every time when i boot it. Need help.

My windows 7:
- x64
- its not original
- full retail version
- Age of system - 2 years 5 months
- Age of OS installition - 1 year


My System SpecsSystem Spec
.
20 Nov 2010   #2
usasma
Microsoft MVP

 
 

Virtual Ethernet adapters are having problems. Is this deliberate? If so, why? If not, please translate this to English for us (it doesn't translate well on BabelFish):
Quote:
Симптом:[IMG]res://wdc.dll/error.gif[/IMG]
Устройство отключено.Причина:Устройство отключено и поэтому не может работать правильно.Сведения:Устройство VMware Virtual Ethernet Adapter for VMnet1 отключено. Если это устройство больше не используется, возможно, оно специально отключено. Идентификатор Plug and Play для этого устройства: 13.Разрешение:1. Определите, требуется ли данное устройство.
2. Если устройство требуется, включите его в диспетчере устройств.
3. Если устройство не требуется, его можно не включать.Связанный:Объяснение кодов ошибок, которые формирует диспетчер устройств
Управление устройствами в Windows
MSINFO32 file isn't readable, please save it as a text file and upload it with your next post (this is a common problem with differening languages).

Systeminfo.txt doesn't show any Windows Updates. Please visit the Windows Update website and get all available updates for your system.

Please uninstall Daemon Tools/Alcohol 120%. Then remove the troublesome sptd.sys file using this free tool: DuplexSecure - FAQ - Remove 64 bit sptd.sys

I ran the last 6 memory dumps (the rest were significantly older and may not be related to this problem).

It is possible that the following older drivers may be causing your problems.
Please either REMOVE or Update the older drivers listed below.
Quote:
HOW TO FIND DRIVERS:
DO NOT use Windows Update or the Update Driver function of Device Manager as they are not the most current versions available.
Also, DO NOT update from the PC Manufacturer's website unless the Driver Reference cited below states that you should get the drivers from the OEM.

The most common drivers are located on this page: Driver Reference
If you can't find the driver, post back and we'll see what we can find.

Here's the older drivers that were found in the memory dump files:
Code:

systormwrb.sys Sun Nov 04 12:25:56 2007 (472E00A4)
 - Cyber Snipa/Flexiglow WarBoard Game Controller
 - Driver Reference

adfs.SYS     Mon Nov 03 11:48:14 2008 (490F2B4E)
 - Adobe File System Filter driver
 - Driver Reference

DgiVecp.sys  Thu Oct 30 23:38:29 2008 (490A7DB5)
 - IEEE-1284 parallel class driver for ECP, Byte, and Nibble modes - Device Guys or Samsung
 - Driver Reference

SSPORT.sys   Thu Aug 11 19:07:32 2005 (42FBDA34)
 - Samsung printer driver
 - Driver Reference
If all of the above doesn't fix the issue, please try running Driver Verifier according to 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/Win7 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:
Code:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov 19 04:18:37.175 2010 (UTC - 5:00)
System Uptime: 0 days 0:08:02.204
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  System
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03a84105 fffff880`0897e960 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 14 23:48:47.567 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:49.596
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`351a8bcb 00000000`00000002 00000000`00000000 fffff800`03892363
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Nov 14 23:46:01.157 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:41.186
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+174 )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
Bugcheck code 000000C5
Arguments 00000000`20446e08 00000000`00000002 00000000`00000000 fffff800`039aa000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 10 05:08:17.128 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:38.157
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000c50`02010000 00000000`00000002 00000000`00000001 fffff800`03891bf0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 10 00:23:09.333 2010 (UTC - 5:00)
System Uptime: 0 days 0:40:07.362
Probably caused by : ntkrnlmp.exe ( nt!SwapContext+11 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000693`00000049 00000000`00000002 00000000`00000000 fffff800`038d4091
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Nov  5 05:07:27.370 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:58.398
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`2e791e35 00000000`00000002 00000000`00000000 fffff800`038e4363
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
21 Nov 2010   #3
b82a

Windows 7 Ultimate x64
 
 

Hmm, today i got bsod "BUGCODE_USB_DRIVER" and now i going to try what you say.
Quote:
Virtual Ethernet adapters are having problems. Is this deliberate? If so, why?
Yes, it is deliberate, because i often use virtual machines and i need internet on it.

Translate:
Quote:
Symptom:[IMG]res://wdc.dll/error.gif[/IMG]
The device is disabled
. Reason: The device is disabled and can not work properly. Information: Device VMware Virtual Ethernet Adapter for VMnet1 disabled. If this device is no longer used, perhaps intentionally disabled. Plug and Play IDs for this device: 13.Resolution:1. Determine whether the device.
2. If you want the device turn it on in device manager.
3. If the device is not required, it can do not turn it on.Associated: Explanation of error codes, which forms the Device Manager
Device Manager in Windows
Quote:
Please uninstall Daemon Tools/Alcohol 120%.
But i need Daemon Tools.
My System SpecsSystem Spec
.

21 Nov 2010   #4
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Daemon Tools is a well documented cause of BSOD's with Win 7. You do not need it if it is the cause of your BSOD's. As an alternative that does not use the sptd.sys driver, try MagicDisc, Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview. Follow USASMA's advice and uninstall Daemon Tools then run the sptd uninstaller: DuplexSecure - FAQ - Remove 64 bit sptd.sys
My System SpecsSystem Spec
22 Nov 2010   #5
b82a

Windows 7 Ultimate x64
 
 

Hmm, i just updated
Quote:
systormwrb.sys Sun Nov 04 12:25:56 2007 (472E00A4)
- Cyber Snipa/Flexiglow WarBoard Game Controller
- Driver Reference

adfs.SYS Mon Nov 03 11:48:14 2008 (490F2B4E)
- Adobe File System Filter driver
- Driver Reference
DgiVecp.sys Thu Oct 30 23:38:29 2008 (490A7DB5)
- IEEE-1284 parallel class driver for ECP, Byte, and Nibble modes - Device Guys or Samsung
- Driver Reference

SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
- Samsung printer driver
- Driver Reference
this drivers and bsods stopped. Do I need to do something else?
My System SpecsSystem Spec
22 Nov 2010   #6
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by b82a View Post
Hmm, i just updated
Quote:
systormwrb.sys Sun Nov 04 12:25:56 2007 (472E00A4)
- Cyber Snipa/Flexiglow WarBoard Game Controller
- Driver Reference

adfs.SYS Mon Nov 03 11:48:14 2008 (490F2B4E)
- Adobe File System Filter driver
- Driver Reference
DgiVecp.sys Thu Oct 30 23:38:29 2008 (490A7DB5)
- IEEE-1284 parallel class driver for ECP, Byte, and Nibble modes - Device Guys or Samsung
- Driver Reference

SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
- Samsung printer driver
- Driver Reference
this drivers and bsods stopped. Do I need to do something else?
If these drivers are the updated drivers, they are still way obsolete. For third party drivers, July 13, 2009 is the date of Win 7 compatible drivers. Any third party driver dated prior to July 13, 2009 is out of date. There are some exceptions. Some drivers date 2009 but prior to July 13th are Vista drivers and will work with Win 7.

There is no Win 7 compatible update, as far as I have been able to find, for SSPORT.sys. This driver is an XP driver - obsolete. It belongs to a Samsung utility. The printer will work with Win 7; but this utility will not. Using Windows explorer, navigate to C:\Windows\System32\Drivers, locate this driver and rename it from .sys to .old. Reboot and it will not load.

The rest of those drivers in your list are also obsolete and will come back to cause you trouble. Rename them as instructed above. Renaming drivers will break the programs or hardware they are associated with. Uninstalling the obsolete software or hardware is the preferred way to go.

Win 7 is not an evolution from XP; it is a totally new OS. Hardware and software designed for XP is not going to work with Win 7. You have to have programs designed for Win 7 - updated versions or new software. Running XP software invites continued trouble.
My System SpecsSystem Spec
28 Nov 2010   #7
b82a

Windows 7 Ultimate x64
 
 

Heh, because my bsod's resumed now i'm here again.
New information:
I remembered that bsods started when i bought new mouse Razer Deathadder and installed drivers for it. Now sometimes i've got a problems with it. Sensetivity of mouse changing by itself and sometimes it cursor just no moves. But now i've got bsod when i run Firefox immediately after my pc booted up. (If i run game for example, play some time and then run Firefox - its okay.)

I unistalled daemon tools, removed stpd driver and trying to use magicIso. Waiting for the result.
My System SpecsSystem Spec
28 Nov 2010   #8
usasma
Microsoft MVP

 
 

Temporarily remove Razer devices and software and see if that helps. Often we see BSOD problems with these devices, but it's not 100% certain if it's a hardware compatibility issue or a driver issue.
My System SpecsSystem Spec
07 Dec 2010   #9
b82a

Windows 7 Ultimate x64
 
 

Now i can get BSOD any time anywhere. Yesterday i got 5 bsods when my PC start and i use Recovery System to fix booting. Its so bad and i dont know what to do
My System SpecsSystem Spec
07 Dec 2010   #10
usasma
Microsoft MVP

 
 

May we see the memory dump files? They may have clues as to the problem.
My System SpecsSystem Spec
Reply

 Win 7 BSOD




Thread Tools



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 11:11.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App