Blue Screen error.... Help!

Problem Event Name: BlueScreen
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 1033'

Additional information about the problem:
BCCode: f5
BCP1: 00000068
BCP2: 9CE9C6A8
BCP3: 9CE9C6D4
BCP4: 00000000
OS Version: 6_1_7100
Service Pack: 0_0
Product: 256_1

This is all the information I can retrieve, it says I can access more of this information via my minidump.... or .dmp files or my XML extension files... I can find the files but I cannot view them to determine the source of the problem, can anyone help me I really want to be able to use windows 7, but its causing problems with my internet and causing my computer to intermittently shut down............. HELP!

 

Well . Can you tell us. what have you done to your laptop. for example , are you playing any game ? or doing anything cause Blue screen ?

 

http://forums.majorgeeks.com/showthread.php?t=35246

 

I am on notebook review and other flash playing sites, freezes up often... when I try to shut down it also does it, sometimes on startup... games are working fine

 

I got the latest Windows 7 Nvidia driver for my card... so looks like im doing some research

 

Tinselworm... Ok so I tried this before using windows debugger... But it says I dont have permission to open those files??? I'm the freaking administrator lol

 

Well, you got stop error code 0x000000f5, which means

See this webpage

If you're technically minded, there's a Filter Manager Overview on MSDN that might get you started.

Basically, it sounds as if something's messing with a file system minifilter.

 

Ok I turned UAC off let see if that will do the trick

 

You need to copy the files into another directory, then you can open them.

 

I can open them now but I have no idea (disabled UAC) but I don't know exactly how to decipher it... if I post it can one of you take a look.... It says something about a problem with ntkrnlpa.exe which is part of the OS

is there a way I can post a small file for download on here?

 

Ok Im going to post it....

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050509-23805-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols* http://msdl.microsoft.com/downloads/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 7100 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0x82c4e000 PsLoadedModuleList = 0x82d96810
Debug session time: Tue May 5 16:58:52.740 2009 (GMT-7)
System Uptime: 0 days 0:01:24.003
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
........

 

After the above has posted in the debugger type !analyze -v , this gives a more detailed analyses.

 

Ok give me a sec lol, I have to transfer the files from my pc to laptop, internet isn't working through the pc
O btw, I have windows 7 installed on my Desktop... my 9280 hasn't arrived yet so.. lol

 

Something is wrong with the file path, I set up the workstation like Tinselworm told me, now it says the symbols aren't set up correctly

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050509-23805-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols* http://msdl.microsoft.com/downloads/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 7100 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0x82c4e000 PsLoadedModuleList = 0x82d96810
Debug session time: Tue May 5 16:58:52.740 2009 (GMT-7)
System Uptime: 0 days 0:01:24.003
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
........
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00001236, The subtype of the bugcheck.
Arg2: 8749e330
Arg3: 8749e3c0
Arg4: 00064b9f

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

*** WARNING: Unable to verify timestamp for rdyboost.sys
*** ERROR: Module load completed but symbols could not be loaded for rdyboost.sys
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 82c4e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8cc4

BUGCHECK_STR: 0x1a_1236

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82cbd6ea to 82d29f28

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9629fa9c 82cbd6ea 0000001a 00001236 8749e330 nt+0xdbf28
9629fad4 893d2c55 00000324 00000394 85ec8478 nt+0x6f6ea
9629fae8 893d3e42 85ec8430 00000394 85ef3728 rdyboost+0x1c55
9629fb00 893d7a24 85ec8478 00000394 893ed0b0 rdyboost+0x2e42
9629fb20 893d7ae8 85ec8478 00000000 85ec8430 rdyboost+0x6a24
9629fb34 893d7be9 85ec8430 85ec8430 85ec8430 rdyboost+0x6ae8
9629fb48 893d7c92 85ec8430 00000001 893ed0f8 rdyboost+0x6be9
9629fb64 893f4c5f 893ed0b0 85ec8430 00000001 rdyboost+0x6c92
9629fb84 893d49cd 00000008 893ed0b0 9629fbb4 rdyboost+0x23c5f
9629fb94 893efab3 893ed0b0 00000000 874bbe48 rdyboost+0x39cd
9629fbb4 893e08f5 893ed0b0 00000000 1f173a7c rdyboost+0x1eab3
9629fbfc 82c7fad1 85ecac30 874bbe48 874bbe48 rdyboost+0xf8f5
9629fc14 82e77177 875a84c0 874bbe48 874bbeb8 nt+0x31ad1
9629fc34 82e7a158 85ecac30 875a84c0 00000000 nt+0x229177
9629fcd0 82eb8487 85ecac30 874bbe48 00000000 nt+0x22c158
9629fd04 82c863fa 00000b5c 00000000 00000000 nt+0x26a487
9629fd34 76e08244 badb0d00 014bef8c 00000000 nt+0x383fa
9629fd38 badb0d00 014bef8c 00000000 00000000 0x76e08244
9629fd3c 014bef8c 00000000 00000000 00000000 0xbadb0d00
9629fd40 00000000 00000000 00000000 00000000 0x14bef8c


STACK_COMMAND: kb

FOLLOWUP_IP:
rdyboost+1c55
893d2c55 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: rdyboost+1c55

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME: rdyboost.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

 

Ok I managed to do this I don't know if it helped or not



Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050509-20358-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols* http://msdl.microsoft.com/downloads/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 7100 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0x82c52000 PsLoadedModuleList = 0x82d9a810
Debug session time: Tue May 5 17:11:14.605 2009 (GMT-7)
System Uptime: 0 days 0:01:23.478
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
........
3: kd> !findthebuild
FindTheBuild service not found
3: kd> !findthebuild -s
FindTheBuild service not found
3: kd> !findthebuild -s ; .reload
Usage: !findthebuild [-E|-Y] [-p|-s|-r] [-l <dir>]
-E - Disables exepath update
-Y - Disables sympath update
-l <dir> - Sets local cache for paths (must be last).
'*' set first sympath cache as local cache.
-p - Prepends discovered paths to sympath and exepath
-r - Sets discovered paths as sympath and exepath
-s - Adds discovered paths to sympath and exepath
-t - Discovers test code paths for this build
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