Solved Getting random BSOD errors need help to know why

adamwentzell82 · Feb 4, 2012

I was only online checking my e-mail and Firefox would keep crashing and had to restart( about 5 times) then the amd display driver stopped responding and has recovered error popped up just 3 minutes before the BSOD error. I added the mini dump file.
More info:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF8800A4DC798
BCP3: FFFFF8800A4DBFF0
BCP4: FFFFF880012B2C04
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

adamwentzell82 · Feb 4, 2012

Ran sfc /scannow through CMD picture is uploaded here

usasma · Feb 4, 2012

Please provide this information in order for us to give a more detailed response: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.

Please uninstall all ATI stuff from Control Panel...Programs...Uninstall a program
Then, download and install a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC).

If the device (AODDriver or AODDriver4.01) remains a problem in perfmon /report, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Memory dump suggests hard drive issues. Please do the following:

1 - do one of these free hard drive diagnostics: HD Diagnostic

2 - Run CHKDSK /R /F

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
FWIW - I know that the /F is supposed to be redundant, but I prefer to have it run anyway.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:

[font=lucida console]
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys        Wed Apr 06 16:07:29 2011 (4D9CC801)
AtiPcie.sys         Mon Aug 24 04:25:26 2009 (4A924E76)
speedfan.sys        Fri Mar 18 12:08:46 2011 (4D83838E)
Rt64win7.sys        Fri Jun 10 02:33:15 2011 (4DF1BAAB)
GEARAspiWDM.sys     Mon May 18 08:17:04 2009 (4A1151C0)
a2ddax64.sys        Thu May 19 08:09:43 2011 (4DD50887)
nusb3hub.sys        Thu Apr 22 21:34:35 2010 (4BD0F92B)
AtihdW76.sys        Tue Oct 18 03:09:49 2011 (4E9D263D)
atikmpag.sys        Mon Dec 05 21:12:14 2011 (4EDD79FE)
amdiox64.sys        Thu Feb 18 10:17:53 2010 (4B7D5A21)
ASACPI.sys          Wed Jul 15 23:31:29 2009 (4A5E9F11)
atikmdag.sys        Mon Dec 05 21:52:23 2011 (4EDD8367)
nusb3xhc.sys        Thu Apr 22 21:34:36 2010 (4BD0F92C)
AODDriver2.sys      Wed Jun 15 04:38:35 2011 (4DF86F8B)
ntk_PowerDVD_64.sys Tue Aug 03 05:04:12 2010 (4C57DB8C)
RTKVHD64.sys        Tue Jul 06 06:05:16 2010 (4C32FFDC)
MpNWMon.sys         Wed Apr 06 16:07:23 2011 (4D9CC7FB)
000.fcl             Thu Nov 18 19:53:28 2010 (4CE5CA88)
NisDrvWFP.sys       Wed Apr 06 16:08:53 2011 (4D9CC855)
point64.sys         Wed May 18 04:07:20 2011 (4DD37E38)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-19546-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 11:39:21.132 2012 (UTC - 5:00)
System Uptime: 0 days 15:49:25.661
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+114 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFindPrefix+114
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0a4dc798 fffff880`0a4dbff0 fffff880`012b2c04
BiosVersion = 0307   
BiosReleaseDate = 12/15/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

adamwentzell82 · Feb 4, 2012

2 new Mini dumps from 2 new BSOD errors.

usasma · Feb 5, 2012

Have you done any of the things that I suggested?
If so, which were done before each of the BSOD's?

adamwentzell82 · Feb 5, 2012

Had to upload thins as a picture. Not sure what this means.

adamwentzell82 · Feb 5, 2012

I got the BSOD errors before I did anything of what was listed that needed to be done here

usasma · Feb 5, 2012

Wait to see if you get BSOD's after doing what I asked.

adamwentzell82 · Feb 5, 2012

AMD OverDrive is not installed and just updated the video card drivers through the ATI website. put the computer in standby after this was all done then about 2 hours later it BSOD when it was waking up. This was the newest Mini dump I uploaded. I just changed the Memory timing to 7-7-7-16 and the Dram voltage to 1.6 volts about 3 hours ago and so far no BSOD yet and I'm running a stress test with ASUS PC Diagnostics. So far no problems.
I have this memory installed:
OCZ Gold Edition OCZ3G1066LV2G DDR3 SDRAM DDR3 1066( High Performance Gaming memory) 8GB(2GB X 4)
not sure if this is causing the problems.
PS nothing is over clocked all setting are stock.
Hard drive was tested through Windows with Scan disk with no problems
Also tested the hard drive with Data Lifeguard Diagnostic for Windows and ran the long test with no errors.
Before I changed the timing setting I ran a windows memory Diagnostic and after a restart it said that this computer has memory problems and after I changed the setting and reran the test it showed no errors with the memory.
Also ran Memtest86 for 9 hours after the timing setting were changed and passed.

usasma · Feb 6, 2012

