Please help a Newb with Rainbow Screen BSOD Problem

Hi woodssi, and welcome to SevenForums!

Unfortunately, there were no .dmp files included ... rerun the collection tool as administrator, or goto c:/windows/minidump and zip up any .dmp files and attach them to your next post..

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. Enable driver verifier using the following procedures ...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ba, 2, 1, 830a3572}

Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+46 )

Followup: MachineOwner

The following drivers are outdated and should be updated where possible...

Code:

943a4000 943a9280   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5) ... CD-ROM Class Filter Driver by Gear Software ... GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering
93210000 932c5000   HSX_CNXT HSX_CNXT.sys Fri Feb 13 15:57:25 2009 (4995DEB5) ... SoftK56 Modem Driver by Conexant Systems ... Conexant: Support
9310e000 93210000   HSX_DPV  HSX_DPV.sys  Fri Feb 13 16:00:17 2009 (4995DF61)... SoftK56 Modem Driver by Conexant Systems ... Conexant: Support
94336000 94382000   HSXHWBS2 HSXHWBS2.sys Fri Feb 13 15:58:27 2009 (4995DEF3)... SoftK56 Modem Driver by Conexant Systems ... Conexant: Support
93c22000 93c2d900   pcouffin pcouffin.sys Tue Dec 05 09:39:53 2006 (457584B9)... Low level access layer for CD devices (A part of many different CD/DVD burning programs)  ... VSO Download DVD Burning Software, convert AVI to DVD, video converter, DVD copy to DVD slideshow photo ... or
rename to pcouffin.BAK and see what CD/DVD program it breaks..
90830000 90a0d600   VX3000   VX3000.sys   Mon Apr 27 21:52:35 2009 (49F66163) ... Microsoft LifeCam VX3000 ... Microsoft Hardware Support for Windows®

This .dmp file is blaming the crash on STREAM.SYS as the faulting driver. This is a core windows file, and is not likely to be the direct cause. Are you using software for a USB camera, by any chance?? I was unable to find out much about problems with this driver except some old camera software causing a BSOD... I am calling in some additional help, so please be patient... You can turn off driver verifier in the mean time..

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {22e, 8fe7e1c2, 90a34f00, 0}

Probably caused by : STREAM.SYS ( STREAM!StreamClassPnP+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000022e, The caller has completed a successful IRP_MJ_PNP instead of passing it down.
Arg2: 8fe7e1c2, The address in the driver's code where the error was detected.
Arg3: 90a34f00, IRP address.
Arg4: 00000000

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


BUGCHECK_STR:  0xc9_22e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  22e

FAULTING_IP: 
STREAM!StreamClassPnP+0
8fe7e1c2 8bff            mov     edi,edi

FOLLOWUP_IP: 
STREAM!StreamClassPnP+0
8fe7e1c2 8bff            mov     edi,edi

IRP_ADDRESS:  90a34f00

DEVICE_OBJECT: 8d19a530

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

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

Resource @ nt!PiEngineLock (0x831aa320)    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  : 0x831aa320
	Thread Count  : 0
	Thread address: 0x00000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 83378ee1 to 8311f3d8

STACK_TEXT:  
80e41708 83378ee1 000000c9 0000022e 8fe7e1c2 nt!KeBugCheckEx+0x1e
80e41728 8337b2b1 8fe7e1c2 80e41760 8fe7e1c2 nt!VerifierBugCheckIfAppropriate+0x30
80e41740 8337b30e 0000022e 8fe7e1c2 00000000 nt!ViErrorFinishReport+0xc9
80e41794 833819d0 0000022e 90a34f00 90a34f00 nt!VfErrorReport1+0x4d
80e417bc 8337af1f 8d074360 8fe7e1c2 00000000 nt!VfPnpVerifyIrpStackUpward+0xa4
80e417d4 8337986d 8d28a398 00000001 00000000 nt!VfMajorVerifyIrpStackUpward+0x3c
80e41808 83373bfe 00000000 80e4188c 90a34fbb nt!IovpCompleteRequest2+0x8a
80e41830 830a30a0 8d19a530 90a34f00 80e418a4 nt!IovpLocalCompletionRoutine+0x75
80e41874 83373b64 00000000 00000000 8d19f828 nt!IopfCompleteRequest+0x115
80e418dc 8fe76707 90a34f00 00000000 80e41950 nt!IovCompleteRequest+0x133
80e418ec 8fe7e665 90a34f00 00000000 8d19f828 STREAM!SCCompleteIrp+0x29
80e41950 833736c3 8d19f770 90a34f00 90a34fd4 STREAM!StreamClassPnP+0x4a3
80e41974 8307c0a4 00000000 90a34ff8 8d19f770 nt!IovCallDriver+0x258
80e41988 8338521d 8d057100 90a34f00 8d19a530 nt!IofCallDriver+0x1b
80e419a0 833736c3 8d19a530 8d19f770 90a35000 nt!ViFilterDispatchPnp+0x120
80e419c4 8307c0a4 00000000 80e41a38 8d19a530 nt!IovCallDriver+0x258
80e419d8 83202964 00000000 86ffc2c8 8d22ef48 nt!IofCallDriver+0x1b
80e419f4 8320289b 80e41a14 830675c5 8d22ef48 nt!PnpAsynchronousCall+0x92
80e41a54 83202623 00000000 830675c5 8d22ef48 nt!PnpQueryDeviceRelations+0xbf
80e41a98 831fde20 8d22ef48 0000003d 00000000 nt!PipEnumerateDevice+0xf9
80e41c94 831cee0d 857cc808 8d0b97e8 80e41cc8 nt!PipProcessDevNodeTree+0x32c
80e41cd4 830673e7 8d0b97e8 831a8240 857c1020 nt!PiProcessStartSystemDevices+0x6d
80e41d00 830a816b 00000000 00000000 857c1020 nt!PnpDeviceActionWorker+0x241
80e41d50 83236418 00000001 caf6016a 00000000 nt!ExpWorkerThread+0x10d
80e41d90 830d6919 830a805e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  STREAM!StreamClassPnP+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: STREAM

IMAGE_NAME:  STREAM.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc861

FAILURE_BUCKET_ID:  0xc9_22e_VRF_STREAM!StreamClassPnP+0

BUCKET_ID:  0xc9_22e_VRF_STREAM!StreamClassPnP+0

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

Tews,

Sorry if this is giving you headache...

My Son installed a webcam on here (which I never use). Should I uninstall this, to see if stability is affected?

Yes... uninstall it and see if the crashes stop...

Your latest .dmp is blaming dxgknnl.sys (Directx) as the cause of this crash... Download and install the latest version ... Download DirectX 11 For Windows 7 ( DirectX3D 11)

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, 8306b4e6}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+1b8 )

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