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: BSOD 0x3B and 0x1E

30 Dec 2013   #11
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Before the BIOS update, your SATA controller mode was AHCI. I think it is AHCI still, otherwise windows wont boot normally.

Let us know about any event later.


My System SpecsSystem Spec
.
30 Dec 2013   #12
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

I have had the computer on all day without any BSOD! I am hoping the BIOS update and SP1 installation has solved the issue. Thank you so much Arc, for all your time and effort to help me. It is sincerely appreciated. Hopefully (fingers crossed) my computer will have no more hissy fits. If it does.. I know where to come for help!
My System SpecsSystem Spec
31 Dec 2013   #13
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Good news

Let us know for any further issue.
My System SpecsSystem Spec
.

31 Dec 2013   #14
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

Alright, things went well all day yesterday, computer was shutdown last night, and within about an hour I had a BSOD.
Seems my comp is still having hissy fits.

On Tue 12/31/2013 4:31:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-33727-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xC30E)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880033545B8, 0xFFFFF88003353E10, 0xFFFFF8800124730E)
Error: CACHE_MANAGER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 12/31/2013 3:47:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-28345-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A010523EB0, 0xFFFFF8A010524AF0, 0x4C4F940)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

My System SpecsSystem Spec
31 Dec 2013   #15
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It seems that something is somehow causing the disks fail. Which is interpreted as memory corruption in the dumps. So is it Page files? Cache?

Take another disc check ..... using Seatools For DOS: SeaTools for DOS and Windows - How to Use

Also, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip   Tip

Let us know the results, with the subsequent crash dumps, if any.
______________________________________________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff880033545b8, fffff88003353e10, fffff8800124730e}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050853
Arg2: fffff880033545b8
Arg3: fffff88003353e10
Arg4: fffff8800124730e

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


EXCEPTION_RECORD:  fffff880033545b8 -- (.exr 0xfffff880033545b8)
ExceptionAddress: fffff8800124730e (Ntfs!NtfsFsdRead+0x000000000000004e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000001
Attempt to write to address 0000000000000001

CONTEXT:  fffff88003353e10 -- (.cxr 0xfffff88003353e10)
rax=ffff0000021c09b5 rbx=fffffa8009d27c60 rcx=fffffa80079a6030
rdx=fffffa8009d278c0 rsi=fffffa8009eb32b0 rdi=0000000000000001
rip=fffff8800124730e rsp=fffff880033547f0 rbp=fffff88003354820
 r8=fffffa80075cb530  r9=0000000000000003 r10=fffffa8009eb32b0
r11=fffffa8009d278c0 r12=0000000000000000 r13=fffffa8007707de0
r14=fffffa8009d278c0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Ntfs!NtfsFsdRead+0x4e:
fffff880`0124730e 48ab            stos    qword ptr [rdi] ds:002b:00000000`00000001=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000001

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d03100
 0000000000000001 

FOLLOWUP_IP: 
Ntfs!NtfsFsdRead+4e
fffff880`0124730e 48ab            stos    qword ptr [rdi]

FAULTING_IP: 
Ntfs!NtfsFsdRead+4e
fffff880`0124730e 48ab            stos    qword ptr [rdi]

BUGCHECK_STR:  0x34

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LAST_CONTROL_TRANSFER:  from fffff88001131bcf to fffff8800124730e

STACK_TEXT:  
fffff880`033547f0 fffff880`01131bcf : fffffa80`09d27c60 fffffa80`09d278c0 fffffa80`09eb32b0 00000000`00000001 : Ntfs!NtfsFsdRead+0x4e
fffff880`033548a0 fffff880`011306df : fffffa80`07707de0 fffffa80`09d9b800 fffffa80`07707d00 fffffa80`09d278c0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03354930 fffff800`02af2e15 : fffffa80`09d278e0 fffffa80`09e72930 fffffa80`09a969c0 fffff880`009b2180 : fltmgr!FltpDispatch+0xcf
fffff880`03354990 fffff800`02d69737 : fffffa80`09d9b800 fffffa80`09d9b800 fffffa80`09e72932 fffff800`02d3313f : nt!IoPageRead+0x255
fffff880`03354a20 fffff800`02d69831 : fffffa80`0967aca0 fffffa80`067a7b50 fffff880`03354b40 00000000`00000005 : nt!MiPfExecuteReadList+0xff
fffff880`03354a80 fffff800`02a78cd3 : fffffa80`0967aca0 00000000`00000000 00000000`00000000 fffff800`02c71280 : nt!MmPrefetchForCacheManager+0xb5
fffff880`03354ad0 fffff800`02b10b4e : fffffa80`09e72930 00000000`00000000 00000000`00000000 00000000`000007ff : nt!CcPerformReadAhead+0x2f3
fffff880`03354c00 fffff800`02ad5261 : fffffa80`067b5500 fffff800`02dc2101 fffff800`02cd2930 00000000`00000002 : nt!CcWorkerThread+0x21e
fffff880`03354cb0 fffff800`02d682ea : 00000000`00000000 fffffa80`067a7b50 00000000`00000080 fffffa80`0671f040 : nt!ExpWorkerThread+0x111
fffff880`03354d40 fffff800`02abc8e6 : fffff880`03186180 fffffa80`067a7b50 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03354d80 00000000`00000000 : fffff880`03355000 fffff880`0334f000 fffff880`033549e0 00000000`00000000 : nt!KiStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs
2 errors : !Ntfs (fffff8800124701f-fffff8800124730f)
fffff88001247010  01  00  eb  04  8b  5c  24  5c  ba  e9  00  00  c0  8b  cb *ef .....\$\........
...
fffff88001247300  45  33  e4  4c  89  65  08  45  8b  fc  44  89  65  10  48 *ab E3.L.e.E..D.e.H.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff88003353e10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
My System SpecsSystem Spec
31 Dec 2013   #16
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

Tried to manually set a restore point, and the system crashed into BSOD.

On Tue 12/31/2013 9:54:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-45131-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880094A5578, 0xFFFFF880094A4DD0, 0xFFFFF8800128D649)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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.

