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: Blue Screen's again


11 Nov 2010   #1

Windows 7 X64
 
 
Blue Screen's again

I thought my bluescreen problem was solved a few weeks agao but now it have started again.

17 passes of memtest without any errors.
Tested the harddrives without any errors.
the temperature of the system is very low so that should not be an issue.
The crashes comes when the system load is very low.

My System SpecsSystem Spec
.

12 Nov 2010   #2
Microsoft MVP

 
 

Your Lenovo EasyCamera driver is from 2008, please update to a Windows 7 compatible version of the program.
(SMIEXP.SYS Wed Jan 16 05:06:19 2008 (478DD71B))

As the dump file doesn't point out anything in particular, I'd suggest running 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/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"
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, Windows 7):
        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.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 11 15:10:50.177 2010 (UTC - 5:00)
System Uptime: 0 days 4:59:21.051
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ec0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  pacman1.exe
Bugcheck code 00000050
Arguments fffff960`0054b138 00000000`00000008 fffff960`0054b138 00000000`00000002
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
My System SpecsSystem Spec
13 Nov 2010   #3

Windows 7 X64
 
 

OK. I can't find any newer driver for the webcam so I will remove it for now and enable driververifier
However I got one more bsod that I will post here.
My System SpecsSystem Spec
.


13 Nov 2010   #4

Windows 7 X64
 
 

And two minidumps with driver verifier enabled
My System SpecsSystem Spec
13 Nov 2010   #5

Windows 7 X64
 
 

And another one
My System SpecsSystem Spec
13 Nov 2010   #6
Microsoft MVP

 
 

Please run these free stress tests (without Driver Verifier running):
Quote:
Quote:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in 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 - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / VMT
Artifact Locator - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / Artifact Locator
Sorry, but I don't read the language that this website is made in.
Also, run this:
Quote:
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).
Copy/paste the results into your next post.
Then, if you haven't identified any problems, please run Driver Verifier again - this time select ONLY the Microsoft drivers (and the rest of the settings being the same). Let it generate 2 or 3 BSOD's. The point here is to see if we get consistent Windows errors (then Windows is likely to be blamed) - or more random errors (like we have been getting)(which blames hardware/compatibility most likely).

Compatibility checks: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

Hardware Troubleshooting Via System Stripdown: Hardware Troubleshooting Via System Stripdown

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 11:15:14.052 2010 (UTC - 5:00)
System Uptime: 0 days 2:04:46.552
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )
BUGCHECK_STR:  0xC1_23
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  TrustedInstall
Bugcheck code 000000C1
Arguments fffff980`18760c10 fffff980`1876076a 00000000`00a103e8 00000000`00000023
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 08:55:18.041 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:32.916
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )
BUGCHECK_STR:  0xC1_23
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  MsMpEng.exe
Bugcheck code 000000C1
Arguments fffff980`0b6b2c10 fffff980`0b6b256a 00000000`003d03e8 00000000`00000023
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 08:51:36.905 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:25.779
Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+1ad )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments fffffa80`06de8ef0 00000000`00000002 00000000`00000001 fffff800`01ca83cd
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 07:23:40.137 2010 (UTC - 5:00)
System Uptime: 0 days 0:44:44.637
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffff880`065e20e0 fffff880`065e20e0 fff1f5fb`fff1f5fb
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
  
My System SpecsSystem Spec
13 Nov 2010   #7

Windows 7 X64
 
 

Regarding checkdisk it reports no problem:

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
261632 file records processed. File verification completed.
302 large file records processed. 0 bad file records processed. 28 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
321658 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
261632 file SDs/SIDs processed. Cleaning up 217 unused index entries from index $SII of file 0x9.
Cleaning up 217 unused index entries from index $SDH of file 0x9.
Cleaning up 217 unused security descriptors.
Security descriptor verification completed.
30014 data files processed. CHKDSK is verifying Usn Journal...
37264992 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
261616 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
23305464 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
146418687 KB total disk space.
52719280 KB in 208595 files.
107580 KB in 30015 indexes.
0 KB in bad sectors.
369971 KB in use by the system.
65536 KB occupied by the log file.
93221856 KB available on disk.
4096 bytes in each allocation unit.
36604671 total allocation units on disk.
23305464 allocation units available on disk.
Internal Info:
00 fe 03 00 1c a4 03 00 4e 25 06 00 00 00 00 00 ........N%......
57 0b 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 W...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
13 Nov 2010   #8

Windows 7 X64
 
 

After a few sec of prime95 I
get "FATAL ERROR: Rounding was 0.5 Expected less than 0.4"
Hardware failure detected, consult stress.txt file

Torture Test completed 0 tests in 0 minutes -1 error 0 warnings
Worker stopped.

I get this for both worker 2 and worker 3

Does this mean that my cpu is broken?
My System SpecsSystem Spec
13 Nov 2010   #9
Microsoft MVP

 
 

No it doesn't mean that your CPU is broken - but it does indicate a problem with your hardware (somewhere).
Most times the blend test in Prime 95 points to memory issues. Since you've run MemTest we can assume that your RAM is good - but we still need to test your video RAM (at a minimum).

Please try the other 2 stress tests that I linked to above (FurMark and Video Memory Stress Test).
My System SpecsSystem Spec
13 Nov 2010   #10

Windows 7 X64
 
 

Hmm i start to suspect the ram anyway. If i over volt the ram it seems to pass the first tests in blend mode.
THe memory is specified to 1.65 and in 1.68 it seems to pass the first tests.

Regarding the video ram, it's an onboard graphic card so it should use the same memory as was thested during the memtest.
I have also tried two other graphic cards when having bluescreens 3 weeks agao so I don't think it's a problem with the graphic card.
My System SpecsSystem Spec
Reply

 Blue Screen's again




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:08 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