BSOD's with multiple error codes

J

jjup

Member
Joined
Jan 14, 2014
Posts
7
Hi everyone,

I've been hit by multiple BSOD's these past couple of days with varying error codes and have been struggling mightily to resolve them. I've spent quite a bit of time online searching for a solution and here is a list of things that I've done so far:
-updated my network and graphics drivers
-run a disk check on my HDD
-run memtest for 8 passes with no errors

after doing all the above I was free of BSOD's for about 4 days before I got hit by another one earlier today (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, error code: 7e).
If anybody has insight on the problem(s) at hand I would greatly appreciate any help I can get. In the mean time I will try updating my BIOs and running driver verifier.

Some info:
· OS - Windows 7x64
· What was original installed OS on system?: Windows 7 x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?: OEM
· Age of system (hardware) - 2009-ish
· Age of OS installation - have you re-installed the OS?: I reinstalled the OS around January 4th.

· CPU: AMD Phenom II X4 965
· Video Card: AMD Radeon HD 5800 series
· MotherBoard: ASUS M4A89GTD PRO
· Power Supply - brand & wattage (if laptop, skip this one): not sure atm.

· System Manufacturer: self-built
· Exact model number (if laptop, check label on bottom):

· Laptop or Desktop?: Desktop

View attachment Windows7_Vista_jcgriff2.zip

Thanks in advance!
 
Hi,

We have various different bug checks:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

This indicates that a system thread generated an exception which the error handler did not catch.

BugCheck 1000007E, {ffffffffc0000005, fffff80002f9409c, fffff880033166c8, fffff88003315f20}

The 1st parameter of the bug check is 0xc0000005 which indicates an access violation occurred, let's see what caused it:

