BSOD with backup or copy

anaron

New member
Power User
Local time
5:48 PM
Messages
178
Location
Kingsland Texas
Windows 7 Pro 32 bit for students and faculty retail
Replaced XP Home this week for my grandkids
Custom installed
Dimension 8250 purchased in '03
Hard drives, video card, and a few other things upgraded 3 to 4 years ago. Original motherboard.

First install went really bad with lots of bluescreens. Formated and did another custom install on one of my hard drives. Updated most the drivers that scanned as out dated. Transferred my files etc. Everything good until today when I first tried to backup to My Passport Essentials drive. Got a blue screen. I then tried to copy a 2.2 gb file to my thumb drive. Just before completion got another blue screen. Decided I better find someone who knows what they are doing. I know just enough to be dangerous!
Ron
 

Attachments

My Computer My Computer

At a glance

Windows 7 Pro 64 bit & Windows Pro 64 bitIntel i7-2600k 3.06 GHz16 GB GSkill F3-10666CL7QEVGA GeForce GT 1030
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Computer by ME
OS
Windows 7 Pro 64 bit & Windows Pro 64 bit
CPU
Intel i7-2600k 3.06 GHz
Motherboard
Gigabyte H67A-UD3H-B3
Memory
16 GB GSkill F3-10666CL7Q
Graphics Card(s)
EVGA GeForce GT 1030
Sound Card
onboard for now
Monitor(s) Displays
Dual AOC 2770VH1
Screen Resolution
1920x1080
Hard Drives
3 - Samsung 850 Pro Series 256 GB SSD
2 - Samsung 840 Pro Series 128 GB SSD
2 - Muskin Chronos Deluxe 120 GB SSD
PSU
Antec EarthWatts EA750
Case
Antec Sonata Elite
Cooling
120 mm Antec System Fan & 120 Antec rear exhaust fan
Keyboard
Keys U See
Mouse
Logitech Trackball T-BC21
Internet Speed
18 mbps down / 4 mbps up
Antivirus
MSE
Browser
Firefox
Other Info
Icy Dock 4 bay x 2.5 ssd to 5.25 exterior hot swap
4-LaCie Rugged USB3 Thunderbolt Series 120GB SSD
2-Mushkin Enhanced Ventura Pro 32GB USB 3.0 Flash Drive
3-Sandisk Extreme Pro 128gb Flash Drive
Netgear Nighthawk X6 AC 3200 R8000 - WZR-1 D1800H
US Robotics USr5610C modem
Windows 7 Pro 32 bit for students and faculty retail
Replaced XP Home this week for my grandkids
Custom installed
Dimension 8250 purchased in '03
Hard drives, video card, and a few other things upgraded 3 to 4 years ago. Original motherboard.

First install went really bad with lots of bluescreens. Formated and did another custom install on one of my hard drives. Updated most the drivers that scanned as out dated. Transferred my files etc. Everything good until today when I first tried to backup to My Passport Essentials drive. Got a blue screen. I then tried to copy a 2.2 gb file to my thumb drive. Just before completion got another blue screen. Decided I better find someone who knows what they are doing. I know just enough to be dangerous!
Ron



Hi anaron and welcome


These 5 were caused by -
*This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
*The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
*If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.


Because of a difference in the symbols that your version uses we cant tell you which ones.


I would update all the below drivers


How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Code:
[B][COLOR=RoyalBlue]
[/COLOR][/B]
[B][COLOR=RoyalBlue]vmodem.sys        0x8c739000    0x8c7e24c0    0x000a94c0    0x3e25eb75    1/15/2003 19:15:01                        
vvoice.sys        0x8c59c000    0x8c5ab940    0x0000f940    0x3e25eb8c    1/15/2003 19:15:24                        
ptserial.sys        0x91b01000    0x91b4c0e0    0x0004b0e0    0x3e25eb9f    1/15/2003 19:15:43                        
vpctcom.sys        0x8c63d000    0x8c6f9340    0x000bc340    0x3e276840    1/16/2003 22:19:44                                               
pcouffin.sys        0x91a22000    0x91a2d900    0x0000b900    0x457584b9    12/5/2006 10:39:53    [COLOR=Red][U][I]uninstall the dvd authoring app that uses this.[/I][/U][/COLOR]                    
PxHelp20.sys        0x8c063000    0x8c06c0c0    0x000090c0    0x475dd057    12/10/2007 19:48:39                        
AsIO.sys        0x91abc000    0x91abd440    0x00001440    0x47663cfc    12/17/2007 05:10:20                        
[/COLOR][/B]




