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's (0x0000000D1 and 0x0000000F7)


25 Dec 2011   #1

Windows 7 Ultimate 32bit
 
 
Random BSOD's (0x0000000D1 and 0x0000000F7)

Ultimate 32bit - Retail version
Reinstalled it about 6 months ago, trying to fix this problem.

My hardware is about 2 years and 9 months old.

CPU - AMD Athlon(tm) 64 X2 Dual Core Processor
Memory - 4096MB RAM
Graphics card - NVIDIA GeForce 9600 GT
Monitor - HANNS-G HW173A, 1280x960
Hard drive - SAMSUNG HD322HJ ATA Device
Motherboard - ASUS M3N78-AM

Hello, and thank you for taking the time to look at this message.

I get BSOD's at pretty much random intervals. Sometime's when I'm playing a video game, but also once when my PC was restarting. I had the same issue (not sure if the BSOD's gave the same error though) a while ago, and removing my printers drivers fixed it. But now I get BSOD's again and the only thing that seems to link them is my event log giving me a Kernel-Power or WMI error.
The only 2 BSOD'S that I have the error code from are 0x0000000D1 and 0x0000000F7, will update this list when I get more (or post it when they stay the same).

Thank you in advance,

Alex.

My System SpecsSystem Spec
.

25 Dec 2011   #2

Windows 7 Home Premium 64 Bit
 
 

AVG is on your system and is known to cause blue screen errors on some systems. Remove it with AVG - Download tools and utilities and install Microsoft Security Essentials - Free Antivirus for Windows in its place, at least for testing purposes.

