Win 7 Blue screen crash at start up

[Geoffswoodwork]

Hi,
I'm getting a Blue screen intermittently at start up just after Windows has started.
I suspect it has something to do with USB periferals being left connected.
I haven't noticed a crash when either my IPOD or MPG player is disconnected.
I do have a USB Disc Drive and Keyboard connected at all times.
When my IPOD or MPG Player is connected the computer seems to report them as a Removeable Disk.
Following the start up crash the computer restarts and provides the opportunity of a Restore Point or carry on with normal start.
Normal start allows the computer to run without any other problems.
The Action Centre > Maintenance > Reliability History > shows the crash but just says 'Windows Sopped Working'.
I dont get any problems once the computer has started up.
I'm not using games mostly Internet, MS Word, and Adobe Grafics programs such as TurboCAD 16. I sometimes get crashes with that but that is quite normal for this program.
In msconfig I only start up Windows Sidebar, AVG antivirus programme and ILO Office Manager (which I cant figure out how to stop it running?)

Question please: Have you any ideas on why I'm crashing on Start up?
Should my portable USB devices be left connected?
Are the problems with my USB devices because of driver problems?
My set up is:
Windows: Microsoft Windows 7 6.1.7600
Internet Explorer: 8.0.7600.16385
Memory (RAM): 3327 MB
CPU Info: Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
CPU Speed: 2495.2 MHz
Sound card: Speakers (High Definition Audio
Display Adapters: NVIDIA GeForce GTS 250 | NVIDIA GeForce GTS 250 | RDPDD Chained DD | RDP Encoder Mirror Driver | RDP Reflector Display Driver
Monitors: 1
Screen Resolution: 1280 X 1024 - 32 bit
Network: Network Present
Network Adapters: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
CD / DVD Drives: D: TSSTcorpCDDVDW SH-S223B
COM Ports: COM1
LPT Ports: LPT1
Mouse: 8 Button Wheel Mouse Present
Hard Disks: C: 698.6GB | E: 298.0GB
Hard Disks - Free: C: 655.9GB | E: 205.1GB
USB Controllers: 8 host controllers.
Firewire (1394): 1 host controllers.
PCMCIA (Laptops): Not Installed
Manufacturer: Phoenix Technologies, LTD
Product Make: OEM
AC Power Status: OnLine
BIOS Info:
Time Zone: GMT Standard Time
Battery: No Battery
Motherboard: Foxconn G31MX Series
Modem: Not detected

 

[zigzag3143]

Hi,
I'm getting a Blue screen intermittently at start up just after Windows has started.
I suspect it has something to do with USB periferals being left connected.
I haven't noticed a crash when either my IPOD or MPG player is disconnected.
I do have a USB Disc Drive and Keyboard connected at all times.
When my IPOD or MPG Player is connected the computer seems to report them as a Removeable Disk.
Following the start up crash the computer restarts and provides the opportunity of a Restore Point or carry on with normal start.
Normal start allows the computer to run without any other problems.
The Action Centre > Maintenance > Reliability History > shows the crash but just says 'Windows Sopped Working'.
I dont get any problems once the computer has started up.
I'm not using games mostly Internet, MS Word, and Adobe Grafics programs such as TurboCAD 16. I sometimes get crashes with that but that is quite normal for this program.
In msconfig I only start up Windows Sidebar, AVG antivirus programme and ILO Office Manager (which I cant figure out how to stop it running?)

Question please: Have you any ideas on why I'm crashing on Start up?
Should my portable USB devices be left connected?
Are the problems with my USB devices because of driver problems?
My set up is:
Windows: Microsoft Windows 7 6.1.7600
Internet Explorer: 8.0.7600.16385
Memory (RAM): 3327 MB
CPU Info: Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
CPU Speed: 2495.2 MHz
Sound card: Speakers (High Definition Audio
Display Adapters: NVIDIA GeForce GTS 250 | NVIDIA GeForce GTS 250 | RDPDD Chained DD | RDP Encoder Mirror Driver | RDP Reflector Display Driver
Monitors: 1
Screen Resolution: 1280 X 1024 - 32 bit
Network: Network Present
Network Adapters: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
CD / DVD Drives: D: TSSTcorpCDDVDW SH-S223B
COM Ports: COM1
LPT Ports: LPT1
Mouse: 8 Button Wheel Mouse Present
Hard Disks: C: 698.6GB | E: 298.0GB
Hard Disks - Free: C: 655.9GB | E: 205.1GB
USB Controllers: 8 host controllers.
Firewire (1394): 1 host controllers.
PCMCIA (Laptops): Not Installed
Manufacturer: Phoenix Technologies, LTD
Product Make: OEM
AC Power Status: OnLine
BIOS Info:
Time Zone: GMT Standard Time
Battery: No Battery
Motherboard: Foxconn G31MX Series
Modem: Not detected

We need the actual DMP file. use these to find and upload it to us. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html


thanks

 

[Geoffswoodwork]

I've downloaded the WDK and looked into the Debug utility.
I've looked at your set up procedures.
Sorry, this looks far too technical that I'd be confident in attempting.
I'll have to pass ...

But can you say if Ipods and Mpg players should be left connected to USB ports on Start up?

 

[Tews]

navigate to c:/windows/minidumd and zip up the .dmp file .. attach it to your next post for analysis...

 

[Geoffswoodwork]

Hmm, I see ...
Is this what you want?
View attachment 60083

 

[Geoffswoodwork]

Or is this one better?
View attachment 60085

 

[Geoffswoodwork]

yesterday I installed software for Creative Zen V series MPG player.
This morning on StartUp I got a blue screen crash followed by another Blue screen crash.
I ignored the prompts to Recover and started Normal.
All OK once started up. The Action Centre > Maintenance > Reliability History - reports the Sync Manager (Creative I think) and Zen Organiser to be responsible.
I presume these drivers are old for Win 7. The CD has 2006 on it?
But this again is similiar to previous crashes on start up.
This mornings Mini Dump is here if it helps. But I presume the obvious reason is out of date program/driver? (smart kid Eh?)
View attachment 60299

 

[Geoffswoodwork]

Are you able to offer any help yet please?

 

[Geoffswoodwork]

Sorry to go on but have you anything to suggest yet?

 

[zigzag3143]

Sorry to go on but have you anything to suggest yet?

Geoff

We are going to have difficulty in analyzing your DMP's because your verion is different from the RTM that MS released. Because it is different we dont have the symbols to analyze it properly.


Have you activated your version yet? Where did you get it, from a download or a retail store?

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


Loading Dump File [C:\Users\K\Desktop\031210-26847-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a13000 PsLoadedModuleList = 0x82b5b810
Debug session time: Fri Mar 12 06:38:20.452 2010 (GMT-4)
System Uptime: 0 days 0:00:21.294
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
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 86e93530, Terminating object
Arg3: 86e9369c, Process image file name
Arg4: 82c3bd50, Explanatory message (ascii)

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

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

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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.

MODULE_NAME: wininit

FAULTING_MODULE: 00000000 

DEBUG_FLR_IMAGE_TIMESTAMP:  0

PROCESS_OBJECT: 86e93530

IMAGE_NAME:  wininit.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xF4

CURRENT_IRQL:  0

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8d8ffc9c 82cef03b 000000f4 00000003 86e93530 nt+0xdce10
8d8ffcc0 82c72e44 82c3bd50 86e9369c 86e935c8 nt+0x2dc03b
8d8ffcf0 82c74cdf 86e93530 86e7b538 000036b1 nt+0x25fe44
8d8ffd24 82a5647a 00000000 000036b1 0021f730 nt+0x261cdf
8d8ffd34 773a64f4 badb0d00 0021f71c 00000000 nt+0x4347a
8d8ffd38 badb0d00 0021f71c 00000000 00000000 0x773a64f4
8d8ffd3c 0021f71c 00000000 00000000 00000000 0xbadb0d00
8d8ffd40 00000000 00000000 00000000 00000000 0x21f71c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

BUCKET_ID:  WRONG_SYMBOLS

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

 

[Geoffswoodwork]

I used the link provided by this Forum which took me to the MS download.
I believe it is their latest one?
Driver Developer Resources: Debugging Tools for Windows

 

[metalpryncyss]

Help please

I woke up this morning and started my computer and got the blue screen. My boyfriend looked into it and told me to upload the dmp and ask for some help. So here I am? Anybody have a clue about what I need to do?

 

[ttran]

I woke up this morning and started my computer and got the blue screen. My boyfriend looked into it and told me to upload the dmp and ask for some help. So here I am? Anybody have a clue about what I need to do?

Hi and welcome to SF!

This is pretty straight forward, it was caused by Atheros network adapter driver, please download and install fresh copy of it. Make sure to go to Device manager (My computer right click-->manage-->Device manager) and uninstall current version of driver before installing new one.

BUGCHECK SUMMARY:

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


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.817\080510-28111-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e93e50
Debug session time: Thu Aug  5 20:39:14.222 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:29.312
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 0, fffff880014b35d6}

Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+2edf7 )

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

Let us know if you need help

Tuan

 

[metalpryncyss]

Thanks so much for the fast reply. I wish I would have read this first, or even just have checked Windows Update. The driver was waiting to be installed. I actually went the route of disabling every driver and restarting over and over again and figured it out using process of elimination. Either way, I figured it out and saved the $150 that Geek Squad was going to charge.