Crashes and BSOD

Asni · 06 Oct 2010

I've got this Crashes and BSODs in the last few weeks, tryed everything I know to see if I could solve but I couldn't.

ps.: When the computer is loading something, at the headphone I can hear some strange noises, also when it just crashes if it is playing any sound the sound keeps repeting where it crashed.

Thanks for the help.
Asni

Asni · 07 Oct 2010

Update: Today for just watching videos on youtube my PC crashes.

usasma · 07 Oct 2010

This device isn't working properly:

Code:

PCI Simple Communications Controller    PCI\VEN_8086&DEV_3B64&SUBSYS_76361462&REV_06\3&11583659&0&B0    The drivers for this device are not installed.

Please visit the manufacturer of your PC/motherboard and download/install your chipset drivers immediately.
Also check in Device Manager for any other devices that have issues.

Please uninstall Alcohol 120%, it can cause BSOD's.

Please run Driver Verifier according to these directions:

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.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 14:58:43.330 2010 (UTC - 4:00)
System Uptime: 0 days 2:16:11.469
Probably caused by : win32k.sys ( win32k!xxxUpdateInputHangInfo+5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  League of Lege
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff960`000e3df5 fffff880`0842c020 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 12:41:34.862 2010 (UTC - 4:00)
System Uptime: 0 days 1:34:35.392
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::AddCommitment+4a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`041cb322 fffff880`03366698 fffff880`03365f00
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct  5 00:24:59.291 2010 (UTC - 4:00)
System Uptime: 0 days 11:16:03.446
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ec0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
Bugcheck code 00000050
Arguments fffff800`03400000 00000000`00000000 fffffa80`044d19d6 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Asni · 07 Oct 2010

Thanks for the reply.

Please visit the manufacturer of your PC/motherboard and download/install your chipset drivers immediately.
Also check in Device Manager for any other devices that have issues.
Done.

Please uninstall Alcohol 120%, it can cause BSOD's.
Done.

Please run Driver Verifier according to these directions:
Done.

The new memory dump file is attached.

Again, Thanks for the help.
Asni

zigzag3143 · 08 Oct 2010

Asni said:

Thanks for the reply.

Please visit the manufacturer of your PC/motherboard and download/install your chipset drivers immediately.
Also check in Device Manager for any other devices that have issues.
Done.

Please uninstall Alcohol 120%, it can cause BSOD's.
Done.

Please run Driver Verifier according to these directions:
Done.

The new memory dump file is attached.

Again, Thanks for the help.
Asni

this one was caused by your video driver. Re-install according to directions below

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

Let us know if you need further assistance.

Ken J

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\100810-15584-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Fri Oct  8 00:46:37.838 2010 (GMT-4)
System Uptime: 0 days 0:09:24.367
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88010516c65, fffff8800379f5e0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+6a6c65 )

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: fffff88010516c65, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800379f5e0, 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: 
nvlddmkm+6a6c65
fffff880`10516c65 488b5b68        mov     rbx,qword ptr [rbx+68h]

CONTEXT:  fffff8800379f5e0 -- (.cxr 0xfffff8800379f5e0)
rax=0000000000000077 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000077 rdi=fffff98012516e80
rip=fffff88010516c65 rsp=fffff8800379ffb0 rbp=0000000000000077
 r8=00000000000007ff  r9=0000000000000000 r10=0000000000000001
r11=fffff880037a0190 r12=0000000000000000 r13=0000000000000001
r14=fffff880037a0060 r15=000000006e76726d
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x6a6c65:
fffff880`10516c65 488b5b68        mov     rbx,qword ptr [rbx+68h] ds:002b:00000000`00000068=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff98013546f70 to fffff88010516c65

STACK_TEXT:  
fffff880`0379ffb0 fffff980`13546f70 : fffff880`1051750c 00000000`00002038 fffff880`1005b907 00000000`0000002e : nvlddmkm+0x6a6c65
fffff880`0379ffb8 fffff880`1051750c : 00000000`00002038 fffff880`1005b907 00000000`0000002e 0000000e`e0000000 : 0xfffff980`13546f70
fffff880`0379ffc0 00000000`00002038 : fffff880`1005b907 00000000`0000002e 0000000e`e0000000 00000000`00000000 : nvlddmkm+0x6a750c
fffff880`0379ffc8 fffff880`1005b907 : 00000000`0000002e 0000000e`e0000000 00000000`00000000 00000000`00000000 : 0x2038
fffff880`0379ffd0 00000000`0000002e : 0000000e`e0000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1eb907
fffff880`0379ffd8 0000000e`e0000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03bab000 : 0x2e
fffff880`0379ffe0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`03bab000 00000000`00000000 : 0xe`e0000000


FOLLOWUP_IP: 
nvlddmkm+6a6c65
fffff880`10516c65 488b5b68        mov     rbx,qword ptr [rbx+68h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+6a6c65

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c37918e

STACK_COMMAND:  .cxr 0xfffff8800379f5e0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_nvlddmkm+6a6c65

BUCKET_ID:  X64_0x3B_VRF_nvlddmkm+6a6c65

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

wish · 08 Oct 2010

Asni said:

Thanks for the reply.

Please visit the manufacturer of your PC/motherboard and download/install your chipset drivers immediately.
Also check in Device Manager for any other devices that have issues.
Done.

Please uninstall Alcohol 120%, it can cause BSOD's.
Done.

Please run Driver Verifier according to these directions:
Done.

The new memory dump file is attached.

Again, Thanks for the help.
Asni

Follow Ken advise to reinstall nVidia driver..

You have uninstalled Alcohol but its driver (sptd.sys) still remain , so remove that driver with SPTDinst.

These drivers also need to be updated :
Rt64win7.sys = Realtek NIC driver
RTKVHD64.sys = Realtek High Definition Audio

usasma · 08 Oct 2010

Please be aware that the driver issue can be a problem with the driver - or it's possible that there's a problem with the card itself.