Random BSOD After upgrading a Dell Studio 1537 to Win 7 32bit

[MannixTheWall]

Hi Guys

I've recently decided to upgrade my girlfriends dell studio 1537 from Vista 32 bit to Windows 7 professional and since then i've encountered countless BSOD. Funny thing is it's always at random but and only when surfing the net using Chrome?

I have uploaded my SF diagnositc file for your interest and any suggestions would be much appreciated. Please ask me any questions, if felt appropriate and i will do my best to provide you with all the information you need. Worse case scenario i will have to roll back to Vista, however if this can be avoided that would be great.

Thanks in advance for your assistance.

Mannix

 

[bagavan]

perform this

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Do this overnight .

Errors might be detected after 7 passes

uninstall Kaspersky antivirus

and use this instead

http://windows.microsoft.com/en-US/windows/security-essentials-download

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 9ee6a, 4, 140001}

*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+24 )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0009ee6a, page frame number
Arg3: 00000004, current page state
Arg4: 00140001, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 83124567 to 83118e98

STACK_TEXT:  
af3fd7f8 83124567 0000004e 00000099 0009ee6a nt!KeBugCheckEx+0x1e
af3fd810 830da6c8 c008dfc0 af3fd998 08925c46 nt!MiBadShareCount+0x24
af3fd924 830d92cb c008d9e0 c008dfb8 e7ec0030 nt!MiDeletePteRun+0x66a
af3fda28 830d98f6 117b0002 11bf7fff e7ec0030 nt!MiDeleteVirtualAddresses+0x3c1
af3fdaf8 830d95ab e7ec0030 88273cf0 d26dbad0 nt!MiRemoveMappedView+0x325
af3fdb20 83282437 d26dbad0 00000000 af3fdbe4 nt!MiRemoveVadAndView+0xe5
af3fdb80 832a08cf e7ec0030 117b0000 00000000 nt!MiUnmapViewOfSection+0x265
af3fdba0 8f63bdd0 ffffffff 117b0000 af3fdbe4 nt!NtUnmapViewOfSection+0x55
WARNING: Stack unwind information not available. Following frames may be wrong.
af3fdbd4 830778fa ffffffff 117b0000 af3fdcec klif+0x30dd0
af3fdbd4 83076c79 ffffffff 117b0000 af3fdcec nt!KiFastCallEntry+0x12a
af3fdc54 98f5c662 ffffffff 117b0000 d505120c nt!ZwUnmapViewOfSection+0x11
af3fdcec 98f5c3de 00000000 00000000 00000000 win32k!SURFACE::bDeleteSurface+0x273
af3fdd00 98f46976 00000000 00000000 fde70848 win32k!SURFREF::bDeleteSurface+0x14
af3fdd14 98f41cdd d505120c 001df424 d505120c win32k!bDeleteSurface+0x20
af3fdd28 830778fa d505120c 001df438 76fc7094 win32k!NtGdiDeleteObjectApp+0x7f
af3fdd28 76fc7094 d505120c 001df438 76fc7094 nt!KiFastCallEntry+0x12a
001df438 00000000 00000000 00000000 00000000 0x76fc7094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+24
83124567 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+24

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f7f43

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24

BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24

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

 

[MannixTheWall]

Hi, sorry for the late reply.

I did what you said but unfortunately no errors where found on the memory test. I have uninstalled both chrome and kaspersky but the BSOD still happen just not as often.

I think the problem is related to hardware drivers not being able to be upgraded as dell detects that the OS is no longer Vista and therefore says that it it unsupported.

I will roll back to Vista and see if this makes a difference.

Thanks for your help.

 

[bagavan]

then upload the new dumps

 

[MannixTheWall]

Sorry, new dumps attached.

 

[bagavan]

Run this

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[MannixTheWall]

Right I've done as you've said and now experiencing BSODs galore. Windows is now only loading in start up repair / recovery mode. I've tried booting windows normally however the BSOD keeps happening.
Shall disable the verifier and upload the new dumps after start up repair has finished?

New dumps attached after using verifier.

 

[bagavan]

Uninstall Daemon tools as it is known for causing BSOD

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, 8c8012e2, 9845cf68, 0}

*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** [B][U]WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+12e2 )
[/U][/B]
Followup: MachineOwner
---------

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: 8c8012e2, The address in the driver's code where the error was detected.
Arg3: 9845cf68, IRP address.
Arg4: 00000000, Status code.

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


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+12e2
8c8012e2 8bff            mov     edi,edi

FOLLOWUP_IP: 
dtsoftbus01+12e2
8c8012e2 8bff            mov     edi,edi

IRP_ADDRESS:  9845cf68

DEVICE_OBJECT: 9692fe70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  831b8be0 -- (!locks 831b8be0)