Gonna try the DV now
My System SpecsSystem Spec
31 Dec 2013   #17
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

Alright, I am in Safe Mode with Networking and the DV crash is below.

On Tue 12/31/2013 10:08:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123113-23368-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x9A879)
Bugcheck code: 0xC4 (0xF6, 0xAC, 0xFFFFFA800A35FB30, 0xFFFFF8800F14D879)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.82
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.82
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_VERIFIER_DETECTED_VIOLATION

There was a Beta update for the Nvidia card, which I went ahead and installed. (via Nvidia Experience)

My System SpecsSystem Spec
01 Jan 2014   #18
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The driver verifier caught the display driver.

Install the NVIDIA DRIVERS 314.22WHQL.
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

But that is not the main stream of the issue. The issue is storage related, it is seen again.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880094a5578, fffff880094a4dd0, fffff8800128d649}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+429 )

Followup: MachineOwner
---------
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes:
Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
  • You have enough physical memory.
  • The antivirus is MSE which never cause a trouble.
  • Not seeing any BackUp/Defrag program installed. Am I missing? Is there any, please uninstall.
  • Disable indexing. http://www.vistax64.com/tutorials/69...e-disable.html
  • And, continue with Driver Verifier for a few more hours.
Let us see the situation.
My System SpecsSystem Spec
01 Jan 2014   #19
SekitaLuna

Windows 7 Home Premium 64bit SP1
 
 

There is no defrag program installed on this comp other than the default program.

Uninstalled Nvidia drivers as listed and ran DDU in safe mode. After reboot, installed 314.22 graphics driver and PhysX, unchecking everything else and checking clean install. Rebooted again and once the windows loaded and the desktop came up the system went into another BSOD.

On Wed 1/1/2014 5:39:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010114-45240-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41287, 0x1, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I have disabled indexing. Starting Driver verifier again.

UPDATE: Windows booted fine with Driver Verifier going this time.
My System SpecsSystem Spec
01 Jan 2014   #20
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The last BSOD that you reported means an illegal page fault occurred while holding working set synchronization.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 1, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )

Followup: MachineOwner
---------
It may be caused by either a failing device driver or a failing RAM. You said you performed memtest twice; so RAM is not failing. It is a device driver.

We have driver verifier running to catch the driver that is causing this issue. In the mean time, let me have a look at the device drivers?

Upload the list of all the third party drivers Using NirSoft DriverView :
  • Download and execute Driverview
  • View > Hide Microsoft Drivers
  • Edit > Select all
  • File > Save Selected Items
  • In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
  • Zip the .txt file and upload it.
I wonder why some of the earlier dumps indicated to storage section, but not this time; but it is good.
My System SpecsSystem Spec
Reply

 BSOD 0x3B and 0x1E




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Intermittent BSOD; 0x1e, 0x7e, 0x3b
Having to type quickly as crashes are random, so apologies for mistakes. Removed programs commonly related to causing problems, updates graphics driver on APU, cant update wireless drivers as its discontinued (possible culprit?). Crashes are very random, can be days between or a loop of 5...
BSOD Help and Support
BSOD whenever playing games, 0x1E or 0x3B
Hi everyone, So sorry to be just dropping in--I've been lurking since my first laptop (now on third) and I've been able to fix BSODs just reading. But this one's really a pain. I get BSODs whenever I game--this happens whatever game I play, sometimes a few minutes after I start, sometimes a...
BSOD Help and Support
BSOD 0x3B / 0x1E @ ntoskml.exe during gaming
Over the last few days I've been having constant crashes. It's not always a bluescreen, sometimes just an instant restart, others a total lockup with audio still coming out. (Just a loud continuous noise of what it was playing before crash) Sometimes it actually blue screened so I did get mini...
BSOD Help and Support
BSOD at random intervals, primarily 0x1e, 0x3b and 0x7e
Windows 7 Enterprise 64-bit Retail GA-MA770T-UD3P Motherboard 2 2x2gb CM3X2G1333C9 Corsair DDR3 AMD Phenom II X4 B50 (4 cores at 3.1ghz stock speeds, 1.4v) NVIDIA Geforce GTX 260 768mb Fresh install of windows, roughly 1 month ago 2-3 years old hardware, 4 year old harddisks
BSOD Help and Support
New installation - Win 7 (64 bit) - BSOD 0xa, 0x3b, 0x1e, etc
System Specs: OS: Windows 7 Home Premium (64-bit) MOBO: Asus M4A89GTD-Pro/USB3 CPU: Athlon Phenom II x4 955 Black Edition VID: Nvidia 9500 GT (Upgraded to ATI HD 5770) AUDIO: Realtek (Motherboard Default) PSU: OCZ Modular - 500 watts Related Errors: 0x0000003b
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 09:12.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App