Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - stop error varies

20 Mar 2010   #1
Gryphonrage

Windows 7 Ultimate 32bit
 
 
BSOD - stop error varies

Hi all, im new to the W7 forums, but ive read a lot of good replies and a few of my problems have been solved thus far. However, its late, and i cant seem to dig this one up.

Occasionally ill get a BSOD with the P17.dll file being the issue. However that isnt always the case.

With the P17.dll its going to be a sound driver issue. I have a Rocketfish 5.1 surround sound card. Rocketfish is horrible at updating drivers.. newest one i have is from October of 09. Though their website does not have a section for drivers... kind of odd imo.

There are a few other stop errors ive gotten, 2 stand out, and the P17 file is the only file that comes to mind.

The 2 stop errors ive gotten are:

DRIVER_IRQL_NOT_LESS_OR EQUAL_TO and
PAGE_FAULT_IN_UNPAGED_AREA

i will upload a minidump zip with this post.

Most of the time though, it BSOD's on me when im watching video. I tend to watch my tv shows a day late, online when i get a chance since i work late. When streaming videos, it will crash to BSOD. i can usually play games without issues, its just the video quality imaging that crashes it.

Thank you in advance for your help.

P.S. Ive already done the following:

Researched the Mobo of my pre-built HP and looked for BIOS updates. Neither HP nor the
Mobo manufacturer had new BIOS builds.

Updated ALL drivers for anything i could; video card, sound card, usb ports even.. hell i updated the drivers on my usb Kensington mouse.

SYSTEM SPECS:
HP Pavilion 2.0ghz dual core
2GB DDR2 Kingston Bargain ram (this is part of my problem, but cant be all of it)
NVIDIA Geforce 8500GT 512mb PCI-e
Rocketfish 5.1 surround sound PCI


My System SpecsSystem Spec
.

20 Mar 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Gryphonrage View Post
Hi all, im new to the W7 forums, but ive read a lot of good replies and a few of my problems have been solved thus far. However, its late, and i cant seem to dig this one up.

Occasionally ill get a BSOD with the P17.dll file being the issue. However that isnt always the case.

With the P17.dll its going to be a sound driver issue. I have a Rocketfish 5.1 surround sound card. Rocketfish is horrible at updating drivers.. newest one i have is from October of 09. Though their website does not have a section for drivers... kind of odd imo.

There are a few other stop errors ive gotten, 2 stand out, and the P17 file is the only file that comes to mind.

The 2 stop errors ive gotten are:

DRIVER_IRQL_NOT_LESS_OR EQUAL_TO and
PAGE_FAULT_IN_UNPAGED_AREA

i will upload a minidump zip with this post.

Most of the time though, it BSOD's on me when im watching video. I tend to watch my tv shows a day late, online when i get a chance since i work late. When streaming videos, it will crash to BSOD. i can usually play games without issues, its just the video quality imaging that crashes it.

Thank you in advance for your help.

P.S. Ive already done the following:

Researched the Mobo of my pre-built HP and looked for BIOS updates. Neither HP nor the
Mobo manufacturer had new BIOS builds.

Updated ALL drivers for anything i could; video card, sound card, usb ports even.. hell i updated the drivers on my usb Kensington mouse.

SYSTEM SPECS:
HP Pavilion 2.0ghz dual core
2GB DDR2 Kingston Bargain ram (this is part of my problem, but cant be all of it)
NVIDIA Geforce 8500GT 512mb PCI-e
Rocketfish 5.1 surround sound PCI

You seem to have about five different causes for these crashes. there is another problem.

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds


