1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Blue screen of death.

Discussion in 'BSOD, App Crashes and Hangs' started by Gerry7371, Jul 19, 2016.

  1. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    Computor is now constantly crashing in normal mode, but is fine in safe mode.
    Last error message I received ieved said issue was ode 1e. I've run malware software as well as virus scan with no results. Don't know what to do from here. Using tablet to get help as desktop in normal mode doesn't last.
    Please help.
     
  2. allheart55 (Cindy E)

    allheart55 (Cindy E) Administrator Administrator

    Joined:
    Jun 11, 2009
    Messages:
    10,271
    Location:
    Pennsylvania
    Operating System:
    Windows 10
    Computer Brand or Motherboard:
    ASUS M4A77TD AM3 AMD 770 ATX AMD
    CPU:
    AMD Phenom II X6 1090T-Thuban 3.2GHz
    Memory:
    Crucial-DDR3 SDRAM 1333-8GB
    Hard Drive:
    WD Caviar Black SE HDD 640 GB - WD Caviar Black SE HDD 500 GB
    Graphics Card:
    Sapphire Radeon HD-7870 2GB
    Power Supply:
    CORSAIR CMPSU-750W
    Did you mean Error Code 1E (0x0000001E) ?
     
  3. Drew

    Drew Registered Members

    Joined:
    Mar 29, 2016
    Messages:
    290
    Operating System:
    Windows 10
    The prudent remedy would be to save any data necessary (whilst in Safe) and then re-load the OS.
     
  4. Tony D

    Tony D Administrator Administrator

    Joined:
    Sep 25, 2009
    Messages:
    4,709
    Location:
    SE Pennsylvania, USA
    Operating System:
    Windows XP Professional
    allheart55 (Cindy E) likes this.
  5. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    I thought it was a small e but that looks like what it was. I don't have a disk to reload the OS as it was already loaded when I bought the unit. It's an E machine bought at Best Buy.
    Can't download anything as it doesn't give me internet access in safe mode
     
  6. Tony D

    Tony D Administrator Administrator

    Joined:
    Sep 25, 2009
    Messages:
    4,709
    Location:
    SE Pennsylvania, USA
    Operating System:
    Windows XP Professional
    Thanks for the clarification on the error code.

    If you can connect using an Ethernet cable, start your computer in Safe Mode with Networking. You should be able to access the Internet.
     
  7. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    System Information (local) Computer name: HOME-PCWindows version: Windows 7 Service Pack 1, 6.1, build: 7601
    Windows dir: C:\Windows
    Hardware: ET1831, eMachines, EMCP73VT-PM
    CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
    2 logical processors, active mask: 3
    RAM: 4025729024 bytes total
    Crash Dump Analysis
    Crash dump directory: C:\Windows\Minidump
    Crash dumps are enabled on your computer.On Tue 7/19/2016 9:36:52 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\071916-33165-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80002A7E3EF)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Tue 7/19/2016 9:36:52 PM GMT your computer crashedcrash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ci.dll (CI!CiFreePolicyInfo+0x58FF) Bugcheck code: 0xA (0x80, 0x2, 0x1, 0xFFFFF80002A7E3EF)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ci.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Code Integrity Module
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Tue 7/19/2016 6:55:53 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\071916-65317-01.dmp
    This was probably caused by the following module: usbhub.sys (usbhub+0x17FA) Bugcheck code: 0xFE (0x8, 0x6, 0x6, 0xFFFFFA80056C1000)
    Error: BUGCODE_USB_DRIVER
    file path: C:\Windows\system32\drivers\usbhub.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Default Hub Driver for USB
    Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Sat 7/2/2016 3:27:06 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\070216-41667-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000313C81E, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Wed 6/29/2016 1:11:38 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\062916-46535-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x5472) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Mon 6/6/2016 10:31:33 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\060616-48750-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E8BFE4, 0xFFFFF88007C3DF50, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Sun 5/29/2016 1:29:08 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\052916-58203-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F1BF60, 0xFFFFF8800619E0F0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Thu 10/15/2015 12:03:39 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\101615-31871-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x74200) Bugcheck code: 0x1 (0x77A9DB1A, 0x0, 0xFFFF, 0xFFFFF88005C70C60)
    Error: APC_INDEX_MISMATCH
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that there has been a mismatch in the APC state index.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Thu 8/27/2015 12:22:32 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\082715-30513-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CC9116, 0xFFFFF880073C5CD0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Tue 8/11/2015 1:50:59 PM GMT your computer crashedcrash dump file: C:\Windows\Minidump\081115-30420-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CDD416, 0xFFFFF88006A60F50, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Conclusion
    13 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
    Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
     
  8. Tony D

    Tony D Administrator Administrator

    Joined:
    Sep 25, 2009
    Messages:
    4,709
    Location:
    SE Pennsylvania, USA
    Operating System:
    Windows XP Professional
    Looks like it may be a driver problem. Try a System Restore to an earlier date.
    1. From the Start menu, type: Restore in the Search programs and files dialog box.
    2. From the list of results, click System Restore.
    3. In the System Restore window, click Next.
    4. From the list of restore points, select the Date and Time you wish to restore from.
     
  9. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    I've done 2 system restores today going back as far as 7/3/16. I know that usually works but not today!
     
  10. Tony D

    Tony D Administrator Administrator

    Joined:
    Sep 25, 2009
    Messages:
    4,709
    Location:
    SE Pennsylvania, USA
    Operating System:
    Windows XP Professional
    Looking thru the report, you've been having crashes due to driver issues for a year now. Many drivers don't load when in Safe Mode. So, I'm guessing there's an offending driver that loads when in normal mode that's causing the problem.

    However, you can try going into msconfig and disabling all startup items except for your protection software. btw: What protection do you use?

    To get to msconfig,
    Click on the Windows 7 start icon, usually in the bottom left corner of your screen
    Type msconfig in the search box
    When msconfig starts, click on the Startup tab and uncheck everything except your protection software.

    Try starting in Normal mode.
     
  11. Rustys

    Rustys Registered Members

    Joined:
    Feb 29, 2016
    Messages:
    1,656
    Location:
    127.0.0.1
    Operating System:
    Linux Based
    Computer Brand or Motherboard:
    Compaq H3900 (Windows 2002)
    CPU:
    Intel (R) PXA250
    Memory:
    64 MB RAM 48 MB ROM
    Hard Drive:
    Yes
    Graphics Card:
    4 D
    Power Supply:
    Solar
    Gerry you said that you do not have the disk to reload the OS on most systems have a hidden recovery partition.

    Now a days they do not include the software (disk) to restore your system you creat them off the system.
     
  12. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    U'd have to walk me thru that. Never done before.
     
  13. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    Ok. Will try that and let you know.
     
  14. Drew

    Drew Registered Members

    Joined:
    Mar 29, 2016
    Messages:
    290
    Operating System:
    Windows 10
    Gerry,

    Ok, I did a wee bit of research for you...

    Never mind the time & frustration of trying other ways to fix this or to find out what is the cause. Since you don't have a Win7 disc...

    Hit F11 to access the Restore to Factory and re-do the thing internally using its Recovery Partition. Remember, as I said earlier, to save any critical, non-backed-up, data whilst in Safe before doing this.
     
  15. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    I currently use AVG - the free version
     
  16. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    I have an external drive that I use as my backup. I'm assuming that it would include all my pictures and docs that I currently have on my PC now if it's been backed up recently, correct?
     
  17. Drew

    Drew Registered Members

    Joined:
    Mar 29, 2016
    Messages:
    290
    Operating System:
    Windows 10
    Gerry,

    Yes, there is a good chance that's true... depends some on what you had told it to back-up.
     
  18. DSTM (Dougie)

    DSTM (Dougie) Registered Members

    Joined:
    May 3, 2009
    Messages:
    8,270
    Location:
    SYDNEY AUSTRALIA
    Operating System:
    Windows 7
    Have a look on your External and see what it contains. Otherwise you are guessing.
     
  19. Drew

    Drew Registered Members

    Joined:
    Mar 29, 2016
    Messages:
    290
    Operating System:
    Windows 10
    Gerry,

    You should look 1st, as Doug said & not assume. But, I was more thinking of putting critical data (pics, docs, et al) on a USB or DVD whilst doing the Reset. Lot better than thinking about the whole back-up drive. Just grab the few things you may want & save that separately & specifically... apart from the Ext.
     
  20. Gerry7371

    Gerry7371 Registered Members

    Joined:
    Oct 22, 2015
    Messages:
    41
    Operating System:
    Windows 7
    How would I do that? I did check my drive and it does have my data, but what you suggest sounds like a better sure solution.
    Also, today I've now tried to boot up and it's now. Rashid even in safe mode. Looks like I have some serious issues.
    Could it be my hard drive that's going?
     

Share This Page