Resource @ nt!PiEngineLock (0x831b8be0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0x831b8be0
	Thread Count  : 0
	Thread address: 0x00000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 83388f1f to 8312fe98

STACK_TEXT:  
88127344 83388f1f 000000c9 0000023e 8c8012e2 nt!KeBugCheckEx+0x1e
88127364 8338b2e9 8c8012e2 8812739c 8c8012e2 nt!VerifierBugCheckIfAppropriate+0x30
8812737c 8338b430 0000023e 8c8012e2 00000000 nt!ViErrorFinishReport+0xc9
881273ec 8338963c 0000023e 9845cf68 00000000 nt!VfErrorReport6+0x51
8812741c 83388e7b 8f9f1ff4 8f9f1f90 00000000 nt!IovpCallDriver2+0x155
88127430 833836d4 8f9f1ff4 00000000 00000000 nt!VfAfterCallDriver+0x119
88127454 83087be0 00000000 962d16c0 9692fe70 nt!IovCallDriver+0x269
88127468 858369e7 962d16c0 963289e8 00000000 nt!IofCallDriver+0x1b
WARNING: Stack unwind information not available. Following frames may be wrong.
881274a8 8583ab87 962d16c0 003289e8 88127508 Wdf01000+0x59e7
881274e4 8c84f49a 00000020 963289e8 962d16c0 Wdf01000+0x9b87
88127518 8c84fbe1 69d2efe8 96328ac8 00000001 cdrom!DeviceSendRequestSynchronously+0x9c
881275c0 8c851a66 69d2efe8 001275fc 9632c700 cdrom!DeviceSendSrbSynchronously+0x2ad
88127640 8c85383c 962d1190 962a3384 962a3370 cdrom!DeviceCacheDeviceInquiryData+0x86
8812765c 85859ded 69d2efe8 88127688 85843917 cdrom!DeviceEvtSelfManagedIoInit+0xc2
88127668 85843917 962a3370 88127680 962d1ce8 Wdf01000+0x28ded
88127688 8585067f 00000001 8589ccc0 00000005 Wdf01000+0x12917
8812769c 858433bf 962d1ce8 00000040 8589cb58 Wdf01000+0x1f67f
88127738 8584161e 962d1ce8 00000312 962d1e08 Wdf01000+0x123bf
88127760 858425a1 962d1ce8 8812778c 00000501 Wdf01000+0x1061e
88127798 85856dfa 962d1ce8 881277d0 85844171 Wdf01000+0x115a1
881277a4 85844171 962d1ce8 8589f1b8 962d1ce8 Wdf01000+0x25dfa
881277d0 85840fad 962d1ce8 00000501 962d1e78 Wdf01000+0x13171
881277fc 85841183 88127824 962d1ce8 962d1a78 Wdf01000+0xffad
88127834 8585310e 962d1ce8 00000108 00000003 Wdf01000+0x10183
88127854 85852fc1 962d1ce8 962d1ce8 8589d850 Wdf01000+0x2210e
88127888 85852e78 962d1ce8 00000108 962d1da4 Wdf01000+0x21fc1
881278ac 858512bc 881278d0 962d1ce8 8b371318 Wdf01000+0x21e78
881278e4 858533c1 962d1ce8 00000002 962d1ce8 Wdf01000+0x202bc
881278f8 8583db07 962d1ce8 88127918 962d10d4 Wdf01000+0x223c1
88127924 85834bc2 98446f20 962d1a78 98446f20 Wdf01000+0xcb07
8812794c 85834a33 002d1a78 98446f20 8f9f1e28 Wdf01000+0x3bc2
88127968 833836c3 962d1a78 98446f20 98446ffc Wdf01000+0x3a33
8812798c 83087be0 00000000 88127a10 962d1a78 nt!IovCallDriver+0x258
881279a0 832107a0 00000000 9692fe70 96327718 nt!IofCallDriver+0x1b
881279bc 830632bb 881279ec 8306609f 96327718 nt!PnpAsynchronousCall+0x92
88127a20 83207609 8306609f 96327718 962a00a0 nt!PnpStartDevice+0xe1
88127a7c 832074d2 96327718 0000002b 00000000 nt!PnpStartDeviceNode+0x12c
88127a98 8320eee5 00000000 00000001 00000000 nt!PipProcessStartPhase1+0x62
88127c94 831dae4a 857cd610 8b3ad2a0 88127cc8 nt!PipProcessDevNodeTree+0x188
88127cd4 83065d2d 8b3ad2a0 831b6b00 857c4020 nt!PiProcessStartSystemDevices+0x6d
88127d00 830ce1eb 00000000 00000000 857c4020 nt!PnpDeviceActionWorker+0x241
88127d50 8325b07a 00000001 aed9cb24 00000000 nt!ExpWorkerThread+0x10d
88127d90 83101819 830ce0de 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+12e2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f103595

FAILURE_BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+12e2

BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+12e2

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

 

[MannixTheWall]

ok done. Now should i rerun the verifier?

 

[bagavan]

not necessary.

just see if the bsod persists

 

[MannixTheWall]

to be honest i only installed daemon tools last night and the BSOD happend prior to it being installed. As there's no harm in running the verifier one more time as i want to be sure and i'll upload my findings.
Thanks for your support so far.

 

[bagavan]

Sure.
Run driver verifier and post back the new dumps