Windows 7: BSOD playing Battlefield 3, error 0x0000001E

tbarrett86 · 22 Jun 2012

Hi Guys,

For the past few months I have been getting very random BSOD/Crashes (the pc will just freeze and restart without getting a BSOD and then it leaves no Minidump file), and this mostly happens when playing Battlefield 3, but not always.

The latest BSOD I got was yesterday and the error code was

STOP: 0x0000001E (0xFFFFFFFC0000005,0xFFFFF80003AE887B2,0x0000000000000000,0xFFFFFFFFFFFFFFFF)

I ran memtest86 for around 2 hours with 2 passes and got no errors. I have downloaded Driver Checker and updated the few drivers that were not fully updated. This morning I started playing BF3 and my computer froze and restarted again, but with no BSOD. When I checked my Minidump folder, no file was created. No file has been created for the past month or so. It only randomly posts a minidump file to its folder. I don't know why.

At current I am starting to get 3-5 Crashes/BSOD per week.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Win 7 Home Premium x64
- an OEM or full retail version? Full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 12 months
- What is the age of OS installation (have you re-installed the OS?) 12 months

Please find attached the Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML file.

Many thanks in advance

tbarrett86 · 23 Jun 2012

In the meantime I have also run a Chkdsk from out of windows (at startup). I have been reading many posts in the forum with issues that sound similar to mine and a lot of them say to run Chkdsk, so I did

Don't really understand the results, but please find the event file attached.

tbarrett86 · 23 Jun 2012

Any help would be great??

Thanks

writhziden · 25 Jun 2012

Code:

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

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  541440 file records processed.                                          File verification completed.
  967 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              60 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  689292 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  541440 file SDs/SIDs processed.                                         Cleaning up 2095 unused index entries from index $SII of file 0x9.
Cleaning up 2095 unused index entries from index $SDH of file 0x9.
Cleaning up 2095 unused security descriptors.
CHKDSK is compacting the security descriptor stream
  73927 data files processed.                                            CHKDSK is verifying Usn Journal...
  35689336 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  541424 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  88046890 free clusters processed.                                         Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

 976657407 KB total disk space.
 623564320 KB in 464609 files.
    232068 KB in 73930 indexes.
         0 KB in bad sectors.
    673455 KB in use by the system.
     65536 KB occupied by the log file.
 352187564 KB available on disk.

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

Internal Info:
00 43 08 00 b0 37 08 00 0f a6 0e 00 00 00 00 00  .C...7..........
5b 05 00 00 3c 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.

You received the message that Windows has made corrections to the file system. I suggest running the disk check again with Automatically fix file system errors checked (you do not need both boxes checked this time).

Problem Devices:

Code:

AODDriver4.1	ROOT\LEGACY_AODDRIVER4.1\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Use the following sites to help with the AODDriver4.1 issue. Rage3D Discussion Area - View Single Post - The AODDriver4.1 service failed .... Cat 12.2 megaproblems

Device Manager : Hidden Devices may help supplement the steps in that link.

Problematic Software:

Code:

Start Menu\Programs\GIGABYTE	Public:Start Menu\Programs\GIGABYTE	Public
Start Menu\Programs\Gigabyte Technology Corp	Public:Start Menu\Programs\Gigabyte Technology Corp	Public
Start Menu\Programs\GIGABYTE\AutoGreen	Public:Start Menu\Programs\GIGABYTE\AutoGreen	Public
Start Menu\Programs\GIGABYTE\EasySaver	Public:Start Menu\Programs\GIGABYTE\EasySaver	Public
Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public
Start Menu\Programs\MSI Afterburner	Troy-PC\Troy:Start Menu\Programs\MSI Afterburner	Troy-PC\Troy

Recommend removing your Gigabyte utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability.
MSI Afterburner/RivaTuner is known to cause instability with systems. Please remove the software.

Your Brother Parallel class Driver is eight years old. I strongly suggest removing the device/software associated with it.

The problem is that your RAM is designed for newer AMD processors and you are using an older processor. It is not compatible:

System Building and Compatibility

AMD Memory for Systems

tbarrett86 · 25 Jun 2012

Thank you very much for your response

~~I will start to work through the issues and post results once I am done.~~

I have completed all the items in the list. I will also purchase some new ram in the near future. Ram that is actually compatible. Once I hopefully determine that was the result I will mark this case as solved.

Many thanks

writhziden · 26 Jun 2012

You're welcome. Look forward to finding out whether the RAM was the problem. Best of luck the problem is then solved!

tbarrett86 · 07 Jul 2012

Well you got it spot on. I changed back to my old RAM and i have run now for around a week, and no BSOD. It seems as the compatability of the RAM was the issue. I am glad you found that as I was almost starting to tear my hair out.

Thank you so much for your help

I will now mark this as solved.

writhziden · 07 Jul 2012

That is excellent news!! I am glad I was able to help you track it down. Thank you for posting back.

Very happy to see the thread solved!!!

Windows 7: BSOD playing Battlefield 3, error 0x0000001E

BSOD playing Battlefield 3, error 0x0000001E problems?