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: Random BSOD During Computer Idle, Startup, and Basic Tasks

07 Mar 2012   #1
FruitdaleJake

Windows 7 Home Premium (x64) Service Pack 1 (build 7601)
 
 
Random BSOD During Computer Idle, Startup, and Basic Tasks

I'm having some issues with my computer crashing multiple times throughout the day. Ever since I attempted to install iTunes last night (March 5, 2012) my computer has been crashing with multiple different error messages like:

0x0000003b
0x00000025
0x0000007e

0x0000003b is definitely the one that shows up the most though. I have tried multiple different attempts in fixing this including updating all my drivers, running disk cleanups and defrags, registry cleanups, and security scans and nothing seems to be helping. Now my ATI Catalyst for my graphics card isnt starting correctly on startup.

My computers specs are:

Windows 7 Home Premium (x64) Service Pack 1 (build 7601)
Gigabyte Technology Co., Ltd. GA-770T-USB3
3.20 gigahertz AMD Phenom II X6 1090T
Hitachi HDS721010CLA332 [Hard drive] (1000.20 GB)
ATI Radeon HD 5700 Series [Display adapter]

You guys are my last hope before I wipe my hard drive and start over with my windows 7 disk and I really don't want to sit around for days reinstalling and downloading games with how huge they are now =P


My System SpecsSystem Spec
.
07 Mar 2012   #2
FruitdaleJake

Windows 7 Home Premium (x64) Service Pack 1 (build 7601)
 
 

As of now there haven't been a crash for an hour or so. Still watching for any new BSOD error codes that may pop up.

Edit: NVM my computer just crashed after attempting to open a game. Error code was 0x0000003b again.
My System SpecsSystem Spec
07 Mar 2012   #3
writhziden

Windows 7 Home Premium 64 Bit
 
 

Possible out of date drivers:
Code:
tifsfilt	fffff880`09140000	fffff880`09157000	Wed Aug 29 06:37:29 2007 (46d56889)	0001e5c2		tifsfilt.sys
timntr	fffff880`018b8000	fffff880`01968000	Wed Aug 29 06:38:23 2007 (46d568bf)	000b2038		timntr.sys
tdrpman	fffff880`01a04000	fffff880`01a98000	Mon Nov 12 06:36:33 2007 (473856e1)	00091de8		tdrpman.sys
snapman	fffff880`01aa0000	fffff880`01adb000	Thu Nov 22 01:19:33 2007 (47453b95)	00043f7b		snapman.sys
tifsfilt.sys
timntr.sys
tdrpman.sys
snapman.sys


