I've been getting BSOD for almost a year now because of these two errors. I have tried clean installs of windows, buying new ram, and a new keyboard (because according another website forum a while back the old Logitech wireless keyboard mouse combo driver was responsible, and for a while it did fix the problem).
I sent in my motherboard to Asus to see if there was a problem and they said there wasn't, have new ram and keyboard (which came in 4 days ago) and new mouse. Still same problem. I very much appreciate any help you could give, this issue has had me doing this for a while :banghead:
OS- Windows 7 Ultimate
x64
(This was original, bought it along with my setup august 2010)
Fresh install 5 days ago
Phenom II x4 965
HIS Radeon HD 5830
Asus M4A89GTD PRO USB3
Cooler Master GX 750W
Corsair 8GB Vengeance RAM
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
i also ran memtest and after a pass it said there were no issues. I had run this test before many times as well and they has all also come up as no error
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Memtest+ needs to be run for at least 6 full passes.
AODDriver2.sys Is AMD overdrive it's been known to cause issues on WIn 7 x64 systems > uninstall for now
These 4 from the Asus AI suite also are known trouble makers, I don't install them any longer.
ASACPI.sys Wed Jul 15 23:31:29 2009 (4A5E9F11)
AiCharger.sys Wed May 5 04:37:36 2010 (4BE12E50)
AsIO.sys Thu Apr 22 07:18:03 2010 (4BD0306B)
AsUpIO.sys Sun Jul 5 22:21:38 2009 (4A515FB2)
Check the Asus site for updates.
nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B)
nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C)
Since the 1 was usb related check the Asus site for updated USB3 drivers as well
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Debug session time: Tue Oct 2 09:24:03.471 2012 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\100212-37455-01.dmp]
System Uptime: 0 days 0:06:00.000
BugCheck 109, {a3a039d898c8253f, b3b7465eeb44f495, fffff800034609c0, 1}
Probably caused by : memory_corruption
Bugcheck code 00000109
Arguments a3a039d8`98c8253f, Reserved b3b7465e`eb44f495, Reserved fffff800`034609c0, Failure type dependent information 00000000`00000001, Type of corrupted region, can be generic data region odification of a function or .pdata processor IDT processor GDT ype 1 process list corruption ype 2 process list corruption ebug routine modification ritical MSR modification
BUGCHECK_STR: 0x109
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BiosVersion = 3029
BiosReleaseDate = 07/05/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Oct 1 10:24:23.179 2012 (UTC - 4:00)
Loading Dump File [C:\Users\Owner\Bsodapps\100112-29858-01.dmp]
System Uptime: 0 days 9:45:11.334
BugCheck 9F, {3, fffffa8009291440, fffff80000b9c518, fffffa800acae010}
Probably caused by : usbhub.sys
Bugcheck code 0000009F
Arguments 00000000`00000003, A device object has been blocking an Irp for too long a time fffffa80`09291440, Physical Device Object of the stack fffff800`00b9c518, Functional Device Object of the stack fffffa80`0acae010, The blocked IRP
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x9F_3_AiCharger_IMAGE_usbhub.sys
BiosVersion = 2301
BiosReleaseDate = 07/18/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
I've uninstalled the programs and found an update for the the renasas USB 3.0 controller but the AODDriver2.sys file is associated with AMD Fuel and I dont think I can uninstall it.
Will run memtest tonight. thanks again, ill write back in the morning with results
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
sorry about the late reply, i ran memtest last night and after 7 passes it came up error free. As I stated above, I've unistalled those programs except for AMD Fuel which seems to be tied to the Catalyst controller. I wasnt able to use the computer much yesterday after the changed but will be doing so today. Ill report back with the results. thanks again for your help
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Yea you might have to try uninstalling the video drivers and Catalyst package completely and installing the driver only, but for now lets see how the other updates go.
uTorrent is not helping us here - please remove it.
Saluto has caused BSODs in the past; not sure if they ever got their act together or not. Remove Saluto.
The 2 0x109 BSODs are kernel corruption. Hardware failure can be a cause, e.g., RAM failing, thus unable to properly hold kernel code or a rogue driver is attempting to patch the kernel.
If the latter, Driver Verifier can help flush out the offending driver.
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
JCGriff2,
I'll uninstall uTorrent and Soluto now too just incase but I use uTorrent to download unlicensed anime (legal), not for downloading movies and what not. Do you know of any good/reliable torrent clients?
Also I uninstalled ASUS Ai Charger a little while ago, is it still appearing?
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Aicharger goes back to the 1st dump - 0x9f; does not appear in the 2 more recent 0x109 dumps.
No torrents here, so I can offer no alternatives.
Remove uTorrent for the duration until BSODs solved. It is to say at the least a wild-card and its removal means one less item that is a possible contributing factor to the BSODs.
What you install after you leave us. . . I have no control over.
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Hey guys, happy to say that so far there hasnt been a BSOD, that said the hardest thing ive done so far is word overnight and watched an HD video. ill let you know how it goes with gaming
Re: BSOD due to ntoskrnl.exe (nt+0x7F1C0) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
I think the problem was with MagicDisc, because there hasnt been a crash since I uninstalled it. Ive since reinstalled the catalyst manager for the video card bc I needed some of the features within it but have stopped the AMD Fuel process from booting with the computer through msconfig.
Thank you both again for your quick responses and thorough help, this problem had been driving me crazy!
Hello guys same issue again :/ i had to restore an image of the comp bc there had been a virus that got on about 2 days ago when my parents used the comp, and afterwards i uninstalled the programs again. But then the comp started crashing about 2 hours ago.
magic disc, soluto, utorrent are uninstalled.
i had uninstalled amd's catalyst system and then reistalled the chipset drivers but then it crashed before and after the uninstallation of the video drivers
Im going to upload the minudumps, would you mind checking them out please?
i reinstalled the video card drivers bc since they were unistalled when the computer crashed i didnt think they would be a problem to reinstall, plus it limited some features, should i uninstall that?
an image i made myself of the computer after a fresh install and installing just the drivers and a few application, i made it last friday after this started happening thursday and i fresh installed (last week of september)
I would forget about the images an re-install Windows 7. If a fresh install BSODs with a 0x109, then unknown hardware failure is the likely cause.
Regards. . .
jcgriff2
`
Code:
[font=lucida console]
Debug session time: Sat Oct 6 20:38:10.184 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\100612-22354-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime: 0 days 0:27:38.308
BugCheck 109, {a3a039d899832780, b3b7465eebfff6d6, fffff80003460a70, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Bugcheck code 00000109
Arguments a3a039d8`99832780, Reserved b3b7465e`ebfff6d6, Reserved fffff800`03460a70, Failure type dependent information 00000000`00000001, Type of corrupted region, can be generic data region odification of a function or .pdata processor IDT processor GDT ype 1 process list corruption ype 2 process list corruption ebug routine modification ritical MSR modification
BUGCHECK_STR: 0x109
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BiosVersion = 3029
BiosReleaseDate = 07/05/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Forum
4.7M posts
957.9K members
Since 2002
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!