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: BSOD 5-10 mins after unplugging eSata drive

28 Jun 2013   #1
supergahar

windows 7 ultimate x64
 
 
BSOD 5-10 mins after unplugging eSata drive

Hi, i always get BSOD after unplugging eSata drive which is shared over network. BSOD happens always 5-10 minutes after i unplugging eSata drive. Before i shared into network, BSOD never happen. I tried removing all the sharing, but BSOD still occurs. even it will happen when i only "safely remove device" from windows while not physically unplugging the device. Changed into "Quick Removal" but also didnt help.

below are from Who Crash report:

computer name:
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6371704832 total
VM: 2147352576, free: 1917075456




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 20/6/2013 2:28:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-15178-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002360682)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 20/6/2013 2:28:42 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002360682)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 20/6/2013 1:11:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-17643-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Wed 19/6/2013 5:40:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062013-20436-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF80002287710)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 18/6/2013 4:42:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061913-18376-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800022CE710, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 18/6/2013 4:04:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061813-53087-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800022D6710, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 18/6/2013 11:34:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061813-17830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000228D710, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 16/6/2013 4:13:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061613-21403-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF800022DD710)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 14/6/2013 4:05:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061413-23836-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF80002282710)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 14/6/2013 1:25:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061413-22417-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xA (0x18000000408, 0x2, 0x1, 0xFFFFF8000236C64C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 17/4/2013 5:46:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041813-45162-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x9410)
Bugcheck code: 0x116 (0xFFFFFA800A1EB4E0, 0xFFFFF88009409410, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR



On Sun 14/4/2013 4:48:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041413-26067-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFFA800AF561C0, 0x1, 0xFFFFF80002275DE8, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 17/3/2013 10:46:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031713-33087-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x25360)
Bugcheck code: 0xBE (0xFFFFF88001225360, 0xA40000004164121, 0xFFFFF88003222A10, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 10/3/2013 5:38:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031113-246575-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF800032CF800)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 6/3/2013 4:58:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030613-16801-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF80003285800)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


My System SpecsSystem Spec
.
28 Jun 2013   #2
supergahar

windows 7 ultimate x64
 
 
attached dump files

attached dump files
My System SpecsSystem Spec
01 Jul 2013   #3
supergahar

windows 7 ultimate x64
 
 

bump
My System SpecsSystem Spec
.

01 Jul 2013   #4
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Quote:
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 localhost
#
# Adobe Activation Block v2.
#
# For updates to the hosts check here: thethingy - TPB
#
127.0.0.1 3dns.adobe.com 3dns-1.adobe.com 3dns-2.adobe.com 3dns-3.adobe.com 3dns-4.adobe.com activate.adobe.com activate-sea.adobe.com activate-sjc0.adobe.com activate.wip.adobe.com
127.0.0.1 activate.wip1.adobe.com activate.wip2.adobe.com activate.wip3.adobe.com activate.wip4.adobe.com adobe-dns.adobe.com adobe-dns-1.adobe.com adobe-dns-2.adobe.com adobe-dns-3.adobe.com adobe-dns-4.adobe.com
127.0.0.1 adobeereg.com practivate.adobe practivate.adobe.com practivate.adobe.newoa practivate.adobe.ntp practivate.adobe.ipp ereg.adobe.com ereg.wip.adobe.com ereg.wip1.adobe.com
127.0.0.1 ereg.wip2.adobe.com ereg.wip3.adobe.com ereg.wip4.adobe.com hl2rcv.adobe.com wip.adobe.com wip1.adobe.com wip2.adobe.com wip3.adobe.com wip4.adobe.com
127.0.0.1 Registration wwis-dubc1-vip60.adobe.com www.wip.adobe.com www.wip1.adobe.com
127.0.0.1 www.wip2.adobe.com www.wip3.adobe.com Adobe wwis-dubc1-vip60.adobe.com crl.verisign.net CRL.VERISIGN.NET ood.opsource.net
0.0.0.0 sams.nikonimaging.com
127.0.0.1 sams.nikonimaging.com
#
# Any other entries you had go here (new line no # no space);


#
172.1.6.9 iPhone Backup Extractor for Windows and Mac
Based on some content in your HOSTS file, Perhaps we should do this first:

1. Download and save this tool to your desktop:
http://go.microsoft.com/fwlink/?linkid=52012

2. Run the tool, and then click Copy - ignore any errors if they appear