The following drivers can also cause problems:
Code:
AODDriver2	fffff880`03a72000	fffff880`03aa3000	Wed Jun 15 02:38:35 2011 (4df86f8b)	00012df4		AODDriver2.sys
dtsoftbus01	fffff880`019b4000	fffff880`019fd000	Fri Jan 13 06:45:46 2012 (4f10358a)	00046d1e		dtsoftbus01.sys
Remove the appropriate programs:
Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\FruitdaleJake\Windows_NT6_BSOD_jcgriff2\030612-25147-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0365a000 PsLoadedModuleList = 0xfffff800`0389f670 Debug session time: Tue Mar 6 21:55:19.526 2012 (UTC - 7:00) System Uptime: 0 days 0:04:14.743 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800039c1961, fffff8800807edb0, 0} Probably caused by : ntkrnlmp.exe ( nt!ObLogSecurityDescriptor+c2 ) Followup: MachineOwner --------- 5: 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: fffff800039c1961, Address of the instruction which caused the bugcheck Arg3: fffff8800807edb0, 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!ObLogSecurityDescriptor+c2 fffff800`039c1961 8b4614 mov eax,dword ptr [rsi+14h] CONTEXT: fffff8800807edb0 -- (.cxr 0xfffff8800807edb0) rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000011 rdx=00000000805dc8eb rsi=fffdf8a00180a500 rdi=00000000805dc97d rip=fffff800039c1961 rsp=fffff8800807f790 rbp=fffffa8005312b60 r8=0000000000000068 r9=fffff8a0036668a4 r10=fffff8a0036668a4 r11=0000000000000084 r12=fffff80003883090 r13=0000000000000000 r14=fffff80003883098 r15=fffff8a003666820 iopl=0 nv up ei ng nz ac pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010293 nt!ObLogSecurityDescriptor+0xc2: fffff800`039c1961 8b4614 mov eax,dword ptr [rsi+14h] ds:002b:fffdf8a0`0180a514=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800039c1961 STACK_TEXT: fffff880`0807f790 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObLogSecurityDescriptor+0xc2 FOLLOWUP_IP: nt!ObLogSecurityDescriptor+c2 fffff800`039c1961 8b4614 mov eax,dword ptr [rsi+14h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ObLogSecurityDescriptor+c2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 STACK_COMMAND: .cxr 0xfffff8800807edb0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ObLogSecurityDescriptor+c2 BUCKET_ID: X64_0x3B_nt!ObLogSecurityDescriptor+c2 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\FruitdaleJake\Windows_NT6_BSOD_jcgriff2\030612-16504-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03612000 PsLoadedModuleList = 0xfffff800`03857670 Debug session time: Tue Mar 6 21:19:49.513 2012 (UTC - 7:00) System Uptime: 0 days 0:01:02.370 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff8800c11cb28, fffff8800c11c380, fffff800036a4915} Probably caused by : Ntfs.sys ( Ntfs!NtfsReadMftRecord+b2 ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff8800c11cb28 Arg3: fffff8800c11c380 Arg4: fffff800036a4915 Debugging Details: ------------------ EXCEPTION_RECORD: fffff8800c11cb28 -- (.exr 0xfffff8800c11cb28) ExceptionAddress: fffff800036a4915 (nt!CcGetVirtualAddress+0x0000000000000105) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff8800c11c380 -- (.cxr 0xfffff8800c11c380) rax=000000000000003d rbx=000000000000000e rcx=0000000000000012 rdx=0000000009300000 rsi=ff00fa80039d6ee0 rdi=0000000000000001 rip=fffff800036a4915 rsp=fffff8800c11cd60 rbp=fffffa80049b0e00 r8=0000000000000000 r9=0000000000f59800 r10=0000000000000800 r11=0000000000000001 r12=0000000000019800 r13=0000000000000001 r14=0000000000019800 r15=0000000000000001 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!CcGetVirtualAddress+0x105: fffff800`036a4915 f00fc17e10 lock xadd dword ptr [rsi+10h],edi ds:002b:ff00fa80`039d6ef0=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: wmpnetwk.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c1100 ffffffffffffffff FOLLOWUP_IP: Ntfs!NtfsReadMftRecord+b2 fffff880`012fa1e2 84c0 test al,al FAULTING_IP: nt!CcGetVirtualAddress+105 fffff800`036a4915 f00fc17e10 lock xadd dword ptr [rsi+10h],edi BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff8000398b642 to fffff800036a4915 STACK_TEXT: fffff880`0c11cd60 fffff800`0398b642 : fffff880`00000001 00000000`00f59800 fffff880`0c11ceb8 fffff880`0c11ceb0 : nt!CcGetVirtualAddress+0x105 fffff880`0c11cdf0 fffff880`012fa1e2 : fffffa80`04a9d200 fffff880`016d0160 00000000`000002db fffff880`0000000e : nt!CcMapData+0xd2 fffff880`0c11ceb0 fffff880`012f5d5c : fffffa80`061b0ce0 fffffa80`04aa9180 fffff8a0`029ef018 fffff8a0`0318cf01 : Ntfs!NtfsReadMftRecord+0xb2 fffff880`0c11cf60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsLookupInFileRecord+0x6c SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: Ntfs!NtfsReadMftRecord+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b STACK_COMMAND: .cxr 0xfffff8800c11c380 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsReadMftRecord+b2 BUCKET_ID: X64_0x24_Ntfs!NtfsReadMftRecord+b2 Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\FruitdaleJake\Windows_NT6_BSOD_jcgriff2\030612-17955-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0341b000 PsLoadedModuleList = 0xfffff800`03660670 Debug session time: Tue Mar 6 16:43:14.409 2012 (UTC - 7:00) System Uptime: 0 days 0:00:57.627 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff880070996e8, fffff8800ad95650, 0} Probably caused by : atikmpag.sys ( atikmpag+306e8 ) Followup: MachineOwner --------- 1: 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: fffff880070996e8, Address of the instruction which caused the bugcheck Arg3: fffff8800ad95650, 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: atikmpag+306e8 fffff880`070996e8 ff5008 call qword ptr [rax+8] CONTEXT: fffff8800ad95650 -- (.cxr 0xfffff8800ad95650) rax=fffff8800706c030 rbx=fffffa8003a07040 rcx=fffffa8003a07040 rdx=fffff8800ad96050 rsi=fffff8800ad961d0 rdi=fffff8a00293a05c rip=fffff880070996e8 rsp=fffff8800ad96030 rbp=00000000c0000001 r8=0000000000000000 r9=fffffa80054ab040 r10=0000000000000594 r11=fffff8800ad96050 r12=fffff8a00293a010 r13=0000000000000000 r14=fffffa80056046c0 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 atikmpag+0x306e8: fffff880`070996e8 ff5008 call qword ptr [rax+8] ds:002b:fffff880`0706c038=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: sidebar.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880070996e8 STACK_TEXT: fffff880`0ad96030 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmpag+0x306e8 FOLLOWUP_IP: atikmpag+306e8 fffff880`070996e8 ff5008 call qword ptr [rax+8] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmpag+306e8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4edd79fe STACK_COMMAND: .cxr 0xfffff8800ad95650 ; kb FAILURE_BUCKET_ID: X64_0x3B_atikmpag+306e8 BUCKET_ID: X64_0x3B_atikmpag+306e8 Followup: MachineOwner ---------
  4. Loading Dump File [D:\Kingston\BSODDmpFiles\FruitdaleJake\Windows_NT6_BSOD_jcgriff2\030612-19593-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03400000 PsLoadedModuleList = 0xfffff800`03645670 Debug session time: Tue Mar 6 16:41:35.298 2012 (UTC - 7:00) System Uptime: 0 days 0:03:32.516 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa0007310b80, 0, fffff8000357db2c, 7} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffa0007310b80, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8000357db2c, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036af100 fffffa0007310b80 FAULTING_IP: nt!MiEmptyPageAccessLog+dc fffff800`0357db2c 488b08 mov rcx,qword ptr [rax] MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: WerFault.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800c5907f0 -- (.trap 0xfffff8800c5907f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa0007310b80 rbx=0000000000000000 rcx=0000000000000010 rdx=fffff8a0038f42f8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000357db2c rsp=fffff8800c590980 rbp=0000000000000000 r8=fffffa8003f40001 r9=fffffa8003f7d048 r10=fffffa8007310b00 r11=fffffa80064f5a30 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!MiEmptyPageAccessLog+0xdc: fffff800`0357db2c 488b08 mov rcx,qword ptr [rax] ds:fffffa00`07310b80=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003427347 to fffff8000347cc40 STACK_TEXT: fffff880`0c590688 fffff800`03427347 : 00000000`00000050 fffffa00`07310b80 00000000`00000000 fffff880`0c5907f0 : nt!KeBugCheckEx fffff880`0c590690 fffff800`0347ad6e : 00000000`00000000 fffffa00`07310b80 fffffa80`02424600 00000000`0065f001 : nt! ?? ::FNODOBFM::`string'+0x44711 fffff880`0c5907f0 fffff800`0357db2c : 00000000`00000000 fffffa80`07310b40 fffffa80`064f5a30 00000000`0065f000 : nt!KiPageFault+0x16e fffff880`0c590980 fffff800`034f14d5 : fffffa80`03f43060 00000003`00000000 00000000`0065f001 fffffa00`07310b80 : nt!MiEmptyPageAccessLog+0xdc fffff880`0c5909f0 fffff800`03794221 : fffffa80`068b0b50 00000000`00000000 fffffa80`07310b80 fffffa80`07310b80 : nt! ?? ::FNODOBFM::`string'+0x3b9a6 fffff880`0c590b10 fffff800`03794623 : 0000007f`00000000 00000000`01d40000 fffffa80`00000001 00000000`000ab701 : nt!MiUnmapViewOfSection+0x1b1 fffff880`0c590bd0 fffff800`0347bed3 : 00000000`00000000 00000000`02398488 fffffa80`03f43060 00000000`0239847c : nt!NtUnmapViewOfSection+0x5f fffff880`0c590c20 00000000`770c15ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000aabb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770c15ba STACK_COMMAND: kb FOLLOWUP_IP: nt!MiEmptyPageAccessLog+dc fffff800`0357db2c 488b08 mov rcx,qword ptr [rax] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiEmptyPageAccessLog+dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiEmptyPageAccessLog+dc BUCKET_ID: X64_0x50_nt!MiEmptyPageAccessLog+dc Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
  2. Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...
  3. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
  4. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.
  • If you are overclocking any hardware, please stop.

  • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

  • Run the Hitachi Drive Fitness Test to check whether the drive is faulty.

  • Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

  • Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.
    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    8. Restart your computer after uninstalling drivers for all display cards
    9. Install the latest driver for the display cards once Windows starts

    Alternatively:
    1. Login as an adminstrative user
    2. Download the latest drivers for your display card(s)
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Expand Display adapters
    8. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer after uninstalling drivers for all display cards
    10. Install the latest driver for the display cards once Windows starts

  • Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.
My System SpecsSystem Spec
.

Reply

 Random BSOD During Computer Idle, Startup, and Basic Tasks




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD's on idle computer, mostly 0x00000124
I have a computer running as my home server with Plex, etc., and every now and again (it might be a few days in between, or just an hour) it gets a BSOD. It's just a "server" so it sits there with very little interaction from me. I've stripped it down to the bare components, done memtest86 on the...
BSOD Help and Support
Random BSOD 117 Even when computer is idle.
I get 2-4 times in a 3 hour period a 117 BSOD. This can happen right after a reboot... or after hours of use. There is no pattern. Sometimes a game is open- sometime a browser is open. I've tried many driver versions... re-installed the OS from scratch. Nothing I do seems to resolve it for...
BSOD Help and Support
Random BSOD while computer IDLE and Gaming
Hi, I have gone through the process of trying to figure out my BSOD problems. I ended up reinstalling Windows 7. After installing the latest drivers for everything I thought I had the problem solved.. not so much. The problems are still plaguing me, so I find myself here. Here is my uploaded...
BSOD Help and Support
Random BSOD when computer idle and in use
Hello my computer appears to BSOD randomly. I haven't really noticed any particular activity which set these off and am at a loss of what to do. I'm using a retail copy of windows 7 with service pack 1 and I have attached the BSOD files Many thanks
BSOD Help and Support
BSOD on random, playing games and computer idle
heres some mini dump files, i dont know how this works exactly, but ive gotten diffrent codes so far one was bccode d1 and there was another one also, and i have like 4 minidump files here i get different errors, hope u can help this really irritating. but yeah sometimes ill be playing games...
BSOD Help and Support
Random BSODs win7 while basic browsing / idle, never when gaming
I have been getting some random BSODs usually just while browsing the web, once while watching a streaming video in flash player or while the pc is idle and afk. But never while gaming or anything more intensive. Any help would be greatly appreciated. EDIT: I should add I ran prime95, and...
BSOD Help and Support


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 13:49.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App