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: I have been getting random BSOD's

21 Nov 2012   #1
Zoidbort

Win7 Pro
 
 
I have been getting random BSOD's

So over the past 3 weeks I have been getting random BSOD's and at first my SABNDZB was having issues so I uninstalled it and all seemed stable but suddenly 3 days ago I started getting BSOD's again.
No issues for hours in Safe Mode (points to me that it is a driver more so than hardware but) but when in standard boot it seems to go to a BSOD at random times within 1-2 hours of boot up.
After enabling all the goodies and running verifier it posted, upon boot up, an error in the hidclass.sys file.
Now that seems generic after reading here so I have attached the zip for a peek.
Cheers in advance for the help!


My System SpecsSystem Spec
.
21 Nov 2012   #2
Zoidbort

Win7 Pro
 
 

Sorry Mods for posting in a similar previous post.
Thanks for putting it into my own thread.
My System SpecsSystem Spec
21 Nov 2012   #3
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Dump Files - Configure Windows to Create on BSOD

Follow it manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump.

We need to see the crahsdumps.

Anyway, hidclass is USB related.

For the port, first, uninstall and reinstall the USB ports drivers.
  1. Right click on Computer icon > manage. It will open the computer management window.
  2. Click on "Device Manager" in the left pane, it will list all installed devices up.
  3. Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
  4. Click on one item to select, then right click and uninstall.
  5. Do the same for all.
  6. Restart the computer.
  7. At restart, windows will auto configure the appropriate drivers.
And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off


For the devices, first, detach all the USB devices other than the keyboard and mouse.
Then, Update the drivers for them all, including the keyboard and mouse, if any third party drivers are installed for them.
My System SpecsSystem Spec
.

21 Nov 2012   #4
Zoidbort

Win7 Pro
 
 

Woke up this morn and did the USB removal...no BSOD all day while I was at work.
I had my CCleaner clean out dump files so I haven't any to upload but I will as soon as a new BSOD appears.
Cheers for the reply and help mate!
My System SpecsSystem Spec
22 Nov 2012   #5
Zoidbort

Win7 Pro
 
 

Well that was a nice 20 hours of peace but it came back overnight.
This time a new error...boot.ini issue from a little reading I did.
Will run a chkdsk /r now.
Dump included.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [H:\Windows\Minidump\112212-13837-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`0364a000 PsLoadedModuleList = 0xfffff800`0388e670
Debug session time: Thu Nov 22 05:02:33.559 2012 (UTC - 8:00)
System Uptime: 0 days 22:26:24.026
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa00036cbe7a, 2, 8, fffffa00036cbe7a}

***** 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+7efc0 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
22 Nov 2012   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

I have to analyze the dump myself, in my own way ..... to suggest anything.
My System SpecsSystem Spec
22 Nov 2012   #7
Zoidbort

Win7 Pro
 
 

Cool, thanks very much for the help.
Check Disk was running when I left for work.
My System SpecsSystem Spec
24 Nov 2012   #8
Zoidbort

Win7 Pro
 
 

Got another one...all was well for the past 35 hours or so...PC was asleep.
Memory Management

Code:
Loading Dump File [H:\Windows\Minidump\112412-18142-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`0360b000 PsLoadedModuleList = 0xfffff800`0384f670
Debug session time: Fri Nov 23 23:00:30.784 2012 (UTC - 8:00)
System Uptime: 1 days 16:06:03.877
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8008dfbe80, ffff, 0}

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

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: nt

FAULTING_MODULE: fffff8000360b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800036f5b50 to fffff80003689fc0

STACK_TEXT:  
fffff880`0bd658d8 fffff800`036f5b50 : 00000000`0000001a 00000000`00041790 fffffa80`08dfbe80 00000000`0000ffff : nt+0x7efc0
fffff880`0bd658e0 00000000`0000001a : 00000000`00041790 fffffa80`08dfbe80 00000000`0000ffff 00000000`00000000 : nt+0xeab50
fffff880`0bd658e8 00000000`00041790 : fffffa80`08dfbe80 00000000`0000ffff 00000000`00000000 fffff800`037882c1 : 0x1a
fffff880`0bd658f0 fffffa80`08dfbe80 : 00000000`0000ffff 00000000`00000000 fffff800`037882c1 fffffa80`14aec2b0 : 0x41790
fffff880`0bd658f8 00000000`0000ffff : 00000000`00000000 fffff800`037882c1 fffffa80`14aec2b0 00000000`00000000 : 0xfffffa80`08dfbe80
fffff880`0bd65900 00000000`00000000 : fffff800`037882c1 fffffa80`14aec2b0 00000000`00000000 fffff680`003ffef8 : 0xffff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt+7efc0
fffff800`03689fc0 48894c2408      mov     qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt+7efc0

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntoskrnl.exe

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
My System SpecsSystem Spec
24 Nov 2012   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If you dont supply the dump, how can I see it? I told you that I want to analyze it at my own to infer anything.

Blue Screen of Death (BSOD) Posting Instructions
My System SpecsSystem Spec
24 Nov 2012   #10
Zoidbort

Win7 Pro
 
 

Ah sorry, dmp file zipped and added.
My System SpecsSystem Spec
Reply

 I have been getting random BSOD's




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD after start and Random stuck on windows logo screen
Heyy.. So yesterday due to a sudden power outage (happens allot here), my windows started behaving erratically. First when the power came on my windows 7 ultimate 64 bit, was stuck on windows logo. i waited for about 20 mins and it was still stuck. The HDD read activity light on my casing was...
BSOD Help and Support
Random BSOD problems in the past 2 days. Random errors at random times
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
BSOD Help and Support
BSOD at seemingly random times, memory dump blaming random drivers
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
BSOD Help and Support
Random BSOD at random moments on Toshiba L500 laptop; graphics card?
My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now. It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem. Four days ago it started blue...
BSOD Help and Support
Random BSOD with random error code at random moment
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
BSOD Help and Support
BSOD doing random things (Google Chrome, minecraft, random times)
I have finally had it up to here with the BSODs, so I really need help. I ran a windows memtest and it detected no errors. I just finished updating to SP1 with pretty much most updates too. The BSODs I get the most are: Driver IRQL not less or Equal System Service Exception and these two I...
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 17:14.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App