BSOD 0x3B and 0x1E

Page 4 of 7 FirstFirst ... 23456 ... LastLast

  1. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #31

    Installations are of two types. Clean install and Repair install. You are suggested to perform a clean install; as the repair install will not cure your issue.

    When you are on Step 8, you can format the disc/partition.

    Read it a few times before you start. If needed, get a print out and start installing following step by step.
    Last edited by Arc; 02 Jan 2014 at 05:44. Reason: typo; as always.
      My Computer


  2. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #32

    I do agree with Arc. A clean install is the proper thing to do.
      My Computer


  3. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #33

    I have reinstalled (clean) twice in the past 3 weeks, and the problem resurfaces once I start installing Windows Updates. I spent yesterday gathering all my Keys and such. I will read thru the clean install. Setting up Clean Install with formatting and will see if this remedies the situation.
    Last edited by SekitaLuna; 02 Jan 2014 at 20:36. Reason: clarification
      My Computer


  4. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #34

    I see no place in all this thread that you stated that you have done two clean installs before post #33.
    I'm I missing something?

    Where did you get your copy of Windows 7 to do the clean install?
      My Computer


  5. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #35

    SekitaLuna said:
    Seems it doesn't matter what I am doing, I will get a BSOD after the computer has ran for a bit. It has crashed while playing flash games, Steam games, and just sitting and idling. I have pulled the computer apart and cleaned any dust in there just in case it was a dust insulated overheating issue. I have checked drivers, reinstalled drivers, reinstalled Windows and I am at my wits end on what to do.
    Was in first post, although I did not specifically state I had reinstalled twice. My Comcast date usage limit was almost hit due to this. A reinstallation disc came with the computer as it was pre-built. I used this to do a "clean" install but the problems always resurfaced. I did not reformat before though as I had read that it was not necessary with Win 7. This time I made a Win 7 SP1 ISO image from heidoc.net. (Link was from Clean Install page Arc posted) I clicked the advanced options and formatted the partition, then reinstalled Win 7 SP1 from the ISO DVD.

    Windows 7 Direct Download Links

    Currently doing updates. I have installed MSE and MBAM but the first of the two installations (MSE) said "AMD" so I didn't use that one.

    Everything seems to be going well. All updates going thru without a hitch.
    Last edited by SekitaLuna; 02 Jan 2014 at 20:37. Reason: Adding SF Grab All/Update
      My Computer


  6. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #36

    UPDATE:
    Computer is now fully updated, have not had a problem as of yet. Will return in 24 hours or if I have a problem. Uploading a current Speccy and SF text. Thank you both Arc and Layback for all your helpful insight. I'm so glad I found this site.
      My Computer


  7. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #37

    I guess I am gonna suck it up and take the unit to a professional. I am SO frustrated at this point and I am ready to throw the tower across the room. 2 BSOD not long after I made the above post.

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Fri 1/3/2014 3:41:06 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010214-22744-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0xA87B1)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF93F187B1, 0xFFFFFFFFA6532C34, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    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 Fri 1/3/2014 3:41:06 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: win32k.sys (win32k!EngUnmapFontFileFD+0x1AA6D)
    Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF93F187B1, 0xFFFFFFFFA6532C34, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
    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 Fri 1/3/2014 3:34:31 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010214-21637-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
    Bugcheck code: 0xA (0xFFFFFFFF8BDA0008, 0x2, 0x1, 0xFFFFFFFF82CFC03D)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntkrnlpa.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.
      My Computer


  8. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #38

    I went to make coffee and all hell broke loose with your computer.
    Hang in there.
    Arc is not online at the time to look at your BSOD.

    I try to remember that their might be more than one problem that is hiding the other problem.
      My Computer


  9. Posts : 37
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #39

    Layback Bear said:
    I went to make coffee and all hell broke loose with your computer.
    Hang in there. .

    ahahaha yea I have a cup as well. I just can't understand what the heck is wrong with my computer. I have ordered a new HDD and will probably order a new graphics card as well. I am seriously considering taking it to a shop tomorrow. I don't know what else to do. Thank you for making me laugh.. I needed it.

    Edit: Just a thought, I had two partitions when I reinstalled Windows. One said system reserved, I didn't touch that one.
      My Computer


  10. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #40

    I do believe when you do a format and clean install it cleans all the drive and then installs Windows. So I'm not understanding what exactly you are doing.

    When was the last time you did the Clean Insatall with Format.
    12 hours ago/1 day ago/ how long has it been?
      My Computer


 
Page 4 of 7 FirstFirst ... 23456 ... LastLast

  Related Discussions
Our Sites
Site Links
About 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 23:21.
Find Us