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: Win 7 Blue screen crash at start up


10 Mar 2010   #1

Windows 7 Home Premium
 
 
Win 7 Blue screen crash at start up

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

My System SpecsSystem Spec
.

10 Mar 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Geoffswoodwork View Post
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-loc...d-problem.html


thanks
My System SpecsSystem Spec
11 Mar 2010   #3

Windows 7 Home Premium
 
 

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?
My System SpecsSystem Spec
.


11 Mar 2010   #4

64-bit Windows 8.1 Pro
 
 

navigate to c:/windows/minidumd and zip up the .dmp file .. attach it to your next post for analysis...
My System SpecsSystem Spec
11 Mar 2010   #5

Windows 7 Home Premium
 
 

Hmm, I see ...
Is this what you want?
Attachment 60083
My System SpecsSystem Spec
11 Mar 2010   #6

Windows 7 Home Premium
 
 

Or is this one better?
Attachment 60085
My System SpecsSystem Spec
12 Mar 2010   #7

Windows 7 Home Premium
 
 

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?)
Attachment 60299
My System SpecsSystem Spec
13 Mar 2010   #8

Windows 7 Home Premium
 
 

Are you able to offer any help yet please?
My System SpecsSystem Spec
15 Mar 2010   #9

Windows 7 Home Premium
 
 

Sorry to go on but have you anything to suggest yet?
My System SpecsSystem Spec
16 Mar 2010   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Geoffswoodwork View Post
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?

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\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
---------
My System SpecsSystem Spec
Reply

 Win 7 Blue screen crash at start up




Thread Tools



Similar help and support threads for2: Win 7 Blue screen crash at start up
Thread Forum
blue screen crash BSOD Help and Support
Blue Screen crash BSOD Help and Support
Blue Screen Crash BSOD Help and Support
blue screen crash at start up [urgent help please] BSOD Help and Support
Blue screen crash BSOD Help and Support
Crash (blue screen) BSOD Help and Support
Blue Screen Crash BSOD Help and Support

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 01:08 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33