If that doesnt cure the problem put the next dmp files up for us.




Jan


 
Last edited:

My Computer My Computer

At a glance

Win 7 Ultimate 64-bit. SP1.Intel i7 -720QM.[1.6GHz Turbo Boost 2.8GHz. 6...8 DDR 3 RAM. 1066MHZATI 1024 MB. DDR3. Radeon HD5650
Computer Manufacturer/Model Number
LAPTOP. HP Pavilion dv7-4010TX .
OS
Win 7 Ultimate 64-bit. SP1.
CPU
Intel i7 -720QM.[1.6GHz Turbo Boost 2.8GHz. 6MB Cache.]
Memory
8 DDR 3 RAM. 1066MHZ
Graphics Card(s)
ATI 1024 MB. DDR3. Radeon HD5650
Monitor(s) Displays
17.3" High Definition Brightview LCD. LED Backlit.
Screen Resolution
1600 x 900.
Hard Drives
640GB
Case
Laptop / notebook.
Mouse
Logitech Anywhere mouse. MX.
Internet Speed
ADSL [ but too slow ]
Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+51 )

Need to research...
 

My Computer My Computer

At a glance

Systems 1 and 2: Windows 7 Enterprise x64, Wi...System 1: i7 [email protected], System 2: AMD FX-41...System 1: 8GB System 2: 8GBSystem 1: ATI FirePro V4800 System 2: Radeon ...
Computer Manufacturer/Model Number
Dell and Custom
OS
Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
CPU
System 1: i7 [email protected], System 2: AMD FX-4100 Zambezi 3.6G
Motherboard
System 1:Dell 06NWYK System 2: ASUS M5A97 AM3+
Memory
System 1: 8GB System 2: 8GB
Graphics Card(s)
System 1: ATI FirePro V4800 System 2: Radeon HD 6850
Sound Card
System 1: onboard System 2: onboard
Monitor(s) Displays
System1: Viewsonic HDMI 24"
Screen Resolution
System 1: 1920x1080 System 2: 1920x1080
Hard Drives
System 1: Mirrored .5B drives System 2: Seagate Barracuda ST1000DM003 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s
Case
System 1: Dell System 2: Cooler Master
Internet Speed
10 MBPS
Will do Jan. I also know I have a driver problem with MY Passport Essential drive. Install it and a while later it can't be found. Am working on that now.

Lemur, that was one of the most repeated error sources on my first install and many bsods.
 

My Computer My Computer

At a glance

Windows 7 Pro 64 bit & Windows Pro 64 bitIntel i7-2600k 3.06 GHz16 GB GSkill F3-10666CL7QEVGA GeForce GT 1030
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Computer by ME
OS
Windows 7 Pro 64 bit & Windows Pro 64 bit
CPU
Intel i7-2600k 3.06 GHz
Motherboard
Gigabyte H67A-UD3H-B3
Memory
16 GB GSkill F3-10666CL7Q
Graphics Card(s)
EVGA GeForce GT 1030
Sound Card
onboard for now
Monitor(s) Displays
Dual AOC 2770VH1
Screen Resolution
1920x1080
Hard Drives
3 - Samsung 850 Pro Series 256 GB SSD
2 - Samsung 840 Pro Series 128 GB SSD
2 - Muskin Chronos Deluxe 120 GB SSD
PSU
Antec EarthWatts EA750
Case
Antec Sonata Elite
Cooling
120 mm Antec System Fan & 120 Antec rear exhaust fan
Keyboard
Keys U See
Mouse
Logitech Trackball T-BC21
Internet Speed
18 mbps down / 4 mbps up
Antivirus
MSE
Browser
Firefox
Other Info
Icy Dock 4 bay x 2.5 ssd to 5.25 exterior hot swap
4-LaCie Rugged USB3 Thunderbolt Series 120GB SSD
2-Mushkin Enhanced Ventura Pro 32GB USB 3.0 Flash Drive
3-Sandisk Extreme Pro 128gb Flash Drive
Netgear Nighthawk X6 AC 3200 R8000 - WZR-1 D1800H
US Robotics USr5610C modem
Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+51 )
Need to research...


