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: BSOD - doing us instructed

21 Sep 2010   #1
minkmink

Windows 7 Ultimate x64
 
 
BSOD - doing us instructed

-x64 ultimate
-not the original installed OS on the system
-full retail version

- What is the age of system (hardware)? 1.5 years - What is the age of OS installation? 2 days. first time i installed it. b4 i had windows xp

this is the last error code i got:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1037

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8004812060
BCP3: FFFFF80004139518
BCP4: FFFFFA8003FB9780
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

------------------
System Information
------------------
Time of this report: 9/22/2010, 00:47:15
Machine name: YOAVGS-PC
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Language: Hebrew (Regional Setting: Hebrew)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: EP43-DS3L
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz (4 CPUs), ~2.3GHz
Memory: 4096MB RAM
Available OS Memory: 4094MB RAM
Page File: 1584MB used, 6602MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode




My System SpecsSystem Spec
.
22 Sep 2010   #2
usasma
Microsoft MVP

 
 

D-Link Wireless G DWA-110 USB Adapter is known to cause issues if not using Win7 drivers. Also, they are not as powerful or reliable as a wireless card that plugs into the motherboard. I would suggest upgrading to one of those instead.

Please remove Daemon Tools as it is known to cause issues with Win7 in some cases. Once we're finished troubleshooting feel free to reinstall it.

Please uninstall the ATI Catalyst Control Center as it has been known to cause issues in some Win7 systems.

Please update your Samsung printer drivers as one component of it is from 2005:
Quote:
SSPORT.sys Thu Aug 11 19:07:32 2005 (42FBDA34)
If unable to update this 2005 driver, uninstall the printer until we're finished troubleshooting.

There are:
- 7 memory dumps from the last 2 days
- 6 different BSOD error messages
- 4 different causes are blamed.

This is most likely a hardware problem, but it's impossible to rule out software/driver issues (to include incompatibilities) with this few dump files.
- Run the system for a while after completing the steps above to see if that has fixed the BSOD's
- If the BSOD's recur, please run Driver Verifier according to these instructions:
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
While waiting for a reply, please try these free hardware diagnostics/stress tests:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:
Quote:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Quote:
Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- 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. (run all 3 if you find a problem and note how long it takes to error out with each)
- "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).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
Quote:
Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - http://nvworld.ru/utilities/vmt/
Artifact Locator - http://nvworld.ru/utilities/alocator/
Sorry, but I don't read the language that this website is made in.
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 21 18:15:48.105 2010 (UTC - 4:00)
System Uptime: 0 days 3:47:58.697
Probably caused by : atapi.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`04812060 fffff800`04139518 fffffa80`03fb9780
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 21 14:26:45.521 2010 (UTC - 4:00)
System Uptime: 0 days 2:56:45.113
BugCheck FE, {8, 6, b, fffffa80055c3640}
Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
Bugcheck code 000000FE
Arguments 00000000`00000008 00000000`00000006 00000000`0000000b fffffa80`055c3640
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep 20 13:33:26.985 2010 (UTC - 4:00)
System Uptime: 0 days 3:10:46.951
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`028f935f 00000000`00000000 ffffffff`ffffffff
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep 20 10:21:43.868 2010 (UTC - 4:00)
System Uptime: 0 days 3:00:45.834
Probably caused by : atapi.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`047ec680 fffff800`00b9c518 fffffa80`03c3c820
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep 20 07:20:20.564 2010 (UTC - 4:00)
System Uptime: 0 days 6:22:33.546
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`028e735f fffff880`03b4f020 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep 20 00:57:03.717 2010 (UTC - 4:00)
System Uptime: 0 days 2:49:59.309
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00003222`9430694d 00000000`00000002 00000000`00000000 fffff800`02976a8f
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 19 22:06:19.968 2010 (UTC - 4:00)
System Uptime: 0 days 5:04:42.935
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f72 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgchsva.exe
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`00008fd8 b4d00000`2aaad035 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
22 Sep 2010   #3
minkmink

Windows 7 Ultimate x64
 
 
one more piece of information

thanks, but one more piece of information before i start trying all of your suggestions.

most of the BSOD's happened when the computer came back from sleep mode. this morning i turned off the sleep mode option to "NEVER", and it didn't crash since this morning.

does this piece of information gives you a better clue of the solution?
My System SpecsSystem Spec
.

22 Sep 2010   #4
Tews

64-bit Windows 8.1 Pro
 
 

Do as usasma suggests ... he is our resident expert here and his advice is spot on!
My System SpecsSystem Spec
22 Sep 2010   #5
usasma
Microsoft MVP

 
 

Thanks Tews!

There may be further issues - it's not unheard of for us to fix one problem and that will reveal another.

FYI - the sleep transition has become very complex in the latest versions of Windows. In XP, most issues with sleep transitions could be traced to video driver issues. With Win7, there are issues with video and with the storage controllers (and I suspect a lot of other stuff).

In my case, I had an Asus P6T Deluxe mobo with a RAID card - and countless BSOD's when trying to sleep. After dealing with the RAID card compatibility (and it's drivers) and the drivers of the P6T Deluxe I still got sleep related BSOD's for almost a year. I recently purchased a P6T Deluxe v2 mobo and the sleep issues have vanished!!! So, in my case, it was the motherboard that was at fault.
My System SpecsSystem Spec
Reply

 BSOD - doing us instructed




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