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: Functions cause long delays, BSOD

14 Oct 2011   #1
dogiebitt

Windows 7 Home Premium 64 bit
 
 
Functions cause long delays, BSOD

Disclaimer: This is my mom's laptop, I am in no way held liable for what the logs in the zip file may show..

OS:
  • Windows 7 Home Premium x64
  • Original OS - Came with laptop from Best Buy - OEM Version
  • Laptop is about 1 year old, have never re-installed Windows on it.
Hardware:

  • Gateway NV55C03u
  • Pentium P6100
  • Intel HD Graphics
  • 3GB DDR3 RAM (1x Elpida 2GB stick, 1x Kingston 1GB stick - Came this way, I have done no upgrades to this laptop)
  • 320 GB Hard Drive
Symptoms:

  • Slowness attributed to commands causing the computer to "think". For example, right clicks to bring up context menus will sit for 10-30 seconds before bring them up. Hovering over the start button (or clicking it) will freeze everything but the mouse for 10-30 seconds. Placing the cursor into a field (actually clicking to place the blinking line) to type will hang for 10-30 seconds.
  • BSOD randomly. I think it has something to do with the iaStor.exe timing out (from the event logs), but then other signs point to something about a Kernel having a problem.
  • Cannot complete a "sfc /scannow", it stops around 76%. "sfc /verifyonly" will complete to 100% and tell me there were problems found, but skimming the log I did not see anything stand out at me. I don't know what I'm looking for though and there are thousands of lines of log.
  • Can't do chkdsk error I get is - "Chkdsk cannot run because the volume is in use." So I schedule it to run after a restart. During startup, the screen goes blue and some words appear, but then go away and it continues to boot into windows. They disappear too quick to read, but I think it had some acronyms like NTFS in there.



My System SpecsSystem Spec
.
14 Oct 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by dogiebitt View Post
Disclaimer: This is my mom's laptop, I am in no way held liable for what the logs in the zip file may show..

OS:
  • Windows 7 Home Premium x64
  • Original OS - Came with laptop from Best Buy - OEM Version
  • Laptop is about 1 year old, have never re-installed Windows on it.
Hardware:

  • Gateway NV55C03u
  • Pentium P6100
  • Intel HD Graphics
  • 3GB DDR3 RAM (1x Elpida 2GB stick, 1x Kingston 1GB stick - Came this way, I have done no upgrades to this laptop)
  • 320 GB Hard Drive
Symptoms:

  • Slowness attributed to commands causing the computer to "think". For example, right clicks to bring up context menus will sit for 10-30 seconds before bring them up. Hovering over the start button (or clicking it) will freeze everything but the mouse for 10-30 seconds. Placing the cursor into a field (actually clicking to place the blinking line) to type will hang for 10-30 seconds.
  • BSOD randomly. I think it has something to do with the iaStor.exe timing out (from the event logs), but then other signs point to something about a Kernel having a problem.
  • Cannot complete a "sfc /scannow", it stops around 76%. "sfc /verifyonly" will complete to 100% and tell me there were problems found, but skimming the log I did not see anything stand out at me. I don't know what I'm looking for though and there are thousands of lines of log.
  • Can't do chkdsk error I get is - "Chkdsk cannot run because the volume is in use." So I schedule it to run after a restart. During startup, the screen goes blue and some words appear, but then go away and it continues to boot into windows. They disappear too quick to read, but I think it had some acronyms like NTFS in there.

These were all related to your iaStor.sys (raid driver). I would re-install newest version available.
My System SpecsSystem Spec
14 Oct 2011   #3
dogiebitt

Windows 7 Home Premium 64 bit
 
 

As far as I know, all of the drivers on this laptop are up to date. I ran driver checked and it also told me the same thing.
isStor.exe driver is at version 10.6.0.1002 fro 5/20/2011
My System SpecsSystem Spec
.

14 Oct 2011   #4
dogiebitt

Windows 7 Home Premium 64 bit
 
 

Just got another BSOD. Here is some info from it. I'm not sure how to fix my symbols errors in the dump logs...
Code:
Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    7a
  BCP1:    FFFFF6FC5002BF20
  BCP2:    FFFFFFFFC00000B5
  BCP3:    0000000053455880
  BCP4:    FFFFF8A0057E42C8
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\101411-49639-01.dmp
  C:\Users\Eleonora\AppData\Local\Temp\WER-110916-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


==================
Minidump
==================

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


