BSOD after clean Win7 installation on new SSD Kingston

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

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

Code:

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
rimmptsk	bedb5000	bedc6000	Wed Nov 05 07:20:23 2008 (4911aba7)	00015427	None	rimmptsk.sys
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

Code:

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.

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. :)

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]

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).

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..