Which dmp did you get that from?? I also found wrong symbols and no data we all reading the same dmp files?


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\10-5-10 Bsod\100510-82328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8280c000 PsLoadedModuleList = 0x8294b570
Debug session time: Tue Oct  5 16:22:18.884 2010 (GMT-4)
System Uptime: 0 days 0:03:25.962
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!Kei386EoiHelper+29d3 )

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

0: 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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 8280c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3f9b

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 00000000 

CURRENT_IRQL:  0

FAULTING_IP: 
+71f952f035fd960
00000000 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from 00000000 to 82844b7b

FAILED_INSTRUCTION_ADDRESS: 
+71f952f035fd960
00000000 ??              ???

STACK_TEXT:  
8292abe0 00000000 badb0d00 ffff0001 854d8002 nt!Kei386EoiHelper+0x29d3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!Kei386EoiHelper+29d3
82844b7b 833d205e968200  cmp     dword ptr [nt!KiBugCheckData+0x30c0 (82965e20)],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!Kei386EoiHelper+29d3

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID:  WRONG_SYMBOLS

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


old drivers
Code:
PfModNT.sys        0x9a1e8000    0x9a1ebda0    0x00003da0    0x3e657ad0    3/5/2003 00:19:28                        
BCMSM.sys        0x8da51000    0x8db5df80    0x0010cf80    0x3f4d715e    8/27/2003 23:05:02                        
ctoss2k.sys        0x8f1b7000    0x8f1e28e0    0x0002b8e0    0x3f6e46a9    9/21/2003 20:47:37                        
ctsfm2k.sys        0x8f1e3000    0x8f202b80    0x0001fb80    0x3f6e46c4    9/21/2003 20:48:04                        
P16X.sys        0x8f02a000    0x8f16eb80    0x00144b80    0x3f6e7dd8    9/22/2003 00:43:04                        
PxHelp20.sys        0x87d6e000    0x87d72d20    0x00004d20    0x409a7a91    5/6/2004 13:49:05                        
e100b325.sys        0x8f203000    0x8f229e00    0x00026e00    0x473de72c    11/16/2007 14:53:32
 

My Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up

My Computer My Computer

At a glance

Systems 1 and 2: Windows 7 Enterprise x64, Wi...System 1: i7 [email protected], System 2: AMD FX-41...System 1: 8GB System 2: 8GBSystem 1: ATI FirePro V4800 System 2: Radeon ...
Computer Manufacturer/Model Number
Dell and Custom
OS
Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
CPU
System 1: i7 [email protected], System 2: AMD FX-4100 Zambezi 3.6G
Motherboard
System 1:Dell 06NWYK System 2: ASUS M5A97 AM3+
Memory
System 1: 8GB System 2: 8GB
Graphics Card(s)
System 1: ATI FirePro V4800 System 2: Radeon HD 6850
Sound Card
System 1: onboard System 2: onboard
Monitor(s) Displays
System1: Viewsonic HDMI 24"
Screen Resolution
System 1: 1920x1080 System 2: 1920x1080
Hard Drives
System 1: Mirrored .5B drives System 2: Seagate Barracuda ST1000DM003 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s
Case
System 1: Dell System 2: Cooler Master
Internet Speed
10 MBPS

My Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Ken, found this in both dmps.

Loading Dump File [C:\Users\Mark\Desktop\bsod\100510-82328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8280c000 PsLoadedModuleList = 0x8294b570
Debug session time: Tue Oct 5 16:22:18.884 2010 (GMT-4)
System Uptime: 0 days 0:03:25.962
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, 0}

Probably caused by : storport.sys ( storport!RaidpAdapterDpcRoutine+51 )
 

My Computer My Computer

At a glance

Systems 1 and 2: Windows 7 Enterprise x64, Wi...System 1: i7 [email protected], System 2: AMD FX-41...System 1: 8GB System 2: 8GBSystem 1: ATI FirePro V4800 System 2: Radeon ...
Computer Manufacturer/Model Number
Dell and Custom
OS
Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
CPU
System 1: i7 [email protected], System 2: AMD FX-4100 Zambezi 3.6G
Motherboard
System 1:Dell 06NWYK System 2: ASUS M5A97 AM3+
Memory
System 1: 8GB System 2: 8GB
Graphics Card(s)
System 1: ATI FirePro V4800 System 2: Radeon HD 6850
Sound Card
System 1: onboard System 2: onboard
Monitor(s) Displays
System1: Viewsonic HDMI 24"
Screen Resolution
System 1: 1920x1080 System 2: 1920x1080
Hard Drives
System 1: Mirrored .5B drives System 2: Seagate Barracuda ST1000DM003 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s
Case
System 1: Dell System 2: Cooler Master
Internet Speed
10 MBPS
  • Like
Reactions: JMH
Lemur thanks for the verification. I thought it was my problem just wanted to make sure.
 

My Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
anaron,
Is that old computer even on the list of approved computers?

Check with the manufactuer to see what he has to say about running Win 7 on it and if it's even possible, a list of driver updates and any possible bios update.

Windows 7 Compatibility Center home
 

My Computer My Computer

At a glance

MS Windows 7 Ultimate SP1 64-bitAMD A10-4600M6.00 GB Dual-Channel DDR3 @ 798MHz (11-11-12-28)AMD Radeon HD 7660G
Computer Manufacturer/Model Number
Toshiba Satellite S875D-S7239 laptop
OS
MS Windows 7 Ultimate SP1 64-bit
CPU
AMD A10-4600M
Motherboard
AMD Pumori (Socket FT1)
Memory
6.00 GB Dual-Channel DDR3 @ 798MHz (11-11-12-28)
Graphics Card(s)
AMD Radeon HD 7660G
Sound Card
High Definition Audio Device
Monitor(s) Displays
Generic PnP Monitor (1600x900@60Hz)
Screen Resolution
1600x900@60Hz
Hard Drives
SSD 119GB Corsair CSSD-V128GB2 ATA Device
Keyboard
Standard PS/2 Keyboard
Mouse
HP Wireless Optical Mobile Mouse Model FHA-3410
Internet Speed
What the local pub, local coffee shop offers.
Other Info
Optical Drive:MATSHITA BD-CMB UJ160B ATA Device


Also have an Asus ha1002xp netbook with Win 7 Ultimate installed.
Microsoft says no problem especially since most of my hardware has been upgrade in the last 3 or 4 years. Dell says it should run it with no "major issues"! Have already updated everything from Dell that applies to my current configuration.
 

My Computer My Computer

At a glance

Windows 7 Pro 64 bit & Windows Pro 64 bitIntel i7-2600k 3.06 GHz16 GB GSkill F3-10666CL7QEVGA GeForce GT 1030
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Computer by ME
OS
Windows 7 Pro 64 bit & Windows Pro 64 bit
CPU
Intel i7-2600k 3.06 GHz
Motherboard
Gigabyte H67A-UD3H-B3
Memory
16 GB GSkill F3-10666CL7Q
Graphics Card(s)
EVGA GeForce GT 1030
Sound Card
onboard for now
Monitor(s) Displays
Dual AOC 2770VH1
Screen Resolution
1920x1080
Hard Drives
3 - Samsung 850 Pro Series 256 GB SSD
2 - Samsung 840 Pro Series 128 GB SSD
2 - Muskin Chronos Deluxe 120 GB SSD
PSU
Antec EarthWatts EA750
Case
Antec Sonata Elite
Cooling
120 mm Antec System Fan & 120 Antec rear exhaust fan
Keyboard
Keys U See
Mouse
Logitech Trackball T-BC21
Internet Speed
18 mbps down / 4 mbps up
Antivirus
MSE
Browser
Firefox
Other Info
Icy Dock 4 bay x 2.5 ssd to 5.25 exterior hot swap
4-LaCie Rugged USB3 Thunderbolt Series 120GB SSD
2-Mushkin Enhanced Ventura Pro 32GB USB 3.0 Flash Drive
3-Sandisk Extreme Pro 128gb Flash Drive
Netgear Nighthawk X6 AC 3200 R8000 - WZR-1 D1800H
US Robotics USr5610C modem
OKKKKKK! Had a thought.

Cloned the sata drive that has the issue to my ide drives. Booted to one of the ide drives. Successfully cloned it to the My Passport Essential usb drive and copied a large file to the thumb drive. Worked great.

