Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs


[SOLVED] BSOD 0x8E Possibly driver?

This is a discussion on [SOLVED] BSOD 0x8E Possibly driver? within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category.


Reply
 
Thread Tools Search this Thread
Old 08-20-2013, 01:32 AM   #1
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



OS -Windows 7
· x86 (32-bit)
· What was original installed OS on system? Windows 7 32bit.
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retail.
· Age of system (hardware) Around 4 years.
· Age of OS installation - have you re-installed the OS? - Not even a month old installation.

· CPU - Pentium Dual-Core 2GHz
· Video Card - Integrated GMA 4500
·
·

· System Manufacturer - Asus
· Exact model number (if laptop, check label on bottom) - F52Q

Hello I've got a BSOD yesterday all of a sudden.
First I thought it might have been cause by some power failure as my old TV died a few minutes after I received the BSOD. But using BlueScreenView I determined halmacpi and ntkrnlpa.exe being the probable cause.
Here's the dump log, please help.

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


Loading Dump File [C:\Windows\Minidump\081913-19936-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\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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82a43000 PsLoadedModuleList = 0x82b8b810
Debug session time: Mon Aug 19 22:47:03.958 2013 (UTC + 2:00)
System Uptime: 0 days 2:58:18.800
*********************************************************************
* 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\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
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82c8bfe8, b61a0bd4, 0}