Code:
022210-33789-01.dmp    2/22/2010 10:26:51 PM    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    0xc0000005    0x82fac885    0x8ab3b9d8    0x8ab3b5b0    fltmgr.sys    fltmgr.sys+a885                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-33789-01.dmp    2    15    7600    
022210-35755-01.dmp    2/22/2010 10:14:35 PM    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    0x80000003    0x965332c6    0x95f9b660    0x95f9b240    SRTSP.SYS    SRTSP.SYS+a2c7                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-35755-01.dmp    2    15    7600    
022210-36145-01.dmp    2/22/2010 9:50:25 PM    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED    0x1000007e    0x80000003    0x990dd2c6    0x9d23f660    0x9d23f240    SRTSP.SYS    SRTSP.SYS+a2c7                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-36145-01.dmp    2    15    7600    
022210-39515-01.dmp    2/22/2010 8:48:36 PM    PROCESS_HAS_LOCKED_PAGES    0x00000076    0x00000000    0x8677da80    0x00000001    0x00000000    ntkrnlpa.exe    ntkrnlpa.exe+dcd10                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-39515-01.dmp    2    15    7600    
022210-27970-01.dmp    2/22/2010 11:54:37 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    0xcccccccd    0x00000001    0x9a8c02c4    0x00000002    SYMEVENT.SYS    SYMEVENT.SYS+1bb1c                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-27970-01.dmp    2    15    7600    
022310-26036-01.dmp    2/23/2010 5:20:17 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    0x97f43a61    0x00000001    0x97c802c4    0x00000000    fltmgr.sys    fltmgr.sys+2161                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-26036-01.dmp    2    15    7600    
022310-33867-01.dmp    2/23/2010 4:41:39 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    0xccccccce    0x00000000    0x9b2382c4    0x00000002    fltmgr.sys    fltmgr.sys+1efb1                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-33867-01.dmp    2    15    7600    
022310-25178-01.dmp    2/23/2010 6:57:19 PM    NTFS_FILE_SYSTEM    0x00000024    0x001904fb    0x92cd121c    0x92cd0e00    0x884bf969    Ntfs.sys    Ntfs.sys+d969                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-25178-01.dmp    2    15    7600    
022210-28173-01.dmp    2/22/2010 10:50:05 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc000001d    0x8e13f84f    0x9ff418fc    0x00000000    SYMEVENT.SYS    SYMEVENT.SYS+884f                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-28173-01.dmp    2    15    7600    
022210-46051-01.dmp    2/22/2010 9:45:40 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0x80000003    0x95b0c2c6    0x8fb5f988    0x00000000    SRTSP.SYS    SRTSP.SYS+a2c7                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-46051-01.dmp    2    15    7600    
022310-21450-01.dmp    2/23/2010 4:19:38 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x00000001    0x8a994894    0x00000000    halmacpi.dll    halmacpi.dll+5ba9                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-21450-01.dmp    2    15    7600    
022310-26925-01.dmp    2/23/2010 6:01:10 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc000001d    0x9829dc13    0x8f8bb894    0x00000000    SRTSP.SYS    SRTSP.SYS+20c13                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-26925-01.dmp    2    15    7600    
022310-27066-01.dmp    2/23/2010 8:02:32 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc000001d    0x92780231    0x8a82e9ac    0x00000000    nvlddmkm.sys    nvlddmkm.sys+37d231                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-27066-01.dmp    2    15    7600    
022310-28064-01.dmp    2/23/2010 4:48:05 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc000001d    0x961066e4    0x97bb76ac    0x00000000    SRTSP.SYS    SRTSP.SYS+426e4                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-28064-01.dmp    2    15    7600    
022310-28251-01.dmp    2/23/2010 4:45:48 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc000001d    0x993d86e4    0x9638d6ac    0x00000000    SRTSP.SYS    SRTSP.SYS+426e4                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-28251-01.dmp    2    15    7600    
022310-28688-01.dmp    2/23/2010 4:50:24 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc000001d    0x983e16e4    0x99c7f6ac    0x00000000    SRTSP.SYS    SRTSP.SYS+426e4                    32-bit        C:\Users\K\Desktop\New folder (3)\022310-28688-01.dmp    2    15    7600    
022210-24538-01.dmp    2/22/2010 11:56:01 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    0xdcd8877d    0x00000002    0x00000001    0x88a80ade    ndis.sys    ndis.sys+6ade                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-24538-01.dmp    2    15    7600    
022210-39156-01.dmp    2/22/2010 11:24:44 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    0x45a5c8d1    0x00000002    0x00000000    0x8fd42250    Rt86win7.sys    Rt86win7.sys+1250                    32-bit        C:\Users\K\Desktop\New folder (3)\022210-39156-01.dmp    2    15    7600    
031910-29343-01.dmp    3/19/2010 7:25:33 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    0x3e4579d8    0x00000002    0x00000000    0x8fe55282                            32-bit        C:\Users\K\Desktop\New folder (3)\031910-29343-01.dmp    2    15    7600
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (3)\022210-39156-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82845000 PsLoadedModuleList = 0x8298d810
Debug session time: Tue Feb 23 00:22:47.797 2010 (GMT-4)
System Uptime: 0 days 0:33:14.888
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\Rt86win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt86win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {45a5c8d1, 2, 0, 8fd42250}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
My System SpecsSystem Spec
Reply

 BSOD - stop error varies




Thread Tools





Similar help and support threads
Thread Forum
BSOD varies from turning on to a few hours of surfing the web
the error code is smb.driver.intel (sys) attached DMP files current windows is 8.1 thank you for the help.
BSOD Help and Support
BSOD Civ 5 Error STOP 124
I can't seem to finish a game of Civilization V because my computer gets a STOP 124 BSOD error as the game progresses. Things I notice about this error include my computer getting abnormally hot when the error occurs. Note that no other games such as League of Legends, any MMORPG's, or any of my...
BSOD Help and Support
BSOD Since playing BF4, Varies in error's
Hey, I've been having some BSOD issues starting the first of this month, oddly once I bought BF4. I've BSOD'd 3 times since then, with the last two happening today. The first time was After I quit out of a match and went to go into another, The second time was mid match while typing and the third...
BSOD Help and Support
Random BSOD stop error 0x0000001E, hardware error?
Hello, A few days ago I got a random BSOD with the 0x0..1E stop error. Now my computer will rarely boot and when it does it still randomly gets the same BSOD. I once got a 1D stop error but its mostly 1E that keeps happening. I run Windows 7 Professional 64-bit and this time I used a Windows DVD...
BSOD Help and Support
Frequent BSOD while browsing web, specific error varies
edit: problem not fixed, scroll to bottom for update Is Windows 7 Pro x64 This is the original OS I obtained this copy of Windows 7 through my college System is brand new, only a few weeks old The OS installation is as old as the system, although I have reformatted/reinstalled Windows the...
BSOD Help and Support
Error open *.docx in Office 2003 with compatiablity pack varies
I had issue opening this particular file in WIN 7 (64BIT) with office 2003 SP3. This gives me a message saying "There was an error opening this file." However i have an older machine on WIN XP with office 2003 SP3, there is no problem in opening the docx file. Both machine have the office...
Microsoft Office

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:12.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App