Code: 
2: kd> .exr 0xfffff880033166c8
ExceptionAddress: fffff80002f9409c (nt![COLOR=#ff0000][I][B]MiLogPageAccess[/B][/I][/COLOR]+0x00000000000001fc)
   ExceptionCode: c0000005 (Access violation)

^^ Unsure of what this exact routine is, but it's certainly a memory related routine.

NTFS_FILE_SYSTEM (24)

This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

BugCheck 24, {1904fb, fffff8800317e718, fffff8800317df70, fffff8000318eae9}

If we run an .exr on the 2nd parameter of the bug check, we get the following:

Code: 
0: kd> .exr 0xfffff8800317e718
ExceptionAddress: fffff8000318eae9 (nt![COLOR=#ff0000][I][B]FsRtlTeardownPerStreamContexts[/B][/I][/COLOR]+0x0000000000000069)
   ExceptionCode: c0000005 (Access violation)

File systems call FsRtlTeardownPerStreamContexts to free all per-stream context structures associated with a given FSRTL_ADVANCED_FCB_HEADER structure. When a file system tears down the stream context object for a file stream, it must call FsRtlTeardownPerStreamContexts, which in turn calls the FreeCallback routines of all per-stream context structures associated with the file stream.

MEMORY_MANAGEMENT (1a)

This indicates that a severe memory management error occurred.

BugCheck 1A, {5003, fffff70001080000, 15537, 925d0003aa6e}

- The 1st parameter of the bug check is 5003 which indicates the working set free list is corrupt. Given the above bug checks + this *1A, this is probably a hardware error. More specifically, a RAM or HDD issue. Let's first rule out the possibility of driver(s) causing memory corruption.

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

1. AODDriver2.sys - Wed Sep 11 23:36:40 2013

^^ AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Very known to cause BSOD's, so please remove ASAP.

2. Various Asus PC Probe & software drivers are listed in your loaded modules list. I would go ahead and remove PC Probe and any other Asus bloatware that is installed. It's all unnecessary.

3. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes:

Avira removal - How do I uninstall my Avira product?

MSE - Microsoft Security Essentials - Microsoft Windows

4. 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.

Regards,

Patrick
 
Many thanks for taking the time to reply.

I followed your suggestions at the bottom and also did some tests to see if I had any HDD or RAM issues but nothing came up. After following your instructions, I didn't get a single BSOD for a week so I thought I was safe but yesterday and today I got hit by 3 BSOD's all with different error codes; dmp files are attached below.

View attachment dmp_files.zip

Also, for some reason windows performed a chkdsk even though I didn't schedule it and there seems to be errors (I can't really tell).

Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
The attribute name offset for attribute of type 0x30
and instance tag 0x4 is incorrect.
30 00 00 00 d8 00 00 00 00 00 01 00 00 00 04 00 0...............
ba 00 00 00 18 00 01 00 ef 04 01 00 00 00 07 00 ................
24 e2 44 5b 64 0a cf 01 2d a3 bd f8 7d a4 ce 01 $.D[d...-...}...
2b de b9 5a 64 0a cf 01 24 e2 44 5b 64 0a cf 01 +..Zd...$.D[d...
00 30 00 00 00 00 00 00 59 25 00 00 00 00 00 00 .0......Y%......
20 00 00 00 00 00 00 00 3c 01 70 00 61 00 63 00 .......<.p.a.c.
Deleting corrupt attribute record (48, "")
from file record segment 112830.
197888 file records processed. File verification completed.
679 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
There is no NTFS file name attribute in file 0x1b8be.
Correcting minor file name errors in file 112830.
Unable to locate the file name attribute of index entry PA89FA~1.CAT
of index $I30 with parent 0x104ef in file 0x1b8be.
Deleting index entry PA89FA~1.CAT in index $I30 of file 66799.
Unable to locate the file name attribute of index entry package_44_for_kb2852386~31bf3856ad364e35~amd64~~6.1.1.3.cat
of index $I30 with parent 0x104ef in file 0x1b8be.
Deleting index entry package_44_for_kb2852386~31bf3856ad364e35~amd64~~6.1.1.3.cat in index $I30 of file 66799.
265386 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
1 unindexed files scanned. Recovering orphaned file PA89FA~1.CAT (112830) into directory file 66799.
0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
197888 file SDs/SIDs processed. Cleaning up 15 unused index entries from index $SII of file 0x9.
Cleaning up 15 unused index entries from index $SDH of file 0x9.
Cleaning up 15 unused security descriptors.
Security descriptor verification completed.
33750 data files processed. CHKDSK is verifying Usn Journal...
35882264 USN bytes processed. Usn Journal verification completed.
Windows has made corrections to the file system.

976657407 KB total disk space.
55018348 KB in 163150 files.
119832 KB in 33751 indexes.
0 KB in bad sectors.
330303 KB in use by the system.
65536 KB occupied by the log file.
921188924 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
230297231 allocation units available on disk.

Internal Info:
00 05 03 00 31 01 03 00 6d d4 05 00 00 00 00 00 ....1...m.......
b7 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
Click to expand...

Does the above mean that I have a harddrive problem? For the record, I have run the hdd diagnostics program from the WD website and it passed the extended test. I don't really know what to do from here but I guess I'll try memtest again tonight or tomorrow night. Any suggestions and help is appreciated.
 
There are no errors in the chkdsk, no. Even though you have a WD drive, you should still be able to 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
 
I ran all the tests on Seatools (except the ones you mentioned) and they all passed. Does this mean it is not a HDD problem and more likely a RAM issue? I ran driver verifier for about 20~ hours yesterday so it is likely not a driver issue... but I also ran memtest for 8 passes a week ago and everything was fine as well. Do you happen to know of any more tests I can do on my RAM?
 
If you're not getting errors in Chkdsk, Seatools, or WD Diagnostics, your HDD is likely healthy. If you're not getting errors after ~8 passes of Memtest, your RAM is likely healthy. Leave verifier enabled and when the system crashes next, upload the crash dump from it.

Regards,

Patrick
 
It is verifier enabled, yes, however there is no driver detected within violation.

SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

-- DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

Call stack:

Code: 
2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0277cac8 fffff800`02e8e169 : 00000000`0000003b 00000000`c0000005 fffff880`0165a8b8 fffff880`0277d390 : nt!KeBugCheckEx
fffff880`0277cad0 fffff800`02e8dabc : fffff880`0277cd10 fffff800`02e65c5d fffff800`02fe95a8 fffff880`0277e080 : nt!KiBugCheckDispatch+0x69
fffff880`0277cc10 fffff800`02eb975d : fffff800`030aeb40 00000000`00000000 fffff800`02e19000 fffff880`0277db38 : nt!KiSystemServiceHandler+0x7c
fffff880`0277cc50 fffff800`02eb8535 : fffff800`02fde6c4 fffff880`0277ccc8 fffff880`0277db38 fffff800`02e19000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0277cc80 fffff800`02ec94c1 : fffff880`0277db38 fffff880`0277d390 fffff880`00000000 fffff880`0277de08 : nt!RtlDispatchException+0x415
fffff880`0277d360 fffff800`02e8e242 : fffff880`0277db38 fffffa80`05281f80 fffff880`0277dbe0 fffff8a0`018dc468 : nt!KiDispatchException+0x135
fffff880`0277da00 fffff800`02e8cb4a : fffffa80`06ea5060 00000000`00000001 00000000`00000000 fffff880`0277dc80 : nt!KiExceptionDispatch+0xc2
fffff880`0277dbe0 fffff880`0165a8b8 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff8a0`0029ff60 : nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff880`0277dbe0)
fffff880`0277dd70 fffff880`0165ad6c : fffff8a0`018dc460 00000000`00000000 00000000`00000420 00000000`00000001 : tcpip!WfpAllocateFromPerProcessorLookasideList+0x28
fffff880`0277dda0 fffff880`0165ac73 : 00000000`00000000 fffff880`0277eca0 00000000`00000420 00000000`00000000 : tcpip!WfpAleCaptureImageFileName+0x7c
fffff880`0277ddf0 fffff880`0167f2fe : fffff8a0`0029ff60 fffff800`0317b1b8 00000000`00000010 00000000`00000000 : tcpip!WfpCreateProcessNotifyRoutine+0x63
fffff880`0277ded0 fffff800`0317b23a : fffff8a0`00008040 fffff880`0277eca0 fffff8a0`0028fe10 fffffa80`063f91b0 : tcpip!CreateProcessNotifyRoutineEx+0xe
fffff880`0277df00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspInsertThread+0x67a

Various network routine calls, which lead me to check your modules list to see that you still haven't followed many of my recommendations such as removing avast!, etc. Follow this, please:

1. AODDriver2.sys - Wed Sep 11 23:36:40 2013

^^ AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Very known to cause BSOD's, so please remove ASAP.

2. Various Asus PC Probe & software drivers are listed in your loaded modules list. I would go ahead and remove PC Probe and any other Asus bloatware that is installed. It's all unnecessary.

3. Remove and replace Avira with Microsoft Security Essentials for temporary troubleshooting purposes:

Avira removal - How do I uninstall my Avira product?

MSE - Microsoft Security Essentials - Microsoft Windows

4. 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.
Click to expand...

Regards,

Patrick
 
I removed all of the ASUS software stuff that I could find from the programs and features menu but are the drivers still showing up? I will do a run down of my drivers list to make sure they are gone. Also, I thought I had removed AMD OverDrive but it seems that the AODDriver2.sys file was still present in my harddrive in a folder called "\ATI Technologies\ATI.ACE\Fuel\amd64" for some reason. I went ahead and deleted the file entirely so that should be the end of it. Completely forgot about uninstalling avira and I will get to that. I will let you know if I get any more BSOD's after these fixes.
 
Hello again!

The latest attached DMP file is of the *3B bug check as we've seen above, however it's verifier enabled --
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
Click to expand...
and failing to detect a driver in violation.

If we take a look at the call stack:

Code: 
STACK_TEXT:  
fffff880`0260a9a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : [B][I][COLOR=#ff0000]dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x171[/COLOR][/I][/B]

As I've mentioned in a previous thread regarding this:

dxgmss1.sys is the DirectX MMS, a component of DirectX. VIDMM_GLOBAL::BeginCPUAccess - ??? Very hard to tell what's going on as I cannot find proper documentation, and it's a very uninformative stack. If maybe after the 'BeginCPUAccess' call we had an 'xWaitOnDMAReferences', then I could say we may have a DMA allocation problem, but we have a blank stack so there's very little information to get.
Click to expand...

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

Given all of the diagnostics we've run (including Memtest), and enabled Driver Verifier and still see a dxgmms1.sys fault, we're likely dealing with a faulty video card. Do you have access to integrated graphics to test or possibly a secondary video card?

Regards,

Patrick
 
Yes, I do believe that my board has onboard graphics and I will try switching to it tomorrow. In the meantime, do you think updating the BIOS and chipset drivers would be helpful at all to my problem? I'm asking because I've heard that its best not to update the BIOS unless absolutely necessary. My BIOS version and chipset drivers are outdated but could they possibly be the cause of the BSOD's?
 
Although they may not have any positive effect, it's definitely worth a try. It's always important having the latest Chipset drivers, and latest BIOS can be important as well depending on what's included in the latest version.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top