3. Use CTRL+V to paste the unedited results of the tool here in your next reply.
My System SpecsSystem Spec
02 Jul 2013   #5
supergahar

windows 7 ultimate x64
 
 

==removed double post
My System SpecsSystem Spec
02 Jul 2013   #6
supergahar

windows 7 ultimate x64
 
 

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-2FF62-C2DD7-9BFRV
Windows Product Key Hash: iU2H2KaJIQe1Zes0ZoRE50k4tDg=
Windows Product ID: 00426-292-8031853-85214
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {8F726E24-2A65-4720-9A56-BDB5312A10EA}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130318-1533
TTS Error:
Validation Diagnostic:
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\vjo\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{8F726E24-2A65-4720-9A56-BDB5312A10EA}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-9BFRV</PKey><PID>00426-292-8031853-85214</PID><PIDType>5</PIDType><SID>S-1-5-21-515527064-3904255067-944443875</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Studio 1458</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A04</Version><SMBIOSVersion major="2" minor="6"/><Date>20100413000000.000000+000</Date></BIOS><HWID>C7D23107018400FE</HWID><UserLCID>4809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>SE Asia Standard Time(GMT+07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>FX09 </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00170-292-803185-00-1033-7600.0000-0672012
Installation ID: 007792401476822653700070029561026623403711359884917715
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: 9BFRV
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/7/2013 8:37:33 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 6:7:2013 21:02
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: NgAAAAIAAQABAAIAAAADAAAAAwABAAEAonbgbcYndxYqnpRFYqyuKWI9pIZ3YysKqkJe/3ZW

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC DELL M09
FACP DELL M09
HPET DELL M09
BOOT DELL M09
MCFG DELL M09
OSFR DELL DELL
SLIC DELL FX09
SSDT PmRef CpuPm
SSDT PmRef CpuPm
SSDT PmRef CpuPm
My System SpecsSystem Spec
04 Jul 2013   #7
supergahar

windows 7 ultimate x64
 
 

bump!
My System SpecsSystem Spec
05 Jul 2013   #8
supergahar

windows 7 ultimate x64
 
 

bump
My System SpecsSystem Spec
08 Jul 2013   #9
supergahar

windows 7 ultimate x64
 
 

bump!
My System SpecsSystem Spec
Reply

 BSOD 5-10 mins after unplugging eSata drive




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Multiple BSODs after unplugging and plugging in flash drive.
Dual Core Windows 7 Pro 64 bit Toshiba laptop. My daughter was working on a Power Point project for school. She went to plug in her flash drive and it didn’t seem to load the drive up. She unplugged it and then plugged it back in. We got a BSOD. We restarted it and it BSOD again. I tried some...
BSOD Help and Support
eSATA drive not detected--can CrystalDiskInfo damage an eSATA drive
I plugged in my eSATA drive while CrystalDiskInfo was running and the computer froze. There was no way to regain control of the computer so I restarted. So now this eSATA drive is not recognized by the computer. The eSATA drive works in another computer. What's really weird is that...
BSOD Help and Support
BSOD after unplugging ESATA external drive
Lately I've been getting BSODs whenever I unplug my Seagate GoFlex Pro portable external hard drive from my Esata port on my Dell Studio 14 laptop. Even after I "safely remove hardware" and unplug the drive, a couple minutes later the BSOD shows up. I even have the hard drive policies set...
BSOD Help and Support
BSOD w/External eSATA Dock & Drive
- x86 (32-bit) or x64 ? x64 - the original installed OS on the system? Home Premium x64 - an OEM or full retail version? Was OEM, now full retail - OEM = came pre-installed on system Was OEM - Full Retail = you purchased it from retailer Windows 7 Professional x64, SP1 - What is the age of...
BSOD Help and Support
Can I move eSATA Drive into case without reformatting the drive?
I backed up files from one 1TB eSATA drive to another 1TB eSATA drive. It now occurs to me that it might have been better to have installed the backup drive in my computer case . Not wanting to do the backup all over again, can I simply install the drive in my computer without having to...
Hardware & Devices
No boot after unplugging setup drive
Hey all. Sorry if this question has really obvious solution but I've been bashing my head against this for a few hours this afternoon and am getting nowhere. I have downloaded the Win7 RC1 ISO and "burnt" it onto a 16GB OCZ Throttle eSATA / USB drive (exactly as in the SevenForums tutorial). I...
Installation & Setup


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 14:50.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App