Code:
  1. BugCheck D1, {3ec, 4, 0, 928fe654} 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+f8654 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 000003ec, memory referenced Arg2: 00000004, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 928fe654, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 82971718 Unable to read MiSystemVaType memory at 829511a0 000003ec CURRENT_IRQL: 4 FAULTING_IP: nvlddmkm+f8654 928fe654 8b93ec030000 mov edx,dword ptr [ebx+3ECh] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: 80786aa8 -- (.trap 0xffffffff80786aa8) ErrCode = 00000000 eax=00000000 ebx=00000000 ecx=9293e700 edx=000000f4 esi=85188660 edi=00000002 eip=928fe654 esp=80786b1c ebp=80786b1c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nvlddmkm+0xf8654: 928fe654 8b93ec030000 mov edx,dword ptr [ebx+3ECh] ds:0023:000003ec=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 928fe654 to 828485cb STACK_TEXT: 80786aa8 928fe654 badb0d00 000000f4 00000000 nt!KiTrap0E+0x2cf WARNING: Stack unwind information not available. Following frames may be wrong. 80786b1c 9290529d 85188660 86d99b48 85188660 nvlddmkm+0xf8654 80786b68 928fe5aa 00000001 865d3cac 00000000 nvlddmkm+0xff29d 80786b80 9289530b 8650b478 865d3cac 865cf000 nvlddmkm+0xf85aa 80786b98 9289543c 00000000 92860777 00000000 nvlddmkm+0x8f30b 80786bc8 9203db14 92810c44 00000000 80786bec nvlddmkm+0x8f43c 80786bd8 9204dd59 86a1ea00 865d5920 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17 80786bec 828417ad 86a1ea00 865d5920 80786c18 dxgkrnl!DpiFdoLineInterruptRoutine+0x12 80786bec 8283fd91 86a1ea00 865d5920 80786c18 nt!KiInterruptDispatch+0x6d 80786d50 82a10f5e 8080b350 b16c12be 00000000 nt!KiXMMIZeroPagesNoSave+0x19 80786d78 82c1eba9 ffffffff 828c6ccd b391a266 nt!PspSystemThreadStartup+0x9e 80786d90 828b8219 82994433 8080b350 00000000 hal!KfLowerIrql+0x61 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+f8654 928fe654 8b93ec030000 mov edx,dword ptr [ebx+3ECh] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nvlddmkm+f8654 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49fa9243 FAILURE_BUCKET_ID: 0xD1_nvlddmkm+f8654 BUCKET_ID: 0xD1_nvlddmkm+f8654 Followup: MachineOwner ---------
  2. BugCheck D1, {63, 2, 8, 63} Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000063, memory referenced Arg2: 00000002, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 00000063, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 82bb6848 Unable to read MiSystemVaType memory at 82b95e20 00000063 CURRENT_IRQL: 2 FAULTING_IP: +3231656331343038 00000063 ?? ??? PROCESS_NAME: Steam.exe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 807e7de8 -- (.trap 0xffffffff807e7de8) ErrCode = 00000010 eax=85201000 ebx=807e7ec8 ecx=00000000 edx=00000000 esi=00000000 edi=00000063 eip=00000063 esp=807e7e5c ebp=82b3f3c4 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 00000063 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 00000063 to 82a8e5fb FAILED_INSTRUCTION_ADDRESS: +3231656331343038 00000063 ?? ??? STACK_TEXT: 807e7de8 00000063 badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 807e7e58 807c7120 00000000 807c7120 017d7840 0x63 807e7e70 82ad165d 00000000 807c7120 807c8a08 0x807c7120 807e7e88 82a57082 807c7120 807c7120 00000001 nt!PpmQueryTime+0x16 807e7f30 82b40f9a 807ca520 87d34534 807c8a00 nt!PpmSnapIdleAccumulation+0xb3 807e7f48 82ac51b5 807ca520 807c7120 00000000 nt!PpmPerfAction+0x25 807e7fa4 82ac5018 807c7120 87d344b0 00000000 nt!KiExecuteAllDpcs+0xf9 807e7ff4 82ac47dc a736cbdc 00000000 00000000 nt!KiRetireDpcList+0xd5 807e7ff8 a736cbdc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 82ac47dc 00000000 0000001a 00d6850f bb830000 0xa736cbdc STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+2cf 82a8e5fb 833d4417bb8200 cmp dword ptr [nt!KiFreezeFlag (82bb1744)],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap0E+2cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76eb4 FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+2cf BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+2cf Followup: MachineOwner ---------
  3. BugCheck D1, {44c131c0, 2, 1, 93d3b118} Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_iSetGlobalEndpointStateTx+b3 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 44c131c0, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 93d3b118, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b7f848 Unable to read MiSystemVaType memory at 82b5ee20 44c131c0 CURRENT_IRQL: 2 FAULTING_IP: USBPORT!USBPORT_iSetGlobalEndpointStateTx+b3 93d3b118 c70173654938 mov dword ptr [ecx],38496573h CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: 807e3b84 -- (.trap 0xffffffff807e3b84) ErrCode = 00000002 eax=fbe6a4e3 ebx=865680f0 ecx=44c131c0 edx=0000000e esi=8705e008 edi=82a51108 eip=93d3b118 esp=807e3bf8 ebp=807e3c0c iopl=0 ov up ei pl nz na pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a07 USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xb3: 93d3b118 c70173654938 mov dword ptr [ecx],38496573h ds:0023:44c131c0=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 93d3b118 to 82a575fb STACK_TEXT: 807e3b84 93d3b118 badb0d00 0000000e 807cc800 nt!KiTrap0E+0x2cf 807e3c0c 93d3b05c 00000004 8705e098 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xb3 807e3c2c 93d3ab56 86568028 8705e008 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18 807e3c54 93d3a9ce 8705e008 86568720 86568002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x17d 807e3c78 82a8e1b5 8656872c 86568002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173 807e3cd4 82a8e018 807c7120 807cc800 00000000 nt!KiExecuteAllDpcs+0xf9 807e3d20 82a8de38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5 807e3d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38 STACK_COMMAND: kb FOLLOWUP_IP: USBPORT!USBPORT_iSetGlobalEndpointStateTx+b3 93d3b118 c70173654938 mov dword ptr [ecx],38496573h SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: USBPORT!USBPORT_iSetGlobalEndpointStateTx+b3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: USBPORT IMAGE_NAME: USBPORT.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c04bd FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_iSetGlobalEndpointStateTx+b3 BUCKET_ID: 0xD1_USBPORT!USBPORT_iSetGlobalEndpointStateTx+b3 Followup: MachineOwner ---------
  4. BugCheck A, {bf3f5758, 2, 0, 82a0b90e} Probably caused by : luafv.sys ( luafv!GetFileInformation+105 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: bf3f5758, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 82a0b90e, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 82ba8848 Unable to read MiSystemVaType memory at 82b87e20 bf3f5758 CURRENT_IRQL: 2 FAULTING_IP: hal!KeReleaseQueuedSpinLock+e 82a0b90e 8b18 mov ebx,dword ptr [eax] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: hamachi-2-ui.e TRAP_FRAME: 8cb7f488 -- (.trap 0xffffffff8cb7f488) ErrCode = 00000000 eax=bf3f5758 ebx=8635ed00 ecx=879116c4 edx=746c6600 esi=864bf1e8 edi=879116d4 eip=82a0b90e esp=8cb7f4fc ebp=8cb7f508 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 hal!KeReleaseQueuedSpinLock+0xe: 82a0b90e 8b18 mov ebx,dword ptr [eax] ds:0023:bf3f5758=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 82a0b90e to 82a805fb STACK_TEXT: 8cb7f488 82a0b90e badb0d00 746c6600 00000000 nt!KiTrap0E+0x2cf 8cb7f4fc 82af37db 8635ed80 8cb7f520 8b725b51 hal!KeReleaseQueuedSpinLock+0xe 8cb7f508 8b725b51 864bf1e8 879116d4 879116c4 nt!IoGetAttachedDeviceReference+0x2e 8cb7f520 8b726670 85abe788 864bf1e8 879116d4 fltmgr!FltpGetVolumeFromDeviceObject+0x11 8cb7f534 8b7323a3 85abe788 8635ed80 879116d4 fltmgr!FltpGetVolumeFromFileObject+0x1a 8cb7f558 8b72bbe7 0017ffcc 8635ed80 8cb7f580 fltmgr!TargetedIOCtrlAttachAsFoCtx+0x75 8cb7f5b4 94db70d8 8763c6b0 8763f768 8cb7f650 fltmgr!FltCreateFileEx2+0x13f 8cb7f634 94db6c59 00000000 8cb7f798 8cb7f69c luafv!GetFileInformation+0x105 8cb7f750 94db4ff7 9f48c398 9f4ec580 00000002 luafv!CreateTableNode+0xae 8cb7f7c4 94db58e5 002072c0 00b7f824 00000000 luafv!LuafvFindTableNode+0x254 8cb7f86c 94db34ca 0063f768 00000000 00000000 luafv!LuafvQueryStoreFile+0x1b7 8cb7f8d4 8b712aeb 87968598 00b7f8f4 8cb7f920 luafv!LuafvPreCreate+0x267 8cb7f940 8b7159f0 8cb7f984 87a8d400 00000000 fltmgr!FltpPerformPreCallbacks+0x34d 8cb7f958 8b7291fe 8cb7f984 8b72cf3c 00000000 fltmgr!FltpPassThroughInternal+0x40 8cb7f96c 8b7298b7 8cb7f984 87a8d400 8775b5a0 fltmgr!FltpCreateInternal+0x24 8cb7f9b0 82a7658e 864bf1e8 861326c0 8775b5fc fltmgr!FltpCreate+0x2c9 8cb7f9c8 82c85367 b5a33b79 8cb7fb70 00000000 nt!IofCallDriver+0x63 8cb7faa0 82c64b6e 85f46c18 c51a6b90 8781c008 nt!IopParseDevice+0xed7 8cb7fb1c 82c74f80 00000000 8cb7fb70 00000040 nt!ObpLookupObjectName+0x4fa 8cb7fb78 82c97b81 0012f6b8 851a6b90 00000401 nt!ObOpenObjectByName+0x165 8cb7fd24 82a7d21a 0012f6b8 0012f690 0012f6e8 nt!NtQueryAttributesFile+0x121 8cb7fd24 77bf70b4 0012f6b8 0012f690 0012f6e8 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 0012f6e8 00000000 00000000 00000000 00000000 0x77bf70b4 STACK_COMMAND: kb FOLLOWUP_IP: luafv!GetFileInformation+105 94db70d8 8bf8 mov edi,eax SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: luafv!GetFileInformation+105 FOLLOWUP_NAME: MachineOwner MODULE_NAME: luafv IMAGE_NAME: luafv.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc020 FAILURE_BUCKET_ID: 0xA_luafv!GetFileInformation+105 BUCKET_ID: 0xA_luafv!GetFileInformation+105 Followup: MachineOwner ---------
  5. BugCheck D1, {a8f1b164, ff, 0, a} Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: a8f1b164, memory referenced Arg2: 000000ff, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 0000000a, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 82b7e848 Unable to read MiSystemVaType memory at 82b5de20 a8f1b164 CURRENT_IRQL: 0 FAULTING_IP: +3231656331343038 0000000a ?? ??? PROCESS_NAME: ts3client_win3 ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target. BUGCHECK_STR: DISABLED_INTERRUPT_FAULT CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT TRAP_FRAME: a7130cc0 -- (.trap 0xffffffffa7130cc0) ErrCode = 00000000 eax=7ffdb000 ebx=82a563cd ecx=8790b470 edx=01df7af0 esi=01dea3c8 edi=8790b470 eip=82a53e0e esp=a7130d34 ebp=a7130d34 iopl=0 nv up di pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010006 nt!CommonDispatchException+0x52: 82a53e0e 8b442468 mov eax,dword ptr [esp+68h] ss:0010:a7130d9c=008a4850 Resetting default scope LAST_CONTROL_TRANSFER: from 82a53e0e to 82a565fb STACK_TEXT: a7130cc0 82a53e0e badb0d00 01df7af0 82c3dc9d nt!KiTrap0E+0x2cf a7130d34 008a4850 badb0d00 01df7af0 00000000 nt!CommonDispatchException+0x52 WARNING: Frame IP not in any known module. Following frames may be wrong. a7130d38 badb0d00 01df7af0 00000000 00000000 0x8a4850 a7130d3c 01df7af0 00000000 00000000 00000000 0xbadb0d00 a7130d40 00000000 00000000 00000000 00000000 0x1df7af0 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+2cf 82a565fb 833d4497b78200 cmp dword ptr [nt!KiFreezeFlag (82b79744)],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap0E+2cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76eb4 FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_nt!KiTrap0E+2cf BUCKET_ID: DISABLED_INTERRUPT_FAULT_nt!KiTrap0E+2cf Followup: MachineOwner ---------
ASACPI.SYS is a known BSOD problem on Windows 7. Update the driver by:
1. Going to the Asus motherboard support site
When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
a. Click Start Menu
b. Click My Computer
c. Go to C:\WIndows\System32\drivers\
d. Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
Thanks to JMH and zigzag3143 for the above information.

Update Logitech SetPoint USB Filter (See Driver Reference)

Download and install the latest version of LogMeIn.

Uninstall all nVidia utilities and get the latest versions of those utilities.



1. Download and install Driver Sweeper
2. Download the latest nVidia driver for your nVidia display card
3. Click Start Menu
4. Right Click My Computer
5. Click Manage
6. Click Device Manager from the list on the left
7. Click the + next to Display adapter
8. Right click your nVidia display/graphics card device
9. Click Uninstall
10. Check the box to Delete driver software for the device
11. Click OK
12. Restart your computer in safe mode
13. Run Driver Sweeper, select nVidia display card drivers, analyze, clean
14. Restart your computer
15. Install the latest drivers
My System SpecsSystem Spec
25 Dec 2011   #3

Windows 7 Ultimate 32bit
 
 

I did everything, and it seems to be fixed. I'll post again if the problem comes back, but for now thanks a lot!

Edit: No BSOD so far, so I think it's fixed. Thank you for the quick response and helpful info!
My System SpecsSystem Spec
.


16 Jan 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Glad your system is now stable. Thank you for posting back and marking the thread solved.
My System SpecsSystem Spec
Reply

 Random BSOD's (0x0000000D1 and 0x0000000F7)




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:06 PM.
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