Guys,
I've had my PC for over 5 years, and have successfully upgraded it from it's original Media Centre OS through XP Pro to it's current Windows 7 Ultimate without too many hassles.
However, over the last 10 days or so, I'm experiencing Rainbow Screen crashes (usually when I'm browsing) which result in BSOD's.
I've had mostly 'IRQL_NOT_LESS_OR_EQUAL', but also 'MEMORY_MANAGEMENT' and basic non-specific STOP messages.
I would really appreciate your assistance in sorting this out.
I've attached all the requested info (including Memtest results), however I'm sure you'll require more.
If you do, please give me some pointers as to how/where I find the info you want.
Looking forward to your help.
Stephen
I've had my PC for over 5 years, and have successfully upgraded it from it's original Media Centre OS through XP Pro to it's current Windows 7 Ultimate without too many hassles.
However, over the last 10 days or so, I'm experiencing Rainbow Screen crashes (usually when I'm browsing) which result in BSOD's.
I've had mostly 'IRQL_NOT_LESS_OR_EQUAL', but also 'MEMORY_MANAGEMENT' and basic non-specific STOP messages.
I would really appreciate your assistance in sorting this out.
I've attached all the requested info (including Memtest results), however I'm sure you'll require more.
If you do, please give me some pointers as to how/where I find the info you want.
Looking forward to your help.
Stephen
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..
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..
Thanks for the reply Tews,
As requested...
As requested...
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).
The following drivers are outdated and should be updated where possible...
- 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 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�
Tews,
Have done as directed, and now getting a message that
'The IO Manager has detected a violation from a Driver that is currently being verified'
Have enclosed another .dmp file.
Stephen
Have done as directed, and now getting a message that
'The IO Manager has detected a violation from a Driver that is currently being verified'
Have enclosed another .dmp file.
Stephen
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?
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 --------- Your ATI drivers are old, but unfortunately, ATI has stopped releasing new drivers for your card.
ATI Catalyst
You may try uninstalling your current drivers with a utility such as Driver Sweeper, and installing those ones again.
Guru3D - Driver Sweeper
Also, do you have another card you can try? That would be great, if you did.
ATI Catalyst
You may try uninstalling your current drivers with a utility such as Driver Sweeper, and installing those ones again.
Guru3D - Driver Sweeper
Also, do you have another card you can try? That would be great, if you did.
Tews,
I've since found that the webcam is Microsoft Own Brand, and appears to have Microsoft Driver... I've left it on at present.
Have updated DirectX, as you advised. DL'd the End-User option, hope that was the right one.
Lancaster
Strangely enough, I had read (from one of the other posts on the forum - before I started my own thread) about the ATI problem and installed the Catalyst about a week ago. Hasn't stopped the crashes, but cheers for the pointer.
I've since found that the webcam is Microsoft Own Brand, and appears to have Microsoft Driver... I've left it on at present.
Have updated DirectX, as you advised. DL'd the End-User option, hope that was the right one.
Lancaster
Strangely enough, I had read (from one of the other posts on the forum - before I started my own thread) about the ATI problem and installed the Catalyst about a week ago. Hasn't stopped the crashes, but cheers for the pointer.
After a week with no issues, a further crash today. 
BSOD seemed to be pointing towards Intelppm.sys as the cause.
It only got to 93% of the Memory Dump, so doesn't appear to have created a .dmp file.
Help... again!
BSOD seemed to be pointing towards Intelppm.sys as the cause.
It only got to 93% of the Memory Dump, so doesn't appear to have created a .dmp file.
Help... again!
Let's try some basics.
Test your temperatures, after you have been using it for a while. I recommend Speedfan: SpeedFan - Access temperature sensor in your computer
Test CPU. Here's a tutorial: http://www.sevenforums.com/tutorials...t-prime95.html
If it happens again, run the BSOD app again, and upload the new report.
Test your temperatures, after you have been using it for a while. I recommend Speedfan: SpeedFan - Access temperature sensor in your computer
Test CPU. Here's a tutorial: http://www.sevenforums.com/tutorials...t-prime95.html
If it happens again, run the BSOD app again, and upload the new report.
Lancaster, thanks or the hints.
Ran the tests, as you suggested, and all seemed well.
Only one other Crash since my last post and, again, dump only got to 93%.
If problems persist, and I get a full dump (hmmm... dunno if that's the right phrase to use
) then I'll run the BSOD app.
I'm obliged
Ran the tests, as you suggested, and all seemed well.
Only one other Crash since my last post and, again, dump only got to 93%.
If problems persist, and I get a full dump (hmmm... dunno if that's the right phrase to use
) then I'll run the BSOD app.I'm obliged
Okay, still getting the BSOD at least once per day.
Have run the new scans etc, and attached.
Hope someone can kill this, once and for all.....
Have run the new scans etc, and attached.
Hope someone can kill this, once and for all.....
I'm getting various STOP messages:-
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT
BUGCODE_USB_DRIVER
PAGE_ERROR_IN_NONPAGED_AREA
BAD_POOL_HEADER
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT
BUGCODE_USB_DRIVER
PAGE_ERROR_IN_NONPAGED_AREA
BAD_POOL_HEADER
There is one very old driver: A Google search makes me suspect you have an Adaptec device installed -- is this the case?
If so, update the drivers, or replace it, if you can't find any. If you need help locating drivers, post the model of the device.
Also, could you enable driver verifier again?
...Summary of the Dumps:
Code:
aspi32.sys Wed Jul 17 12:05:08 2002 (3D3595B4)
If so, update the drivers, or replace it, if you can't find any. If you need help locating drivers, post the model of the device.
Also, could you enable driver verifier again?
...Summary of the Dumps:
Code:
Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Mon Oct 18 14:57:33.922 2010 (UTC - 4:00) System Uptime: 0 days 0:18:44.204 BUGCHECK_STR: 0x50 PROCESS_NAME: iexplore.exe ��������������������������������������������������������������������������������������
Lancaster,
I ran Verifier through, selecting all of the non-Microsoft Drivers on an INDIVIDUAL basis, to see if I could narrow down the problem (ncluding the aspi32.sys which you had highlighted).
All seemed to pass the test, with the exception of the following:-
hcw88aud.sys
hcw88bar.sys
hcw88tun.sys
hcw88vid.sys
All of these gave 'The IO Manager has detected a violation by a Driver that is being verified' Blue Screen immediately upon Boot.
I ran Verifier through, selecting all of the non-Microsoft Drivers on an INDIVIDUAL basis, to see if I could narrow down the problem (ncluding the aspi32.sys which you had highlighted).
All seemed to pass the test, with the exception of the following:-
hcw88aud.sys
hcw88bar.sys
hcw88tun.sys
hcw88vid.sys
All of these gave 'The IO Manager has detected a violation by a Driver that is being verified' Blue Screen immediately upon Boot.
�� Quote: Originally Posted by Woodssi 
Lancaster,
I ran Verifier through, selecting all of the non-Microsoft Drivers on an INDIVIDUAL basis, to see if I could narrow down the problem (ncluding the aspi32.sys which you had highlighted).
All seemed to pass the test, with the exception of the following:-
hcw88aud.sys
hcw88bar.sys
hcw88tun.sys
hcw88vid.sys
All of these gave 'The IO Manager has detected a violation by a Driver that is being verified' Blue Screen immediately upon Boot.
I ran Verifier through, selecting all of the non-Microsoft Drivers on an INDIVIDUAL basis, to see if I could narrow down the problem (ncluding the aspi32.sys which you had highlighted).
All seemed to pass the test, with the exception of the following:-
hcw88aud.sys
hcw88bar.sys
hcw88tun.sys
hcw88vid.sys
All of these gave 'The IO Manager has detected a violation by a Driver that is being verified' Blue Screen immediately upon Boot.
Since your Hauppauge WinTV is not pass the test , better to uninstall it until your windows stable.
Rename these drivers into .bak extension (you need to take ownership each drivers)
Location : C:\windows\system32\drivers\
Code:
pcouffin.sys --> pcouffin.bak cdrbsdrv.SYS --> cdrbsdrv.bak
GEARAspiWDM.sys --> CD-ROM Class Filter Driver by Gear Software
Rtnicxp.sys --> Realtek NIC driver
Is your WinTV card an NTSC/NTSC-F 26552? If so, I haven't been able to find a stable driver for Windows 7 x64 (have not looked for x86, since I don't have it )
) Wish & LiquidSnak,
Changes made, as per your info...
With regards to the WINTV, this card has been part of the system since Original Build (when OS was Media Centre).
I don't actually have WIN TV software installed, so can I get rid of these drivers (what would be the best way to do it)?
Changes made, as per your info...
With regards to the WINTV, this card has been part of the system since Original Build (when OS was Media Centre).
I don't actually have WIN TV software installed, so can I get rid of these drivers (what would be the best way to do it)?
Go into device manager from the control panel and uninstall & delete the driver. It should be under there.
After that, shut down the computer, remove the hardware, and let us know if that fixes the problem.
After that, shut down the computer, remove the hardware, and let us know if that fixes the problem.
Okay, done..
However, now I'm getting the little yellow warning triangles under my CD & DVD Drives with the message 'Cannot load the device driver for this hardware'.
However, now I'm getting the little yellow warning triangles under my CD & DVD Drives with the message 'Cannot load the device driver for this hardware'.
Are they the drivers for your CD/DVD drive? If so, I would uninstall via device manager and then click "scan for hardware changes"
�� Quote: Originally Posted by Woodssi Okay, done..
However, now I'm getting the little yellow warning triangles under my CD & DVD Drives with the message 'Cannot load the device driver for this hardware'.
However, now I'm getting the little yellow warning triangles under my CD & DVD Drives with the message 'Cannot load the device driver for this hardware'.
After rename 2 drivers from CD/DVD burning software, it'll break the software.(You may rename it back to make the software work again)
But I think it's better to uninstall the software related and install win7 compatible burning software.
Code:
cdrbsdrv.SYS Mon Feb 20 17:17:38 2006 --> CD-ROM Filter Driver for B's Recorder GOLD (update no longer available) pcouffin.sys Tue Dec 05 21:39:53 2006 --> CD/DVD burning programs
Code:
cdrom.sys Tue Jul 14 06:11:24 2009
And lo, after making all the relevant changes, the BSOD's keep coming...
Here's today's Report:-
Here's today's Report:-
I know it's frustrating, but hang in there. We'll get you sorted out 
Yeah, SOMEBODY must have the answers.
I have sorted the issue with my DVD Drives, so just waiting for the final piece of the puzzle to fall into place.
Fingers Crossed.
S
I have sorted the issue with my DVD Drives, so just waiting for the final piece of the puzzle to fall into place.
Fingers Crossed.
S
Your Realtek network drivers should be updated. Install these ones: Realtek
Your modem drivers are out of date as well, so start here: Conexant: Modem Driver Assistance
Now your CD/DVD drive seems to be erroring. You are getting error 39 in Device Manager: Now Windows usually uses generic drivers for ATAPI devices, why would they be corrupted or missing?
Just to make sure, run a system files check. Open an elevated command prompt and enter sfc /scannow.
More likely than a driver issue is a hardware error, honestly. Both of your optical drives are erroring, according to msinfo32. In addition, your USB hard drive (Seagate FreeAgent) seems to be having trouble: We also have some of these: And something curious: Your TV Tuner drivers are out of date: I'm wondering if that could be conflicting. Try uninstalling the drivers, and installing a fresh, updated copy.
Remove the Seagate drive for now. I don't know what to make of the failed minidumps, honestly. Could be another sign of bad hardware, but then, maybe not.
If possible, remove both of your DVD drives. Of course, you will need them someday, sooner or later depending on how much you use optical media. Just see if the BSODs stop.
...Summary of the Dumps:
Your modem drivers are out of date as well, so start here: Conexant: Modem Driver Assistance
Now your CD/DVD drive seems to be erroring. You are getting error 39 in Device Manager:
Quote:
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.
Just to make sure, run a system files check. Open an elevated command prompt and enter sfc /scannow.
More likely than a driver issue is a hardware error, honestly. Both of your optical drives are erroring, according to msinfo32. In addition, your USB hard drive (Seagate FreeAgent) seems to be having trouble:
Code:
Event[558]: Log Name: System Source: Disk Date: 2010-10-21T20:16:13.833 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stephen-PC Description: The driver detected a controller error on \Device\Harddisk2\DR2. Event[4466]: Log Name: System Source: Disk Date: 2010-10-19T15:16:23.476 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stephen-PC Description: The driver detected a controller error on \Device\Harddisk2\DR2. Event[34998]: Log Name: System Source: Disk Date: 2010-09-03T02:01:27.476 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Stephen-PC Description: The driver detected a controller error on \Device\Harddisk2\DR2.
Code:
Event[34951]: Log Name: System Source: Microsoft-Windows-Kernel-Processor-Power Date: 2010-09-03T12:07:29.765 Event ID: 6 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Stephen-PC Description: Some processor performance power management features have been disabled due to a known firmware problem. Check with the computer manufacturer for updated firmware.
Code:
Event[805]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2010-10-21T19:05:58.000 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: STEPHEN-PC Description: Unable to produce a minidump file from the full dump file.
Code:
hcw88aud.sys Fri Jul 10 10:35:04 2009 (4A575198) HCW88BAR.sys Fri Jul 10 10:35:03 2009 (4A575197) hcw88bda.sys Fri Jul 10 12:37:19 2009 (4A576E3F) hcw88tse.sys Fri Jul 10 10:35:10 2009 (4A57519E) hcw88tun.sys Fri Jul 10 10:35:08 2009 (4A57519C) hcw88vid.sys Fri Jul 10 10:35:18 2009 (4A5751A6)
Remove the Seagate drive for now. I don't know what to make of the failed minidumps, honestly. Could be another sign of bad hardware, but then, maybe not.
If possible, remove both of your DVD drives. Of course, you will need them someday, sooner or later depending on how much you use optical media. Just see if the BSODs stop.
...Summary of the Dumps:
Code:
Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Fri Oct 22 04:27:57.337 2010 (UTC - 4:00) System Uptime: 0 days 0:56:47.650 BugCheck A, {18, 2, 0, 8306c132} Probably caused by : ntkrnlmp.exe ( nt!KiUnlinkWaitBlocks+b ) BUGCHECK_STR: 0xA PROCESS_NAME: iexplore.exe �������������������������������������������������������������������������������������� Hi -
System files show -
The earliest timestamp on the 15 mini kernel memory dumps from the various attachments = 28 September 2010. Were there any BSODs or other system trouble during the preceeding 9.5 months?
11 of the 15 BSODs occurred just under 13 seconds after boot-up -
BIOS is a likely problem here -
Your system = Fujitsu Siemens P5GD1-FM. I don't know the significance of DELL mentioned in the BIOS by WMI.
Fujitsu specs show your system has an Asus P5GD1-FM motherboard - http://uk.ts.fujitsu.com/rl/services...s-P5GD1-FM.pdf
You have two identical 200 GB internal HDDs - ST3200827AS ATA Device
- Run chkdsk /r on all drives
- Run HDD Diagnostics on both - Start with SeaTools for DOS - HDD Diag
Given issues with cdrom.sys , I would remove this 2002 CD burning app -
System logs show app hangs and crashes began in December 2009 - iTunes was the first to crash.
Run --> Windows 7 Upgrade Advisor - see whay it has to say.
Windbg Logs
--> http://jcgriff2.net/BSOD_Logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.net/BSOD_Logs/_99-db...riff2_.txt.zip
Regards. . .
jcgriff2
`
BSOD BUGCHECK SUMMARY
System files show -
Code:
Original Install Date: 15/12/2009, 12:00:14
11 of the 15 BSODs occurred just under 13 seconds after boot-up -
Code:
System Uptime: 0 days 0:56:47.650 System Uptime: 0 days 0:00:10.312 System Uptime: 0 days 0:00:11.000 System Uptime: 0 days 0:00:14.109 System Uptime: 0 days 0:00:11.406 System Uptime: 0 days 0:00:12.781 System Uptime: 0 days 0:00:12.656 System Uptime: 0 days 0:00:15.031 System Uptime: 0 days 0:00:12.859 System Uptime: 0 days 0:18:44.204 System Uptime: 0 days 0:25:48.393 System Uptime: 0 days 0:00:55.046 System Uptime: 0 days 0:00:28.312 System Uptime: 0 days 0:00:16.812 System Uptime: 0 days 0:03:49.156
BIOS is a likely problem here -
Code:
Win32_BIOS.Name="BIOS Date: 11/28/05 10:37:03 Ver: 08.00.10", SoftwareElementState=3,TargetOperatingSystem=0,Version="DELL - 11000528"
Fujitsu specs show your system has an Asus P5GD1-FM motherboard - http://uk.ts.fujitsu.com/rl/services...s-P5GD1-FM.pdf
You have two identical 200 GB internal HDDs - ST3200827AS ATA Device
- Run chkdsk /r on all drives
- Run HDD Diagnostics on both - Start with SeaTools for DOS - HDD Diag
Given issues with cdrom.sys , I would remove this 2002 CD burning app -
Code:
aspi32.sys Wed Jul 17 12:05:08 2002 (3D3595B4) - Adaptec CD burning - Adaptec - Technical Support
Run --> Windows 7 Upgrade Advisor - see whay it has to say.
Windbg Logs
--> http://jcgriff2.net/BSOD_Logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.net/BSOD_Logs/_99-db...riff2_.txt.zip
Regards. . .
jcgriff2
`
BSOD BUGCHECK SUMMARY
Code:
Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Fri Oct 22 04:27:57.337 2010 (GMT-4) System Uptime: 0 days 0:56:47.650 Probably caused by : ntkrnlmp.exe ( nt!KiUnlinkWaitBlocks+b ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: iexplore.exe Bugcheck code 0000000A Arguments 00000018 00000002 00000000 8306c132 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 13:55:30.843 2010 (GMT-4) System Uptime: 0 days 0:00:10.312 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys BUGCHECK_STR: 0xc9_c DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000000c 80e4d43c 8997cf68 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 05:30:26.531 2010 (GMT-4) System Uptime: 0 days 0:00:11.000 BUGCHECK_STR: 0xc9_22e DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000022e 8fe8b1c2 93ba0f00 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 05:27:26.640 2010 (GMT-4) System Uptime: 0 days 0:00:14.109 BUGCHECK_STR: 0xc9_23b DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000023b 8fe8f1c2 93540eb8 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 05:18:41.937 2010 (GMT-4) System Uptime: 0 days 0:00:11.406 BUGCHECK_STR: 0xc9_22e DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000022e 8fea31c2 949c4f00 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 05:12:51.312 2010 (GMT-4) System Uptime: 0 days 0:00:12.781 *** WARNING: Unable to verify timestamp for ks.sys *** ERROR: Module load completed but symbols could not be loaded for ks.sys *** WARNING: Unable to verify timestamp for hcw88bda.sys *** ERROR: Module load completed but symbols could not be loaded for hcw88bda.sys BUGCHECK_STR: 0xc9_23b DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000023b 8fe771c2 93aaeeb8 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 05:09:03.187 2010 (GMT-4) System Uptime: 0 days 0:00:12.656 BUGCHECK_STR: 0xc9_23b DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000023b 8fe8a1c2 94e46eb8 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 04:56:45.593 2010 (GMT-4) System Uptime: 0 days 0:00:15.031 BUGCHECK_STR: 0xc9_22e DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000022e 8fe991c2 899e4f00 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Thu Oct 21 04:35:18.406 2010 (GMT-4) System Uptime: 0 days 0:00:12.859 BUGCHECK_STR: 0xc9_22e DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000022e 9027e1c2 90c50f00 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Mon Oct 18 14:57:33.922 2010 (GMT-4) System Uptime: 0 days 0:18:44.204 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: iexplore.exe Bugcheck code 00000050 Arguments ffffffe8 00000001 83096448 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Wed Sep 29 04:49:35.096 2010 (GMT-4) System Uptime: 0 days 0:25:48.393 BugCheck D1, {5, a, 0, 96150b71} *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+89 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System Bugcheck code 000000D1 Arguments 00000005 0000000a 00000000 96150b71 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Wed Sep 29 03:22:42.750 2010 (GMT-4) System Uptime: 0 days 0:00:55.046 *** 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 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: csrss.exe Bugcheck code 0000000A Arguments 00000000 00000002 00000001 8306b4e6 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Wed Sep 29 03:14:19.000 2010 (GMT-4) System Uptime: 0 days 0:00:28.312 Probably caused by : Ntfs.sys ( Ntfs!NtfsFastIoDispatch+c ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: explorer.exe Bugcheck code 1000008E Arguments c0000005 8c06990c 9d648990 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Tue Sep 28 18:14:19.359 2010 (GMT-4) System Uptime: 0 days 0:00:16.812 BUGCHECK_STR: 0xc9_22e DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System Bugcheck code 000000C9 Arguments 0000022e 8fe7e1c2 90a34f00 00000000 ��������������������������������������������������������������������������������������`` Built by: 7600.20738.x86fre.win7_ldr.100618-1621 Debug session time: Tue Sep 28 06:56:18.843 2010 (GMT-4) System Uptime: 0 days 0:03:49.156 Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+46 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: iexplore.exe Bugcheck code 0000000A Arguments 000000ba 00000002 00000001 830a3572 ��������������������������������������������������������������������������������������`` by jcgriff2 J. C. Griffith, Microsoft MVP https://mvp.support.microsoft.com/profile/Griffith www.jcgriff2.com �������������������������������������������������������������������������������������� Jon,
�� Quote: Originally Posted by Jonathan_King Done
The Site only has Drivers up to WinXP, nothing for Windows 7
I have updated the Controllers through Microsoft Site, and all now appears fine.
Done, no issues highlighted.
I have now done an Uninstall / Reinstall of the appropriate Software
I no longer use TV Tuner (since OS Media Centre). Can I just delete these (or do I need a specific program to uninstall them)?
��������������������������������������
Thanks for your assistance
Stephen
�� Quote: Originally Posted by Jonathan_King Your Realtek network drivers should be updated.
Quote:
Your modem drivers are out of date as well
Quote:
Now your CD/DVD drive seems to be erroring. You are getting error 39 in Device Manager - 'Windows cannot load the device driver for this hardware. The driver may be corrupted or missing'.
Quote:
Just to make sure, run a system files check. Open an elevated command prompt and enter sfc /scannow.
Quote:
Your USB hard drive (Seagate FreeAgent) seems to be having trouble.
Quote:
Your TV Tuner drivers are out of date.
��������������������������������������
Thanks for your assistance
Stephen
JC,
Nothing at all like this through Media Centre, then XP Pro, and now 7 Ultimate.
I had a look at the ASUS Updater, but it mentions I need a Floppy DD (which my System doesn't have). Is there another option?
Done, with no issues highlighted (although this was after I updated the Controllers through the Microsoft Support site).
I cannot find this Software at all (I use IMGBurn now anyways). How can I delete or Uninstall this Driver?
Done, and all shows as Compatible, with no other issues highlighted.
I have attached a more recent Report, given the Updates / Changes I've made (from replies from both Jon & yourself).
Much obliged for your assistance.
Stephen
Quote:
System files show -
The earliest timestamp on the 15 mini kernel memory dumps from the various attachments = 28 September 2010. Were there any BSODs or other system trouble during the preceeding 9.5 months?
Code:
Original Install Date: 15/12/2009, 12:00:14
Quote:
BIOS is a likely problem here
Quote:
You have two identical 200 GB internal HDDs - ST3200827AS ATA Device
- Run chkdsk /r on all drives
- Run HDD Diagnostics on both
- Run chkdsk /r on all drives
- Run HDD Diagnostics on both
Quote:
Given issues with cdrom.sys , I would remove this 2002 CD burning app -
Code:
aspi32.sys Wed Jul 17 12:05:08 2002 (3D3595B4)
Quote:
Run --> Windows 7 Upgrade Advisor
I have attached a more recent Report, given the Updates / Changes I've made (from replies from both Jon & yourself).
Much obliged for your assistance.
Stephen
And here's the dmp from the first BSOD since I made the above changes....
Has the BIOS issue been addressed yet?
Some systems simply cannot run Windows 7 and maintain stability.
Per Microsoft -
jcgriff2
`
Some systems simply cannot run Windows 7 and maintain stability.
Per Microsoft -
Regards. . .Quote:... for those running a Windows OS other than Vista,
we recommend that you experience Windows 7 on a new system....
jcgriff2
`
JC,
How do I update BIOS without a Floppy DD?
I've been running Windows 7 for well over a year. The issues have only started within the last Month.
A new BSOD message came up today:-
'The Driver is mismanaging PTEs'....
How do I update BIOS without a Floppy DD?
I've been running Windows 7 for well over a year. The issues have only started within the last Month.
A new BSOD message came up today:-
'The Driver is mismanaging PTEs'....
2005 is the most recent P5GD1 BIOS that I find at Asus - ASUSTeK Computer Inc.-Support- download_item_P5GD1
ASUSTeK Computer Inc.-Support
I am not saying that Windows 7 will not run on this system; just that system stability under Windows 7 cannot be maintained, especially with SP1 arriving in the near future; then SP2, etc...
Regards. . .
jcgriff2
`
ASUSTeK Computer Inc.-Support
I am not saying that Windows 7 will not run on this system; just that system stability under Windows 7 cannot be maintained, especially with SP1 arriving in the near future; then SP2, etc...
Regards. . .
jcgriff2
`
JC,
Yep, appears there is no more up-to-date BIOS for my particular PC.
As far as I can tell, everything else (Drivers wise) has been updated.
Still no reply as to how best to get rid of the aspi32 & Hauppage Drivers...
If anything else springs to mind, I'd be obliged.
Stephen
Yep, appears there is no more up-to-date BIOS for my particular PC.
As far as I can tell, everything else (Drivers wise) has been updated.
Still no reply as to how best to get rid of the aspi32 & Hauppage Drivers...
If anything else springs to mind, I'd be obliged.
Stephen
Quote:
Still no reply as to how best to get rid of the aspi32 & Hauppage Drivers...
�� Quote: Originally Posted by Tews Stephen... If all else fails, rename the drivers with a .bak extension ie: hcw88aud.bak ... that way they will not load on boot...
Other than that, guess I better start saving for a new System.
I'd, once again, like to thank all who posted replies. If I haven't given anyone the proper Reputation, let me know.
Stephen
Certainly our pleasure. I missed entirely that the Hauppage driver was still installed. Fingers crossed, hoping that does it.
Không có nhận xét nào:
Đăng nhận xét