Window 7 Crash in Lenovo Y450 4189

[spyhunter88]

I used Window 7 x86 with Enterprise, Professional, and now x64 Professional. Window crashed in all version I run. I don't know why, because it may crash anytime, when listen music, play game or simple like open word. This report is taken from x64 Professional.

I guess it come from my Card Graphic (G210M), driver's downloaded from NVIDIA, not from Lenovo because it's too old. Sometime it stops responding, I can see it when I use Accelerator Hardware in Browser.

Laptop Lenovo Y450 4189
Window 7 x64 Professional SP1, full retail version.

 

[zigzag3143]

I used Window 7 x86 with Enterprise, Professional, and now x64 Professional. Window crashed in all version I run. I don't know why, because it may crash anytime, when listen music, play game or simple like open word. This report is taken from x64 Professional.

I guess it come from my Card Graphic (G210M), driver's downloaded from NVIDIA, not from Lenovo because it's too old. Sometime it stops responding, I can see it when I use Accelerator Hardware in Browser.

Laptop Lenovo Y450 4189
Window 7 x64 Professional SP1, full retail version.

Memory corruption caused by a driver. Please run driver verifier to find out which.

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

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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

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.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\052211-39171-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`030a0650
Debug session time: Sat May 21 14:02:42.622 2011 (GMT-4)
System Uptime: 0 days 7:44:49.769
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800031b61c0, fffff88006559d60, 0}

Probably caused by : memory_corruption ( nt!MiPerformFixups+80 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031b61c0, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006559d60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiPerformFixups+80
fffff800`031b61c0 410fb603        movzx   eax,byte ptr [r11]

CONTEXT:  fffff88006559d60 -- (.cxr 0xfffff88006559d60)
rax=fffff8a00ba00000 rbx=fffff88007795000 rcx=fffff88007795000
rdx=0000000000000ff8 rsi=0000000006ca0000 rdi=0000000000000003
rip=fffff800031b61c0 rsp=fffff8800655a740 rbp=fa80046a183004c0
 r8=0000000000000ffc  r9=0000000000000fff r10=fffff88007795000
r11=fa80046a183004c0 r12=000000002c82a000 r13=fffff8a00ba00000
r14=fffffa8006dd7170 r15=0000000000164150
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MiPerformFixups+0x80:
fffff800`031b61c0 410fb603        movzx   eax,byte ptr [r11] ds:002b:fa80046a`183004c0=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800031b61c0

STACK_TEXT:  
fffff880`0655a740 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiPerformFixups+0x80


FOLLOWUP_IP: 
nt!MiPerformFixups+80
fffff800`031b61c0 410fb603        movzx   eax,byte ptr [r11]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiPerformFixups+80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

STACK_COMMAND:  .cxr 0xfffff88006559d60 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiPerformFixups+80

BUCKET_ID:  X64_0x3B_nt!MiPerformFixups+80

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

 

[spyhunter88]

Thank. After repeat amount 10 times, I found the driver is dtsoftbus01.sys from DT Soft Ltd, not from NVIDIA.

 

[usasma]

dtsoftbus01.sys is from Daemon Tools/Alcohol 120% - which is a known cause of BSOD's on Win7 systems.
Please do the following:
1 - uninstall Daemon Tools/Alcohol 120%
2 - download this free tool and use it to remove the sptd.sys driver that's the actual cause of the BSOD's: DuplexSecure - FAQ - Remove 64 bit sptd.sys

 

[spyhunter88]

I Uninstall this, and run DuplexSecure x64, but only Install Button is enable, Uninstall Button is disable. Comeback to Verifier, I don't see dtsoftbus01.sys anymore, may I complete?

 

[usasma]

If it's not able to be uninstalled, then it's most likely been taken out by the uninstaller.
To check, go to C:\Windows\System32\drivers and look for sptd.sys
Other than that, just wait to see if you get any further BSOD's.
Good luck!