Please zip up and upload the memory dumps (they're in C:\Windows\Minidump)
Try running Prime95 - it stresses memory, so it'll be the test of choice if you're having issues with RAM. The Blend test is the one that stresses RAM the most. Here's a link and some instructions: Hardware Diags

adamwentzell82 · Feb 6, 2012

For some reason everytime I put the computer in hibernation over night when I wake it back up I get a BSOD error; Computer works fine once it's booted up with no problems.
Running Prime95 now
I just checked out the heatsink I have the Cooler Master hyper 101 and it's only designed for CPU's up to 95watts and the one I just upgraded to is 125watts. As Prime95 runs it's running at 59C to 60C

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002C8BB65
BCP3: FFFFF880031A1478
BCP4: FFFFF880031A0CD0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\020612-18392-01.dmp
C:\Users\Adam\AppData\Local\Temp\WER-32557-0.sysdata.xml

usasma · Feb 6, 2012

020612-18392-01.dmp isn't in the uploaded files
The only memory dump there is 020412-19546-01.dmp

adamwentzell82 · Feb 6, 2012

just uploaded it.

usasma · Feb 6, 2012

Let's hit this with both barrels....

The BSOD blames tcpipreg.sys - a Windows driver related to networking.
So, update all networking drivers - wired, wireless, and any other "internet aware" programs

Next is Emsisoft Anti-Malware it's Direct Disk Access Support Driver (a2ddax64.sys) could possibly be causing problems. Uninstall it, then install another free antivirus (for testing only).

Next is the AOD Driver - there are 2 separate instances of the driver on your system. I presume that one is in C:\Windows\System32\drivers - but I have no idea where the other one is. Please search the hard drive and let us know where it's found.

Code:

AODDriver2.sys      Wed [COLOR=Red]Jun 15[/COLOR] 04:38:35 2011 (4DF86F8B)
AODDriver2.sys      Tue [COLOR=Red]Sep 06[/COLOR] 03:11:44 2011 (4E65C7B0)

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:

[font=lucida console]
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys        Wed Apr 06 16:07:29 2011 (4D9CC801)
speedfan.sys        Fri Mar 18 12:08:46 2011 (4D83838E)
AtiPcie.sys         Mon Aug 24 04:25:26 2009 (4A924E76)
a2ddax64.sys        Thu May 19 08:09:43 2011 (4DD50887)
GEARAspiWDM.sys     Mon May 18 08:17:04 2009 (4A1151C0)
atikmpag.sys        Mon Dec 05 21:12:14 2011 (4EDD79FE)
Rt64win7.sys        Fri Jun 10 02:33:15 2011 (4DF1BAAB)
nusb3xhc.sys        Thu Apr 22 21:34:36 2010 (4BD0F92C)
nusb3hub.sys        Thu Apr 22 21:34:35 2010 (4BD0F92B)
AtihdW76.sys        Tue Oct 18 03:09:49 2011 (4E9D263D)
amdiox64.sys        Thu Feb 18 10:17:53 2010 (4B7D5A21)
ASACPI.sys          Wed Jul 15 23:31:29 2009 (4A5E9F11)
atikmdag.sys        Mon Dec 05 21:52:23 2011 (4EDD8367)
RTKVHD64.sys        Tue Jul 06 06:05:16 2010 (4C32FFDC)
point64.sys         Wed May 18 04:07:20 2011 (4DD37E38)
AODDriver2.sys      Wed Jun 15 04:38:35 2011 (4DF86F8B)
ntk_PowerDVD_64.sys Tue Aug 03 05:04:12 2010 (4C57DB8C)
000.fcl             Thu Nov 18 19:53:28 2010 (4CE5CA88)
MpNWMon.sys         Wed Apr 06 16:07:23 2011 (4D9CC7FB)
NisDrvWFP.sys       Wed Apr 06 16:08:53 2011 (4D9CC855)
AODDriver2.sys      Tue Sep 06 03:11:44 2011 (4E65C7B0)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020612-18392-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Feb  6 11:42:04.305 2012 (UTC - 5:00)
System Uptime: 0 days 22:13:02.834
Probably caused by : tcpipreg.sys ( tcpipreg!TcpipRegRegistryKeyChangeCallback+76 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_tcpipreg!TcpipRegRegistryKeyChangeCallback+76
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02c8bb65 fffff880`031a1478 fffff880`031a0cd0
BiosVersion = 0307   
BiosReleaseDate = 12/15/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

adamwentzell82 · Feb 9, 2012

[FONT=Segoe UI, Arial]Here's the Crash dump report in detail.

Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Mon 2/6/2012 4:42:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-18392-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mpfilter.sys[/FONT] (MpFilter+0x1BA3A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C8BB65, 0xFFFFF880031A1478, 0xFFFFF880031A0CD0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\mpfilter.sys
product: [FONT=Segoe UI, Arial]Microsoft Malware Protection[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft antimalware file system filter driver
Bug check description: This indicates that a system thread 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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 2/5/2012 4:02:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020512-13852-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74B65)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CDBB65, 0xFFFFF88009FA3E98, 0xFFFFF88009FA36F0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread 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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 2/4/2012 5:40:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020412-22027-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 2/4/2012 4:39:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020412-19546-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A4DC798, 0xFFFFF8800A4DBFF0, 0xFFFFF880012B2C04)
Error: [FONT=Segoe UI, Arial]NTFS_FILE_SYSTEM[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time.
[/FONT]

adamwentzell82 · Feb 10, 2012

Found the problem 1 stick of memory was bad.

usasma · Feb 10, 2012

Thanks for letting us know!

Solved Getting random BSOD errors need help to know why

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer