BSOD after clean Win7 installation on new SSD Kingston

[P911T]

Hi,

first I would like to apologize for not writing this thread according to BSOD post instructions but my problem is so specific that I am not able to comply with them.

My problem follow thread I have posted here a week ago:
http://www.sevenforums.com/crashes-debugging/213403-bsod-error-1000008e-1000007e.html#post1788676

I have purchased new SSD from Kingston (SSDNow V200 128GB) a few weeks ago. But I was not able to install win7 on it (BSOD all the time). I thought that I have got damaged SSD, so I claimed it in my vendor. The claim was solved in the way that I have got new same SSD (only exchange for new one was performed). So i tried to perform clean install of Win7 32 bit CZ Pro SP1 on it, but again, during installation process I have got a lot of BSODs. So I changed mode from AHCI to ATA in BIOS. After that I successfully performed installation and booted into win 7. I changed back mode to AHCI according to this tutorial:
Improve SATA hard disk performance (Convert from IDE to AHCI)
and everything was ok. I started to install updates (via windows update), but after installation and reboot I got BSOD again.

Unfortunately, OS did not generate any minidump (I checked it in system properties if generate dump file is checked and it is), but no minidump (I searched it almost everywhere...). So I installed all latest drivers from dell (especially SATA and chipset) and it seemed to get OK. But during work with computer, sometimes response is getting worse, sometimes computer suddenly freeze.

My computer spec:
Windows 7 Pro 32bit (installed from MSDNAA program)
SP1
Age of HW is 3 years, age of OS installation about 1 hour.
More details in my profile

I suspect something is wrong with drivers or motherboard (?) because I have got totally new SSD (so I think that probability of wrong ssd is very small). I am getting pretty agonized with that.

Have anybody ever noticed these kind of problem? Thanks everybody for any help!

 

[writhziden]

Sorry to see you are still having problems. Hopefully we can track them down. I'll call in other people to help this time if needed.

Dell's updates do not seem recent enough to support SSDs, in my opinion. Try updating drivers through the Intel® Driver Update Utility and see if it provides better support.

 

[zigzag3143]

Could we get your event viewer logs?

Please provide us with your Event Viewer administrative logs by following these steps:

Instructions courtesy of writhziden


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

 

[P911T]

Hi guys, thanks for any help. I am really appreciate for your help.

After booting to OS, I had so high latency that I was not able to access my computer or browse IE to get your reply. PC freezed so I had to turned it of hard. During next booting some tool like System Booting Recovery Tool started and tried to correct files but it was not successful. So I restarted PC and run last known good configuration and it helped with latency.

So I run intel driver update utility. But it only tells me to update driver of graphic card. For audio, WiFi and ethernet card says: "This device is unknown or unsupported. Please contact the manufacturer for possible updates." For chipset says that I have current version of driver.

Next I tried to get info from event viewer but during that I got BSOD. Minidump was created so I performed to run your application and result is attached.

Do I have still to export info from event viewer?

 

[zigzag3143]

Hi guys, thanks for any help. I am really appreciate for your help.

After booting to OS, I had so high latency that I was not able to access my computer or browse IE to get your reply. PC freezed so I had to turned it of hard. During next booting some tool like System Booting Recovery Tool started and tried to correct files but it was not successful. So I restarted PC and run last known good configuration and it helped with latency.

So I run intel driver update utility. But it only tells me to update driver of graphic card. For audio, WiFi and ethernet card says: "This device is unknown or unsupported. Please contact the manufacturer for possible updates." For chipset says that I have current version of driver.

Next I tried to get info from event viewer but during that I got BSOD. Minidump was created so I performed to run your application and result is attached.

Do I have still to export info from event viewer?

\

Nope. the problem is related to Disk hardware. Suggest you run CHKDSK'

http://www.sevenforums.com/tutorials/433-disk-check.html

 

[P911T]

to zigzag3143: ok, I run it. Result is in attachment but it is in czech. Ff you need to translate it all, let me know. Result of chkdsk is that "Windows didnt find any errors in file system" but there is also one fact: "The system deleted 166 unused items of index $SDH of file 0x9." but I dont know if it is important.

Do you think is SSD damaged again?

EDIT: I tried to uinstall intel rapid storage technology (or something like this) to perform installation of new SATA drivers but after uninstall I am not able to boot (PC freezes on welcome screen after writing pwd). So I am going to repair/reinstall OS... :-/

 

[P911T]

I have restored OS to restore point before I was not able to boot. But after restoration (after loging in) I got BSOD again, so I have made new info about it (see in attachment).

 

[zigzag3143]

I have restored OS to restore point before I was not able to boot. But after restoration (after loging in) I got BSOD again, so I have made new info about it (see in attachment).

Neither crash contained any useful information as they werent driver verified

 

[P911T]

OK, so should I continue with instructions posted here:
http://www.sevenforums.com/crashes-debugging/213403-bsod-error-1000008e-1000007e.html#post1790355

?

 

[writhziden]

Problem Devices:

Not Available ROOT \ VDRVROOT \ 0000 The drivers for this device are not installed.
Broadcom USH USB \ VID_0A5C & PID_5800 & MI_00 \ 6 & 66DE6C9 & 0 & 0000 The drivers for this device are not installed.
Base system device PCI \ VEN_1180 & DEV_0843 & REV_11 & SUBSYS_024F1028 \ 4 & 1 & C7E0DBE & 0BF0 The drivers for this device are not installed.
Not Available ROOT \ COMPOSITEBUS \ 0000 The drivers for this device are not installed.

Possible outdated drivers:

bcmwl6	92009000	92270000	Tue Jul 07 18:44:47 2009 (4a53ebff)	00265c68		bcmwl6.sys

bcmwl6.sys

[list=1]
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\P911T\Windows_NT6_BSOD_jcgriff2\022512-13150-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8303a000 PsLoadedModuleList = 0x831834d0
Debug session time: Sat Feb 25 12:31:22.787 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:33.410
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 896433f0, Terminating object
Arg3: 8964355c, Process image file name
Arg4: 83252d60, Explanatory message (ascii)

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


PROCESS_OBJECT: 896433f0

IMAGE_NAME:  _(M___

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: _(M___

FAULTING_MODULE: 00000000 

PROCESS_NAME:  

BUGCHECK_STR:  0xF4_

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 83318159 to 83118ef4

STACK_TEXT:  
82c75c9c 83318159 000000f4 00000003 896433f0 nt!KeBugCheckEx+0x1e
82c75cc0 83295cdc 83252d60 8964355c 89643660 nt!PspCatchCriticalBreak+0x71
82c75cf0 83295c1f 896433f0 8968ba58 c0000006 nt!PspTerminateAllThreads+0x2d
82c75d24 8307821a ffffffff c0000006 0118e740 nt!NtTerminateProcess+0x1a2
82c75d24 77487094 ffffffff c0000006 0118e740 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0118e740 00000000 00000000 00000000 00000000 0x77487094


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xF4___IMAGE__(M___

BUCKET_ID:  0xF4___IMAGE__(M___

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\P911T\Windows_NT6_BSOD_jcgriff2\022512-13993-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82a02000 PsLoadedModuleList = 0x82b4b4d0
Debug session time: Sat Feb 25 06:31:21.685 2012 (UTC - 7:00)
System Uptime: 0 days 0:06:25.292
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 88e51120, Terminating object
Arg3: 88e5128c, Process image file name
Arg4: 82c1ad60, Explanatory message (ascii)

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


PROCESS_OBJECT: 88e51120

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 00000000 

ˆESS_NAME:  ð9äˆ*

ˆHECK_STR:  0xF4_ð9äˆ*

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

EXCEPTION_RECORD:  8e4c0c7c -- (.exr 0xffffffff8e4c0c7c)
ExceptionAddress: 775d63ac
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 00000008
   Parameter[1]: 775d63ac
   Parameter[2]: c000009d
Inpage operation failed at 775d63ac, due to I/O error c000009d

LAST_CONTROL_TRANSFER:  from 82ce0159 to 82ae0ef4

STACK_TEXT:  
8e4c0448 82ce0159 000000f4 00000003 88e51120 nt!KeBugCheckEx+0x1e
8e4c046c 82c5dcdc 82c1ad60 88e5128c 88e51390 nt!PspCatchCriticalBreak+0x71
8e4c049c 82c5dc1f 88e51120 88f5ad48 c0000006 nt!PspTerminateAllThreads+0x2d
8e4c04d0 82a4021a ffffffff c0000006 8e4c0964 nt!NtTerminateProcess+0x1a2
8e4c04d0 82a3f46d ffffffff c0000006 8e4c0964 nt!KiFastCallEntry+0x12a
8e4c0550 82ab7359 ffffffff c0000006 0001003f nt!ZwTerminateProcess+0x11
8e4c0964 82a2efe7 8e4c0c7c 00000000 8e4c0d34 nt!KiDispatchException+0x497
8e4c0d04 82a43db7 8e4c0c7c 007ce9c4 00000000 nt!KiRaiseException+0x18a
8e4c0d20 82a4021a 007ce9a4 007ce9c4 00000000 nt!NtRaiseException+0x33
8e4c0d20 775d63ac 007ce9a4 007ce9c4 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
007cece0 00000000 00000000 00000000 00000000 0x775d63ac


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  wininit.exe

FAILURE_BUCKET_ID:  0xF4__9_________IMAGE_wininit.exe

BUCKET_ID:  0xF4__9_________IMAGE_wininit.exe

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


[/list]

1. A windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...
2. Same as 1.

It may help narrow down the cause if you do continue with the instructions from your previous thread.

Update the Broadcom driver listed above.

Also, make sure you install all Windows updates. I noticed you only have a little over half of them installed at the time of your previous upload.

 

[P911T]

Hi, I have tried to find driver for Broadcom but not successfull yet. :-/ The link you have posted doesnt contain appropriate drivers. I googled to find what is Broadcom USH and found that it should be finger print reader. My laptop doesnt have any finger print reader (only chip cards reader but I never used it).

I saw four unrecognized devices in device manager so I tried to install other updates from dell website. I have installed almost all of them but without effect, I still see unrecognized devices in device manager.

Some drivers (f.e. Ovlada and Ovlada) caused BSOD (I think same type like previous BSODs - should I posted info about them again?). I have installed also all updates from Microsoft.

I got new BSOD (code 0x00007A maybe?) but no dump file generated :-/

EDIT: ok, after another googling I probably found driver for broadcom. I am going to try it this evening

 

[writhziden]

If you have any trouble finding a driver, you are welcome to ask in this thread, but another very useful forum to start a thread for driver support is Drivers - Windows 7 Forums in case we are not around to answer.

If it was a 7A error, it appears to be related to the hard disk (Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR). I would be surprised if the disk was bad since you replaced it, but since SSDs are fairly new technology, I'm not ruling out the possibility entirely. It may just be that your system is not compatible with SSDs; it may be worth contacting Dell to find out.



Just analyzed the crash reports you put in the other thread (we should probably stick to this thread from here on), and had a few concerns.

Outdated drivers

PxHelp20	94cdf000	94ce3bc0	Tue Oct 28 12:25:49 2003 (3f9eb4ad)	0000e8bb		PxHelp20.sys
MarvinBus	9414f000	9417d000	Fri Sep 23 15:17:57 2005 (43347105)	00038741		MarvinBus.sys
SSPORT	b25c9000	b25d0000	Tue Nov 21 17:52:06 2006 (45639f36)	00009c15		SSPORT.sys
VMNET	949f5000	949f7f00	Thu May 22 04:33:05 2008 (48354be1)	0000b008		VMNET.SYS
vmnetadapter	949f2000	949f4680	Thu May 22 04:33:07 2008 (48354be3)	00007cba		vmnetadapter.sys
vmnetbridge	94c00000	94c06000	Thu May 22 04:33:38 2008 (48354c02)	00016039		vmnetbridge.sys
[B][COLOR="Red"]rimmptsk	bedb5000	bedc6000	Wed Nov 05 07:20:23 2008 (4911aba7)	00015427	None	rimmptsk.sys[/COLOR][/B]
vstor2_ws60	b25e2000	b25e5d80	Mon Dec 01 12:26:30 2008 (49343a66)	0000c37c		vstor2-ws60.sys
hotcore3	8d7f5000	8d7f9740	Fri Mar 20 04:35:05 2009 (49c37159)	0000a533		hotcore3.sys
LHidFilt	94dc6000	94dcd080	Wed Jun 17 10:49:04 2009 (4a391e80)	000167ac		LHidFilt.Sys
LMouFilt	94dce000	94dd5800	Wed Jun 17 10:49:08 2009 (4a391e84)	0000d1d5		LMouFilt.Sys
LEqdUsb	94d9b000	94da3500	Wed Jun 17 10:49:22 2009 (4a391e92)	0000bdb0		LEqdUsb.Sys
LHidEqd	94dc5000	94dc5e80	Wed Jun 17 10:49:25 2009 (4a391e95)	00005732		LHidEqd.Sys
bcmwl6	94604000	9486b000	Tue Jul 07 18:44:47 2009 (4a53ebff)	00265c68		bcmwl6.sys

PxHelp20.sys
MarvinBus.sys
SSPORT.sys
VMNET.SYS
vmnetadapter.sys
vmnetbridge.sys
rimmptsk.sys
vstor2-ws60.sys
hotcore3.sys
LHidFilt.Sys
LMouFilt.Sys
LEqdUsb.Sys
LHidEqd.Sys
bcmwl6.sys

Loading Dump File [D:\Kingston\BSODDmpFiles\P911T\Windows_NT6_BSOD_jcgriff2\022712-19344-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8363c000 PsLoadedModuleList = 0x837854d0
Debug session time: Mon Feb 27 05:42:26.938 2012 (UTC - 7:00)
System Uptime: 0 days 4:55:31.546
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..................
Unable to load image \SystemRoot\system32\DRIVERS\rimmptsk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rimmptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rimmptsk.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, bedb9138, 8f32b9a4, 8f32b580}

Probably caused by : rimmptsk.sys ( rimmptsk+4138 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bedb9138, The address that the exception occurred at
Arg3: 8f32b9a4, Exception Record Address
Arg4: 8f32b580, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
rimmptsk+4138
bedb9138 8b0401          mov     eax,dword ptr [ecx+eax]

EXCEPTION_RECORD:  8f32b9a4 -- (.exr 0xffffffff8f32b9a4)
ExceptionAddress: bedb9138 (rimmptsk+0x00004138)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000002c
Attempt to read from address 0000002c

CONTEXT:  8f32b580 -- (.cxr 0xffffffff8f32b580)
eax=00000000 ebx=865329f0 ecx=0000002c edx=00000000 esi=865329f0 edi=0000002c
eip=bedb9138 esp=8f32ba6c ebp=8f32ba6c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
rimmptsk+0x4138:
bedb9138 8b0401          mov     eax,dword ptr [ecx+eax] ds:0023:0000002c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0000002c

READ_ADDRESS: GetPointerFromAddress: unable to read from 837a5848
Unable to read MiSystemVaType memory at 83784e20
 0000002c 

FOLLOWUP_IP: 
rimmptsk+4138
bedb9138 8b0401          mov     eax,dword ptr [ecx+eax]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from bedb845d to bedb9138

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8f32ba6c bedb845d 865329f0 0000002c 86532c10 rimmptsk+0x4138
8f32ba88 bedb6764 865329f0 86532aa8 86532aa8 rimmptsk+0x345d
8f32ba9c bedbc62a 865329f0 865329f0 86532aa8 rimmptsk+0x1764
8f32bab4 bedb6cae 865329f0 864ba824 86532aa8 rimmptsk+0x762a
8f32bacc bedb70c9 865329f0 864ba790 864ba848 rimmptsk+0x1cae
8f32baf0 8367358e 865329f0 00000002 8f32bb8c rimmptsk+0x20c9
8f32bb08 83814fcd 8675a620 88b976d0 8675a620 nt!IofCallDriver+0x63
8f32bb38 83901b27 8675a620 00000000 88b976d0 nt!IopSynchronousCall+0xc2
8f32bb90 8371831a 8675a620 00000002 cba311e0 nt!IopRemoveDevice+0xd4
8f32bbbc 838f9873 00000000 cba311e0 00000000 nt!PnpRemoveLockedDeviceNode+0x16c
8f32bbd0 838f9b27 00000002 00000000 00000000 nt!PnpDeleteLockedDeviceNode+0x2d
8f32bc04 838fd4ff 86bf5030 cba311e0 00000002 nt!PnpDeleteLockedDeviceNodes+0x4c
8f32bcc4 837ed2d2 8f32bcf4 00000000 cbac7650 nt!PnpProcessQueryRemoveAndEject+0x946
8f32bcdc 837fb3d2 00000000 89513460 86309a70 nt!PnpProcessTargetDeviceEvent+0x38
8f32bd00 836b9a6b 89513460 00000000 86309a70 nt!PnpDeviceEventWorker+0x216
8f32bd50 83844fda 00000001 a19403ac 00000000 nt!ExpWorkerThread+0x10d
8f32bd90 836ed1f9 836b995e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  rimmptsk+4138

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rimmptsk

IMAGE_NAME:  rimmptsk.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4911aba7

STACK_COMMAND:  .cxr 0xffffffff8f32b580 ; kb

FAILURE_BUCKET_ID:  0x7E_rimmptsk+4138

BUCKET_ID:  0x7E_rimmptsk+4138

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

Caused by the Ricoh Memory Card Reader driver linked to in red above.

 

[P911T]

OK, I found driver only on dell website. I installed it, so I will refer later how it works. I posted this problem to another thread because another thread is about BSODs which I have on laptop with origin hard disc from dell. This thread is about BSODs which I have on my laptop with hard disc changed to SSD Kingston.

 

[writhziden]

I understand, but since you now have the SSD installed, we should keep to this thread.

Unless I am misunderstanding... Do you have two laptops, one with an SSD and one without? If you do, you can post in the other thread for the laptop with the HDD and in this one for the laptop with the SSD.

Let us know how the new driver works and whether it helps.

 

[P911T]

to writhziden: Sorry for late reply but I was very busy last days. No, I have one laptop with classic HDD and I bought SSD and want to change it. But I want to be sure that everything is OK a works great before I copy data from old disc. So when I want to test ssd I have to turn off computer, take out old disc, include ssd and boot again...

I tried to install another drivers (especially for ricoh) and also microsoft updates but I got BSODs again I am not sure but I think that they are the same. For sure I have uploaded info about them (see attachment). I still see 3 unrecognized devices in device manager but I dont know what is it and which driver to install (I tried almost all drivers for my laptop)

[Issue mentioned in the previous post was about laptop with classic HDD. I installed ricoh driver again and it seems to be ok now]

 

[writhziden]

If you are looking to change to SSD, you will have more success with your system if you do a clean install. If you want to keep your current system intact, you can create a system image or your system as it currently is and then do the clean install. To create a system image, use:

http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html​

or

http://www.sevenforums.com/tutorials/663-backup-complete-computer-create-image-backup.html?ltr=B​

Swapping out drives as you are doing is not a fair way to test the hardware and actually may cause issues with how WIndows runs due to conflicts. To properly setup the SSD, I would advise making a system image of the current system as I advised above and then running through the following useful tutorials:

http://www.sevenforums.com/tutorials/113967-ssd-alignment.html
http://www.sevenforums.com/tutorials/149969-ssd-install-transfer-operating-system.html
http://www.sevenforums.com/tutorials/91339-ssd-hdd-optimize-windows-reinstallation.html
http://www.sevenforums.com/tutorials/70822-ssd-tweaks-optimizations-windows-7-a.html​

 

[P911T]

I have performed clean install of Win7 on SSD. I know that swapping discs is not the right way... I probably try to move the OS by imaging it (but currently I have bigger partition and disc that capacity of SSD).

 

[writhziden]

Okay, I think I understand now. Sorry, was not aware you had already tried those steps.

Can you post the hardware ids for the devices listed as not known for the laptop? To find the hardware IDs, go to device manager, right click any unknown devices, Properties, the details tab, and then change the property to Hardware IDs.

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\P911T\Windows_NT6_BSOD_jcgriff2\030112-19640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83001000 PsLoadedModuleList = 0x8314a4d0
Debug session time: Thu Mar  1 14:33:47.042 2012 (UTC - 7:00)
System Uptime: 0 days 0:01:41.665
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 89971030, Terminating object
Arg3: 8997119c, Process image file name
Arg4: 83219d60, Explanatory message (ascii)

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


PROCESS_OBJECT: 89971030

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 00000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
99196c9c 832df159 000000f4 00000003 89971030 nt!KeBugCheckEx+0x1e
99196cc0 8325ccdc 83219d60 8997119c 899712a0 nt!PspCatchCriticalBreak+0x71
99196cf0 8325cc1f 89971030 899c75d0 c0000006 nt!PspTerminateAllThreads+0x2d
99196d24 8303f21a ffffffff c0000006 003df52c nt!NtTerminateProcess+0x1a2
99196d24 76de7094 ffffffff c0000006 003df52c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
003df52c 00000000 00000000 00000000 00000000 0x76de7094


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\P911T\Windows_NT6_BSOD_jcgriff2\030112-13868-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83054000 PsLoadedModuleList = 0x8319d4d0
Debug session time: Thu Mar  1 14:31:11.941 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:16.565
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
........
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 89a26030, Terminating object
Arg3: 89a2619c, Process image file name
Arg4: 8326cd60, Explanatory message (ascii)

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


PROCESS_OBJECT: 89a26030

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 00000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
9061fc9c 83332159 000000f4 00000003 89a26030 nt!KeBugCheckEx+0x1e
9061fcc0 832afcdc 8326cd60 89a2619c 89a262a0 nt!PspCatchCriticalBreak+0x71
9061fcf0 832afc1f 89a26030 89a75900 c0000006 nt!PspTerminateAllThreads+0x2d
9061fd24 8309221a ffffffff c0000006 0151f148 nt!NtTerminateProcess+0x1a2
9061fd24 77d17094 ffffffff c0000006 0151f148 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0151f148 00000000 00000000 00000000 00000000 0x77d17094


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe

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


[/list]

Both of the most recent were identical. A windows system process was terminated unexpectedly. Possible causes are hard disk errors... System file corruption... Viruses... Lack of Windows updates... Drivers...

rimmptsk	92af1000	92b02000	Thu Jun 25 01:58:09 2009 (4a432e11)	000134e8	None	rimmptsk.sys

is still possibly out of date, but at least it is closer to the right timeframe.

 

[P911T]

ok, no problem I still think that better way is to do clean install than imaging OS. Or if you think that better way is imaging OS, just say it and I will try

Only for repetition: now I have two discs. Old one (classic hdd) with win7 pro installed and SSD (kingston) with win7 pro sp1 clean installation + all drivers.

Now I am writing from "classic" disc so I cant write hw ids at the moment. I will swap disc and do it asap. I will refer..

 

[writhziden]

See my above post as it has been updated.

Also, I agree that clean install is the better method and allows for less problems. You can also try running after the clean install without installing any drivers for the system and see if it is more stable. You can install the drivers that you need for the system to work properly (graphics drivers are often a must), but let Windows install the rest. Just test that way for a while. You can add drivers one at a time after that and see if you can determine which might cause crashes.