***** 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 : ntkrnlpa.exe ( nt+248fe8 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82c8bfe8, The address that the exception occurred at
Arg3: b61a0bd4, Trap Frame
Arg4: 00000000

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

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

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

MODULE_NAME: nt

FAULTING_MODULE: 82a43000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ed4

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt+248fe8
82c8bfe8 8b83b8000000    mov     eax,dword ptr [ebx+0B8h]

TRAP_FRAME:  b61a0bd4 -- (.trap 0xffffffffb61a0bd4)
ErrCode = 00000000
eax=00000000 ebx=00000068 ecx=84ad4030 edx=746c6644 esi=8806a410 edi=00000000
eip=82c8bfe8 esp=b61a0c48 ebp=b61a0cb4 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt+0x248fe8:
82c8bfe8 8b83b8000000    mov     eax,dword ptr [ebx+0B8h] ds:0023:00000120=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82cc0631 to 82c8bfe8

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b61a0cb4 82cc0631 00000000 84992358 00000001 nt+0x248fe8
b61a0ccc 82aeb223 84992358 b61a0cf8 b61a0d04 nt+0x27d631
b61a0d1c 82a864f4 00000001 00000000 b61a0d34 nt+0xa8223
b61a0d34 77586344 badb0d00 0012f2f8 00000000 nt+0x434f4
b61a0d38 badb0d00 0012f2f8 00000000 00000000 0x77586344
b61a0d3c 0012f2f8 00000000 00000000 00000000 0xbadb0d00
b61a0d40 00000000 00000000 00000000 00000000 0x12f2f8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt+248fe8
82c8bfe8 8b83b8000000    mov     eax,dword ptr [ebx+0B8h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt+248fe8

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlpa.exe

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------
The windows 7 installed on this laptop isn't even a month old yet. Also before I did a reinstall I remember getting a BSOD while trying to update Adobe Flash Player, I didn't save the log then though and reinstalled windows a week or so after.
Kshksh is offline   Reply With Quote
Sponsored Links
Advertisement
 
Old 08-20-2013, 01:44 AM   #2
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Hi,

Please run the jcgriff app - http://www.techsupportforum.com/foru...ta-452654.html

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 08-20-2013, 01:54 AM   #3
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



Here it is.
Attached Files
File Type: zip Windows7_Vista_jcgriff2.zip (536.2 KB, 34 views)
File Type: zip perfmon.zip (122.1 KB, 27 views)
Kshksh is offline   Reply With Quote
Old 08-20-2013, 02:03 AM   #4
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



There's one dump attached and it's of the KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) bugcheck.

The processor identified a problem, but Windows was unable to deal with it. This problem can appear when one of these issues occurs:
  • Low disk space in the primary system drive
  • A driver bug (which may be identified in the message).
  • Video adapter problems
  • A BIOS bug
  • BIOS caching or shadowing
Update to Service Pack 1 ASAP: Learn how to install Windows 7 Service Pack 1 (SP1)



In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.


Quote:
ATKACPI 909e2000 909ea000 Thu Dec 14 02:11:57 2006 (4580f93d) 0000a891 ATKACPI.sys
^^ ATK Hotkey ATK0101 ACPI Utility Driver

Update via - F52Q - Notebooks & Ultrabooks - ASUS

Quote:
Rtlh86 909a5000 909bd000 Mon Jun 25 01:37:23 2007 (467f5493) 0002352a Rtlh86.sys
^^ Realtek 8101/8168/8169 Wired Network Driver

Update via - F52Q - Notebooks & Ultrabooks - ASUS

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 08-20-2013, 06:30 AM   #5
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



I'll get SP and update realtek and hotkey drivers. I have a question though.

Could it have been the fault of RAM, as it was quite heavily loaded at the moment BSoD occured? I was using an internet browser, an instant communicator and listening to music with last/fm scrobbler so my only 2GB or RAM were quite loaded.
Also I daemon wasn't even started at the moment, could it still have been the cause?

Thank you for everything.
Kshksh is offline   Reply With Quote
Old 08-20-2013, 08:47 AM   #6
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



Updated drivers, also could the daemon driver be the cause even if I wasn't using it at the moment?
Kshksh is offline   Reply With Quote
Old 08-20-2013, 09:00 AM   #7
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



Apparently after updating Realtek driver I got "Realtek PCIe GBE Family Controller is disconnected from network." in Event Viewer and rolled back to previous driver.
Kshksh is offline   Reply With Quote
Old 08-20-2013, 10:42 AM   #8
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



I'm sorry for bumping the thread like that but I didn't find the 'edit' option.

Please disregard previous 2 posts. I'll summarize everything here:

-I uninstalled daemon tools. The bsod that occured on my previous installation of windows was probably caused by it as well as I think that was my first time using that version of Daemon.
-I update the realtek driver but got "Realtek PCIe GBE Family Controller is disconnected from network" error in Event Viewer and rolled back to previous driver, no errors on this one.
-I'll also get the SP today and report if anything happens.

Thank you for help.
Kshksh is offline   Reply With Quote
Old 08-20-2013, 11:02 AM   #9
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Hi,

Good work, please keep me updated.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 08-20-2013, 08:52 PM   #10
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



Updating.

-Installed all windows updates along with SP1.

-Also did memtest to exclude faulty memory, for 6 passes, no error.

Now I'm just waiting for my boots to stabilize since after bsod they were taking a bit longer. Now that I got everything installed they should get back to normal though.
Kshksh is offline   Reply With Quote
Old 08-20-2013, 09:22 PM   #11
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Hi,

Fantastic work, please keep me updated.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 08-31-2013, 07:30 AM   #12
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



Updating since some time passed.

All's fine and dandy. I just got a few application errors from Media Player Classic but I assume it just crashed, once at an incomplete file so I think it's understandable.

Thank you again for the support.
Kshksh is offline   Reply With Quote
Old 08-31-2013, 11:29 AM   #13
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Hi,

Great, thank you for the updates and cooperation. Marked as solved.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 09-04-2013, 02:16 PM   #14
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



It was too soon to be happy after all. I got another BSOD just now. I'm dumping the report files here. Should I open a new thread instead?
Attached Files
File Type: zip Windows7_Vista_jcgriff2 and perfmon.zip (1.07 MB, 27 views)
Kshksh is offline   Reply With Quote
Old 09-04-2013, 03:03 PM   #15
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Hi,

No that won't be necessary, I've marked it as unsolved again.

The attached DMP file is of the same bugcheck as above.

Quote:
A device is disabled preventing it from working properly.Details:The device, Disk drive, is disabled. If this device is no longer used it may be intentionally disabled. The Plug and Play ID for this device is USBSTOR\DISK-VEN_GENERIC--PROD_MULTI-CARD-REV_1.00\20071114173400000-0.
Do you have an external hard drive connected but disabled, or possibly internal? I'd recommend removing it entirely for troubleshooting purposes.

Quote:
The Security Center reports that Windows Update is disabled.
^^ Why?? Enable Windows Update ASAP and install all relevant and important security updates, etc.

I'd also like you to please run some hardware diagnostics so we can be sure. Start with a Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

-------------------------------------------------------------------------------------------------------------

Chkdsk:

Chkdsk:
There are various ways to run Chkdsk~


Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 09-04-2013, 03:36 PM   #16
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



Quote:
Do you have an external hard drive connected but disabled, or possibly internal? I'd recommend removing it entirely for troubleshooting purposes.
I have a disabled card reader. It's broken mechanically but I didn't want to remove it and accidentialy damage anything else.

Quote:
^^ Why?? Enable Windows Update ASAP and install all relevant and important security updates, etc.
I always do my updates manually, almost up-to-date now. I'll update the rest just to be sure.


Quote:
I'd also like you to please run some hardware diagnostics so we can be sure. Start with a Memtest for NO LESS than ~8 passes (several hours):
I did Memtest last time I got BSOD, but only for 6 passes and it turned out fine.
Faulty RAM is my most suspected cause right now actually, do you think it could have been the case even if it turned out fine last time?
Also I'll do a memtest tomorrow for 8 passes too but I was thinking of switching the ram anyway so I'll probably get new soon.

Quote:
If chkdsk turns out okay, run Seatools.
I attached results of chkdsk. Can't run Seatools though, I tried last time I got the BSOD but it didn't initialize with some error. I don't quite trust the windows one too.
Also the hard disk is almost new so I don't want to think it's the cause.
Attached Files
File Type: txt CHKDSKResults.txt (7.5 KB, 28 views)
Kshksh is offline   Reply With Quote
Old 09-04-2013, 04:27 PM   #17
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Quote:
I have a disabled card reader. It's broken mechanically but I didn't want to remove it and accidentialy damage anything else.
Definitely remove it.

Quote:
I always do my updates manually, almost up-to-date now. I'll update the rest just to be sure.
Understood. For reference, you can enable Update and have it set to check but don't download or install without approval.

Quote:
Faulty RAM is my most suspected cause right now actually, do you think it could have been the case even if it turned out fine last time?
Very possible, I'd let it go for at least 8, yes.

Quote:
Also the hard disk is almost new so I don't want to think it's the cause.
I'd still like to test it. Use the DOS version if the OS environment is too unstable - SeaTools for DOS tutorial

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 09-05-2013, 06:09 AM   #18
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



Quote:
Definitely remove it.
It's soldered to the motherboard so I can't actually fully remove it, I was thinking I could take out the cable supplying power to it, should I?

Quote:
Very possible, I'd let it go for at least 8, yes.
I'll let it go tonight to be sure for 8 passes.

Quote:
I'd still like to test it. Use the DOS version if the OS environment is too unstable - SeaTools for DOS tutorial
I'll do this as well after memtest to be sure.

Also I consulted a known IT and he said that the daemon could mess up the registry among other things even if it's uninstalled by now. Do you think it's possible to have been the cause? I'll do a clean install of Windows to be sure.
Kshksh is offline   Reply With Quote
Old 09-05-2013, 01:07 PM   #19
TSF Enthusiast
 
Patrick's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2012
Location: Ring 0
Posts: 4,349
OS: W8.1 x64



Hi,

Quote:
It's soldered to the motherboard so I can't actually fully remove it, I was thinking I could take out the cable supplying power to it, should I?
Yes. The only thing that concerns me is the fact the you said it's physically damaged, and whilst that was the case, you had it connected. It could have worst case also damaged the motherboard, but let's hope that's not the case.

Quote:
daemon could mess up the registry among other things even if it's uninstalled by now. Do you think it's possible to have been the cause?
Daemon Tools is a troublemaker, yes. I seemed to have missed that in your drivers list or I would have certainly missed it, my apologies.

Regards,

Patrick
Patrick is offline   Reply With Quote
Old 09-06-2013, 10:46 AM   #20
Registered Member
 
Join Date: Aug 2013
Posts: 30
OS: Win7



I ran memtest for 9 passes, it didn't show any errors. Seatools was also fine.

Quote:
Yes. The only thing that concerns me is the fact the you said it's physically damaged, and whilst that was the case, you had it connected. It could have worst case also damaged the motherboard, but let's hope that's not the case.
Well, I mean a bit of plastic is bent inside it so it can't be used. It's safe to remove the cable supplying power, right? I want to be sure it doesn't cause any problems.

Quote:
Daemon Tools is a troublemaker, yes. I seemed to have missed that in your drivers list or I would have certainly missed it, my apologies.
I uninstalled it after the first bluescreen I wrote about in opening post. Do you mean that the driver was still present in the 2nd bsod report I submitted 2 days ago?
If so I hope it was the case, and won't be a problem anymore now that I did a clean install of Windows.
So assuming I had problems with daemon, which alternative do you think will be the safest to use? Alcohol 52%? Virtual Clone Drive?
Kshksh is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
Computer running slowly
Hello, My laptop is functioning at a very slow speed when gaming on new games. Here is my dxdiag, could you please recommend what changes I could make to make my laptop work better? Thanks in advance, ------------------ System Information ------------------ Time of this report: 6/18/2013,...
esxu PC Gaming Support 2 06-20-2013 11:09 AM
Computer running slowly
Hello, My laptop has not been working at the rate it should be, when I play games, it has very low framerates, and when I copy stuff to my hard drive, it takes ages (7-8MB/s) when originally it worked at around 30 MB/s, Here is my Dxdiag and the link to my speccy results: ------------------...
esxu Windows 8, 8.1 Support 3 06-19-2013 02:00 AM
Windows Xp slow boot after splash screen
After the Windows Xp splash screen I get about 30 to 40 seconds of blackness (could be more) before the cursor appears. When I start in Safe Mode it takes a long time to load mup.sys but that could just be because it's the last one to load. Here's by most recent ntbtlog.txt: Service...
Sulla Windows XP Support 5 06-17-2013 10:29 AM
0X000000F4
Hello- Randomly my HP Pavilion running XP crashes with: 0X000000F4 0X000000003 0X8ACC9298 .... Any Clues- I ran all hardware tests with no issues. Thanks, Jeff
jfuchs10 BSOD, App Crashes And Hangs 9 08-15-2012 07:52 AM
windows 7 freezes during startup
i have been having issues since friday my computer seems to freeze on startup. it gets to the welcome screen and freezes. someone recommended doing a boot log but i don't know how to know what it means. the whole thing is to long but here is the last part someone please help Loaded...
mucwen Windows 7 , Windows Vista Support 1 12-11-2011 08:32 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2


All times are GMT -7. The time now is 10:28 AM.


vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Copyright 2001 - 2015, Tech Support Forum

Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts

 

Partially Powered By Products Found At Lampwrights.com