Rebooted to the sata, cloned my sata to My Passport Essential drive and it failed. I can however, clone my ide drives to my Passport Essentials from the sata drive with no issues.
 

Attachments

Last edited:

My Computer My Computer

At a glance

Windows 7 Pro 64 bit & Windows Pro 64 bitIntel i7-2600k 3.06 GHz16 GB GSkill F3-10666CL7QEVGA GeForce GT 1030
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Computer by ME
OS
Windows 7 Pro 64 bit & Windows Pro 64 bit
CPU
Intel i7-2600k 3.06 GHz
Motherboard
Gigabyte H67A-UD3H-B3
Memory
16 GB GSkill F3-10666CL7Q
Graphics Card(s)
EVGA GeForce GT 1030
Sound Card
onboard for now
Monitor(s) Displays
Dual AOC 2770VH1
Screen Resolution
1920x1080
Hard Drives
3 - Samsung 850 Pro Series 256 GB SSD
2 - Samsung 840 Pro Series 128 GB SSD
2 - Muskin Chronos Deluxe 120 GB SSD
PSU
Antec EarthWatts EA750
Case
Antec Sonata Elite
Cooling
120 mm Antec System Fan & 120 Antec rear exhaust fan
Keyboard
Keys U See
Mouse
Logitech Trackball T-BC21
Internet Speed
18 mbps down / 4 mbps up
Antivirus
MSE
Browser
Firefox
Other Info
Icy Dock 4 bay x 2.5 ssd to 5.25 exterior hot swap
4-LaCie Rugged USB3 Thunderbolt Series 120GB SSD
2-Mushkin Enhanced Ventura Pro 32GB USB 3.0 Flash Drive
3-Sandisk Extreme Pro 128gb Flash Drive
Netgear Nighthawk X6 AC 3200 R8000 - WZR-1 D1800H
US Robotics USr5610C modem
Due to the correct functioning on the ide drive and the bsod on the sata drive, I knew it had to be an issue with the sata and windows 7. Lemur stated that the issue was probably storport!RaidpAdapterDpcRoutine+51. Then I read where Blue Screem Viewer would in a lot of cases point you in the wrong direction and not really get to the root of the problem. Not being knowledgable in this area, I decided to try Windbg which was a whole new world to me. Finally got some basic instructions and ran the last 7 crashes. Five of them were the storport and 2 of them were my fax/voice modem. I removed the modem and instead of 10 or so crashes a day, I have gone 2 days with none. Still researching the storport issue trying to figure out what's what.
 

My Computer My Computer

At a glance

Windows 7 Pro 64 bit & Windows Pro 64 bitIntel i7-2600k 3.06 GHz16 GB GSkill F3-10666CL7QEVGA GeForce GT 1030
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Computer by ME
OS
Windows 7 Pro 64 bit & Windows Pro 64 bit
CPU
Intel i7-2600k 3.06 GHz
Motherboard
Gigabyte H67A-UD3H-B3
Memory
16 GB GSkill F3-10666CL7Q
Graphics Card(s)
EVGA GeForce GT 1030
Sound Card
onboard for now
Monitor(s) Displays
Dual AOC 2770VH1
Screen Resolution
1920x1080
Hard Drives
3 - Samsung 850 Pro Series 256 GB SSD
2 - Samsung 840 Pro Series 128 GB SSD
2 - Muskin Chronos Deluxe 120 GB SSD
PSU
Antec EarthWatts EA750
Case
Antec Sonata Elite
Cooling
120 mm Antec System Fan & 120 Antec rear exhaust fan
Keyboard
Keys U See
Mouse
Logitech Trackball T-BC21
Internet Speed
18 mbps down / 4 mbps up
Antivirus
MSE
Browser
Firefox
Other Info
Icy Dock 4 bay x 2.5 ssd to 5.25 exterior hot swap
4-LaCie Rugged USB3 Thunderbolt Series 120GB SSD
2-Mushkin Enhanced Ventura Pro 32GB USB 3.0 Flash Drive
3-Sandisk Extreme Pro 128gb Flash Drive
Netgear Nighthawk X6 AC 3200 R8000 - WZR-1 D1800H
US Robotics USr5610C modem
Back
Top