Loading Dump File [C:\Windows\Minidump\101411-49639-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 \SystemRoot\system32\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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02ea2670
Debug session time: Fri Oct 14 04:00:35.123 2011 (UTC - 4:00)
System Uptime: 0 days 2:18:25.496
*********************************************************************
* 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 \SystemRoot\system32\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 7A, {fffff6fc5002bf20, ffffffffc00000b5, 53455880, fffff8a0057e42c8}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+7cc40 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
14 Oct 2011   #5
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by dogiebitt View Post
Just got another BSOD. Here is some info from it. I'm not sure how to fix my symbols errors in the dump logs...
Code:
Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    7a
  BCP1:    FFFFF6FC5002BF20
  BCP2:    FFFFFFFFC00000B5
  BCP3:    0000000053455880
  BCP4:    FFFFF8A0057E42C8
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\101411-49639-01.dmp
  C:\Users\Eleonora\AppData\Local\Temp\WER-110916-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


==================
Minidump
==================

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


Loading Dump File [C:\Windows\Minidump\101411-49639-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 \SystemRoot\system32\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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02ea2670
Debug session time: Fri Oct 14 04:00:35.123 2011 (UTC - 4:00)
System Uptime: 0 days 2:18:25.496
*********************************************************************
* 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 \SystemRoot\system32\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 7A, {fffff6fc5002bf20, ffffffffc00000b5, 53455880, fffff8a0057e42c8}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+7cc40 )

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

We could use the new DMp's
My System SpecsSystem Spec
14 Oct 2011   #6
dogiebitt

Windows 7 Home Premium 64 bit
 
 

Alright I'll run it again. Took like 1.5 hours last time

In the mean time, attaching the latest minidump after the BSOD, if that helps.
My System SpecsSystem Spec
15 Oct 2011   #7
dogiebitt

Windows 7 Home Premium 64 bit
 
 

While running the "Windows_NT6_BSOD_v3.03_jcgriff2_" file from the How To thread, it BSOD again. Here is the new new minilog. Trying to run it again...
My System SpecsSystem Spec
15 Oct 2011   #8
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by dogiebitt View Post
While running the "Windows_NT6_BSOD_v3.03_jcgriff2_" file from the How To thread, it BSOD again. Here is the new new minilog. Trying to run it again...
Related to CI.dll. CI can be either a valid OS file or malware. Please run Malwarebytes just to rule out malware.
My System SpecsSystem Spec
15 Oct 2011   #9
dogiebitt

Windows 7 Home Premium 64 bit
 
 

Code:
Malwarebytes' Anti-Malware 1.51.2.1300
www.malwarebytes.org

Database version: 7955

Windows 6.1.7601 Service Pack 1
Internet Explorer 9.0.8112.16421

10/15/2011 3:27:21 PM
mbam-log-2011-10-15 (15-27-21).txt

Scan type: Quick scan
Objects scanned: 175984
Time elapsed: 12 minute(s), 8 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)
My System SpecsSystem Spec
15 Oct 2011   #10
dogiebitt

Windows 7 Home Premium 64 bit
 
 

So after numerous attempts at a chkdsk, it finally ran. I was then able to also run it in /f and /r. It found and fixed a bunch of errors
some bad clusters included
\windows\system32\driver~1\filere~1\igdlh6~2.inf\igdumd64.dll
\windows\system32\driver~1\filere~1\igdlh6~2.inf\igfxext.exe
\system~1\{3d3d8~1

I then tried to run sfc /scannow and it again got to 76%, and gave error

Code:
C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 76% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
CBS.log attached.
My System SpecsSystem Spec
Reply

 Functions cause long delays, BSOD




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD at random (short delays)
Hi there, I've been suffering from BSOD's on my rig since yesterday. Usually i can get it patched up by myself with a lot of tinkering, but this time the error messages aren't very helpful and not pointing to any specific program/driver/etc. The BSOD's started yesterday. I purchased a disk...
BSOD Help and Support
BSOD's, crashes and delays in being able to boot into Bios
I have a 2 and a half year old HP Pavilion P7-1020 desktop with the following specs: Motherboard H-Alvorix-RS880-uATX Chipset: AMD 785G (integrated ATI Radeon HD 4200 video) Processor: AMD Phenom II X4 960T quad core Ram: Hynix 8 gig (2 sticks of 4 gig) non ECC DDR3-1333 in slots 3 & 4...
BSOD Help and Support
BSOD after Win Updates + Mouse & Keyboard Typing Delays
I've been experiencing BSOD over the last year. I'm pretty sure it's happening after automatic windows updates. I'm now experiencing delays in typing and mouse usage sporadically throughout the day. Not sure if they are related. Desktop PC - Custom Build Windows 7 64 bit i7-2600K 3.4GHz...
BSOD Help and Support
Long delays at Welcome screen and subsequent black screen
i;ve been experiencing some unusually long delays at the welcome screen followed by a black screen that stays on for sometime. During the black screen, the cursor is visible and I am able to move the cursor. The problems seem to start after I installed a long list of updates and SP 1. ...
Performance & Maintenance
BSOD at various times / functions
Guys, after a period of stability lasting almost a year (last encountering this problem in Oct of 2010) I find that the issue has reared it's ugly head again. I tend to find it occuring (but not exclusively limited to) when I'm browsing the Internet, although also regularly occurs when I have...
BSOD Help and Support
Install is stalling and has very long delays
First off I had the downloadable windows 7 x64 7100 rc installed on my computer for a long time and decided instead of pirating win7 this time I would actually buy it using the student edition x64 pro downloaded. So i tried to install this after downloading it and extracting it and everything...
Installation & Setup


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 04:10.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App