Windows 7: Blue Screen in windows 7 64 bit

DaxJedi · 18 Nov 2010

Hello thanks in advance for your assistance and patience. Pls find uploaded my file zipped with system info & mini dump files as per your instructions made with Sf tool. awaiting yours eargly rgds.daxjedi

zigzag3143 · 18 Nov 2010

Quote: Originally Posted by DaxJedi

Hello thanks in advance for your assistance and patience. Pls find uploaded my file zipped with system info & mini dump files as per your instructions made with Sf tool. awaiting yours eargly rgds.daxjedi

Hi DJ

Ok where to start? there are abt 4 problems (all easy to get rid of).

1-SPTD.SYS

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

2- ASACPI.SYS the 2005 version almost always cashes.

ASACPI.sys Sun Mar 27 22:30:36 2005

Quote:

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

3- Memory corruption-- This may have been caused by the two above problems but to be safe run a memory test.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Seven Forums\111810-24804-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
Debug session time: Wed Nov 17 21:58:56.711 2010 (GMT-5)
System Uptime: 0 days 1:15:17.724
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 1102c3, 3, 9e22c}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

1: kd> !znzlyze -v
No export znzlyze found
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001102c3, page frame number
Arg3: 0000000000000003, current page state
Arg4: 000000000009e22c, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  memtest.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f6538c to fffff80002ed5740

STACK_TEXT:  
fffff880`058defb8 fffff800`02f6538c : 00000000`0000004e 00000000`00000099 00000000`001102c3 00000000`00000003 : nt!KeBugCheckEx
fffff880`058defc0 fffff800`02f476a9 : 00000000`00000000 fffff680`006018e8 00000000`00000000 fffff700`015fcff8 : nt!MiBadShareCount+0x4c
fffff880`058df000 fffff800`02f06381 : 00000000`00000000 fffff680`00601ff8 fffffa80`04669b30 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x31ed3
fffff880`058df1b0 fffff800`02f170da : 00000000`00000000 00000000`fffaffff fffffa80`00000000 fffffa80`04669b30 : nt!MiDeleteVirtualAddresses+0x408
fffff880`058df370 fffff800`02ed4993 : ffffffff`ffffffff 00000000`0008b170 00000000`0008b168 fffff900`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`058df460 00000000`76ecff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008b138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ecff3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f6538c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------

4-old drivers --- update at least these

Code:

ComproHID64.sys        fffff880`045f4380    0x00002380    9/30/2007 20:56:11            0x470053bb    fffff880`045f2000                
ISODrv64.sys        fffff880`03e84000    0x0001c000    11/2/2007 22:21:18            0x472be92e    fffff880`03e68000                
MTiCtwl.sys        fffff880`01bfa000    0x00009000    11/4/2008 02:40:50            0x490ffc82    fffff880`01bf1000

How To Find Drivers:

Quote:

- 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.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

DaxJedi · 18 Nov 2010

Hi Zigzag you made my day...frankly i was desperated. Now it seems to be the light at the end of tunnel I've done all I was told but the memtest so I'll check that today. One question regarding this test...is it really necessary to check both slots individually, with each memory card and so on...? thanks mate. rgds

DaxJedi · 19 Nov 2010

hello Zigzag Blue screen problem solved.However, from time to time win get stuck, and I have to restart pc an everything is ok. Do you know what could it be?tks/rgds

DaxJedi · 20 Nov 2010

Hello Zigzag, unfortunately another Blue Screen appeared...here is once again the attachments requested showing system info + file from the crash. tks for your usual help.rgds

zigzag3143 · 20 Nov 2010

Quote: Originally Posted by DaxJedi

Hello Zigzag, unfortunately another Blue Screen appeared...here is once again the attachments requested showing system info + file from the crash. tks for your usual help.rgds

DJ

Well still memory corruption, possibly caused by CI.dll (which is a browser helper object).

I still dont know the results of the last memtest.

1-run memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

2-Run a system file check to verify and repair system files

SFC /SCANNOW Command - System File Checker

If after the above two you continue to get BSOD's I would also run driver verifier to find out what driver is causing it

Beyond that, please run Verifier with these settings:

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

Using Driver Verifier to identify issues with Windows drivers for advanced users

DaxJedi · 21 Nov 2010

Thanks ZZ I'll try everything you told me, and let you now results...appreciate your help! rgds

DaxJedi · 21 Nov 2010

Hello ZZ a little problem but not so...just appeared. When I try to use ISO burner, I find out that the DVD rom is not available I can not either reproduce or do something with the DVD rom...I must have happened something when I installed Demon tolls...let me know if there is any other Tread here in this website...i was about to make dvd image memtest dvd and I found this problem...getting crazy here. tks and rgds

DaxJedi · 21 Nov 2010

Hello ZZ I jumped to the step two because as you know my dvd rom is not longer working... I´ve done everything what you said in the step 2. But i've got the first blue screen, then I restarted then it got stuck in the "...windows starting screen..." , si i restarted again and the launching solution menu appeared. I went back to a previous point. And now it is "working". Now tell me something not clear for me should I use my PC for a 36 hs non stop...that parts was not quite clear for me. thanks mate! thanks for your patience. rgds

DaxJedi · 23 Nov 2010

Hello ZZ after 36 hs runnig only two Blue screen after using the verifier completing this procedure

---quote----------

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.

-----unquote------------

I can not perform the memtest since my DVD rom is not working I started a new thread with that problem here but I have no answer so far. tks / rgds

Windows 7: Blue Screen in windows 7 64 bit

Blue Screen in windows 7 64 bit problems?