Sign in with
Sign up | Sign in
Your question

Help me guys! BSODS, all random!

Last response: in Motherboards
Share
July 19, 2010 6:00:44 PM

Hello!! I am getting RANDOM BSODS ALL THE TIME, please help me out here

System Specs are:
Mushkin DDR3 Stiletto 1600 MHZ CL9 ram
M4A785TD-V EVO
Phenom II x4 955 C3
F1 Samsung 750GB
Sapphire 5870 1GB
650W Corsair TX
X-FI Titanium sound card

I am almost forced to run with only one stick of Ram, 2GB all the time, it does not matter which slot it sits in, neither does it matter what stick of ram it is.
Both ram sticks have passed Memtest 5 times but PC crashes instantly when running in dual channel
It does not matter if i play games or just sit on facebook, the crashes are 100% random, it crashes inside BIOS screen, at startup, on the login screen.
Heat is NOT an issue - temps are even below normal, good cooling.

I took out my 5870 and it seemed to run stable with the integrated GPU, for like 4 hours, then it just restarted randomly and the BSODS started popping up again.
It's very weird, and the BSODS are also very random... The most common named in the bsods are NTKRNLPA.exe...

I used BlueScreenView to get the information below, these are all different BSODS at different times..

HELP ME!!! I am almost positive its my motherboard.


I have reinstalled Windows 7 64bit and Windows 7 32bit at least 6 times now! (backed up data, formatted, installed windows 7, installed the correct drivers, installed Avast Comodo Firewall, and then data back over)

If theres anything i forgot please ask, i just want to get rid of these crashes as its very frustrating..

BSOD info is below>
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


071910-15990-01.dmp 19-07-2010 17:45:19 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 0xfffffd80 0x00000000 0x82eafdfa 0x00000000 ntkrnlpa.exe ntkrnlpa.exe 85903 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) 32-bit C:\Windows\Minidump\071910-15990-01.dmp 4 15 7600


071910-17409-01.dmp 19-07-2010 14:57:08 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x009200bc 0x00000002 0x00000001 0x82e84028 ntkrnlpa.exe ntkrnlpa.exe 4682b NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) 32-bit C:\Windows\Minidump\071910-17409-01.dmp 4 15 7600


071910-19219-01.dmp 19-07-2010 14:13:23 BUGCODE_USB_DRIVER 0x000000fe 0x00000006 0x84fd56b0 0x43787254 0x00000000 USBPORT.SYS USBPORT.SYS 1025 USB 1.1 & 2.0 Port Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\071910-19219-01.dmp 4 15 7600


071810-19359-01.dmp 18-07-2010 10:43:48 MEMORY_MANAGEMENT 0x0000001a 0x00000403 0xc0013690 0x2ef70867 0xc0013680 ntkrnlpa.exe ntkrnlpa.exe a7590 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) 32-bit C:\Windows\Minidump\071810-19359-01.dmp 4 15 7600


071510-24180-01.dmp 15-07-2010 22:48:37 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e 0xc0000005 0x82df7d62 0x8db8b9dc 0x8db8b5c0 halmacpi.dll halmacpi.dll 87a7 Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\071510-24180-01.dmp 4 15 7600


062110-16738-01.dmp 21-06-2010 14:56:00 NTFS_FILE_SYSTEM 0x00000024 0x001904fb 0x82136620 0x82136200 0x82c8eb33 Ntfs.sys Ntfs.sys 14221 NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\062110-16738-01.dmp 4 15 7600


062110-33290-01.dmp 21-06-2010 00:04:24 BAD_POOL_HEADER 0x00000019 0x00000003 0x9852b690 0x9852b680 0x9852b680 halmacpi.dll halmacpi.dll 5b48 Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\062110-33290-01.dmp 4 15 7600


062010-17300-01.dmp 20-06-2010 18:21:24 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 0xf029f2d8 0x00000001 0x917d0ebd 0x00000002 ntkrnlpa.exe ntkrnlpa.exe 85903 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) 32-bit C:\Windows\Minidump\062010-17300-01.dmp 4 15 7600


061910-19765-01.dmp 19-06-2010 12:26:42 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 0xfffe7960 0x00000000 0x82caee6e 0x00000000 halmacpi.dll halmacpi.dll 5b48 Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\061910-19765-01.dmp 4 15 7600


123101-17908-01.dmp 31-12-2001 23:01:25 MEMORY_MANAGEMENT 0x0000001a 0x00005003 0xc0802000 0x000029af 0x029ad34e ntkrnlpa.exe ntkrnlpa.exe dcd10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) 32-bit C:\Windows\Minidump\123101-17908-01.dmp 4 15 7600


123101-15428-01.dmp 31-12-2001 22:03:40 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0x00000008 0x807c9750 0x00000000 0x00000000 Unknown_Module_926a5805 Unknown_Module_926a5805 f0e4ceb 32-bit C:\Windows\Minidump\123101-15428-01.dmp 4 15 7600


123101-15132-01.dmp 31-12-2001 21:05:29 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x00000037 0x00000002 0x00000000 0x82e8ca5b ntkrnlpa.exe ntkrnlpa.exe 4682b NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) 32-bit C:\Windows\Minidump\123101-15132-01.dmp 4 15 7600


--------------------------------------------------
And also this weird BSOD with no bug check string!


071510-21262-01.dmp 15-07-2010 22:36:41 0x0000010e 0x0000001f 0xd9250570 0x00000000 0x00d08a75 watchdog.sys watchdog.sys 51f0 Watchdog Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\071510-21262-01.dmp 4 15 7600


Thank you alot!

More about : guys bsods random

a b V Motherboard
July 19, 2010 6:27:32 PM

It is your mother board. Replace it and the problems will be solved.
And just a hint, after you get a good board, if it's an asus board, install the memory in the two slots closest to the CPU.
July 19, 2010 8:02:42 PM

I still have warranty, but i need to prove to them that it is indeed the motherboard, somehow, cos i do not want to pull apart my PC and then send in the motherboard and have them test it for 2+ weeks just like i have been testing it, and all in the meantime i cant do *** with my own PC :( 
Related resources
a b V Motherboard
July 19, 2010 10:30:16 PM

It's better to get a board now, while they will still exchange it. I think, IMHO, that I (according to my own experience and personal preference) would ask the vendor to exchange it for a gigabyte board.
They don't test it, as far as I know they just exchange it. You don't need to prove it to them, just tell them it's bad.

You can try, install the memory in the two slots closest to the CPU, fresh install the OS, run it. Within the first 2-5 boots it usually fails. But it starts out looking like it's working at first, and you think it will keep working, then it fails.

You can try, open the bios setup, push delete during POST. Then turn off the cool and quiet, leave it off. Save changes and exit. This has helped some users, but a lot of times it won't run anyway.

You can try, update to the latest bios, but the bios updater that comes with it does not work a lot of times, it might leave the system dead.

You can try, download CPUID. Check the system voltages, the 3.3 volt supply usually reads a really low voltage when the board is bad.

I am sorry but I really do think your problems would be over with a good board.
July 19, 2010 10:48:09 PM

Oh, and yeah i already flashed it to the newest BIOS, twice.

I am pretty sure i'm taking the MSI GD-70 because its just pure awesome, but it costs more than the one im using now.

I don't think you understand what i mean, its like.. uhm.

I need something that will make them go "Oh, well thats true. We'll send you a motherboard now, and when you have your system up and running you can send back the defect board"... I can't just send in my motherboard now without a replacement, there'd be at least 1 or 2 weeks time before they refund/send me a new board.

Also... This is the last time i buy Asus motherboards.. Had a P5QL-E long time ago, it suuucked, so many problems and incompatible ram etc etc etc..

Got myself a DFI P45 T2RS Blood Iron (damn awesome board, overclocked E8400 to 4.4GHz 24/7) worked for 1 year and sold, still no problems :p 

But, yeah, i guess i'll call them and have a talk.

Thank you for confirming :) 
July 19, 2010 10:58:45 PM

Oh, and according to Everest, CPUID and SpeedFan my 3.3V is around 3.3-3.6 volt constantly.

You said:
"You can try, install the memory in the two slots closest to the CPU, fresh install the OS, run it. Within the first 2-5 boots it usually fails. But it starts out looking like it's working at first, and you think it will keep working, then it fails. "
That is almost what i have to do to get it up and running, i have to move the single stick of ram around from all the 4 slots, have to try at least 30 different positions, then it will randomly start up perfectly and work for 8 hours, and it crashes overnight when doing nothing. The next day it wont boot up, and i didnt change anything!

Soo annoying! :p 
a b V Motherboard
July 20, 2010 12:07:33 AM

Ya, you have a bad board alright, all the classic symptoms.
Call the vendor and ask to exchange for another manufacturer's board, at least try.
a b V Motherboard
July 20, 2010 12:23:56 AM

Before you condemn/change the motherboard try substituting a known good power supply, this is far more likely to be the cause of your problem.
a b V Motherboard
July 20, 2010 12:35:24 AM

download memtest86 and test the ram for atleast 24 hours, odds are it will fail right away, when it does you can see you dont need a new motherboard and get som ram on the QVL, and make sure it is running at the manufacturers speed and voltage.

I can pretty much guarantee it is a ram issue.
a b Ĉ ASUS
a c 112 V Motherboard
July 20, 2010 3:37:50 AM

^+1 that's definitely what i would do first before assuming it's the mobo.
a b Ĉ ASUS
a b V Motherboard
July 20, 2010 4:27:49 AM

although doesnt the CPU have onboard memory controller? could be that?
July 20, 2010 8:19:05 AM

If you analyse the crash data you'll see that it has got something to do with resource assignment to you USB.

Windows automaticaly assigns IRQ resources to devices attached to your PC, these resources are set aside by your system.

So whatever USB device you have attached to your PC is conflicting with your IRQ resource pool. Try and remove the device (unplug the USB device from your PC) and, if any, uninstall the device drivers. Can be a printer, memory stick, whatever.

If that doesn't work then go into your BIOS and look for IRQ assignment. There should be a option to set it to auto and look for "plug and play OS installed" and enable that. You might want to enable USB legacy support if you have a USB keyboard and/or mouse.

If that doesn't work then perform a clean format with the settings set as above and things should be fine after the install.

If that doesn't work then punch the supplier's sales person full in the face and demand a replacement. A broken nose should be good enough reason for them to give you a refund.
July 20, 2010 9:00:29 AM

Ok, listen... What i have told you guys so far was less than half, i just kinda forgot.
I was running this PC 5 months ago with an X3 425 overclocked to 3.9 GHz, it ran smooth.. I realized i didnt want that much overclock, so i put it down to 3.4.
(Followed guides on the internet, other people getting it to 4.1 GHz aswell)
But it was only after i installed my 5870 and removed the overclock totally that the problems began appearing(2-3 weeks).

That was why i sold my X3 425 and got myself a Phenom II x4 955(Didn't touch bios settings, all at default). Problems were solved for like 5 weeks, i thought they were gone permanently... but no, i then called my friend and told him to bring his DDR3 1333 Kingston CL7 ram, and yup the same things ocurred, nothing different.

It is not my ram, it is not my GPU, it could be my Power Supply(but ffs its Corsair, nothing can go wrong!) and i doubt my harddrive could do this.
I ran Driver Verifier and it crashed like 6 times saying CTAUD2K.sys which are the drivers for my sound card.. So i tried removing the card and the drivers entirely, using the onboard sound(driver sweeper aswell)... But still no luck, crashing like it used to but Driver Verifier didnt crash at least...

I have my Razer Imperator and my G15 v2 connected, nothing else, tried ALLLLL the different USB ports on the front and back, still the same(I thought of this when i got my first USB bugcode thingie)

So i guess that leaves PSU or motherboard?
All the voltages are within 3% of what their supposed to be :/  according to software.. but who knows?

It is a damn awesome PC, when it actually works.
July 20, 2010 11:49:50 AM

have you tried a format and clean install?
July 20, 2010 2:27:55 PM

MrMinnaar said:
have you tried a format and clean install?



Read my first post and you will see i have done almost EVERYTHING, all the things people are asking me to do i have already done, and i've done it several times! :p 
more than 6 re-installs with different DVD's with 64bit and 32bit windows 7. (100% clean installs)

not much more i can test i think :( 
July 20, 2010 4:55:30 PM

Oh i just got a new bsod while playing WoW :p 


072010-15319-01.dmp 20-07-2010 18:27:38 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x00000004 0x00000002 0x00000001 0x892dbefe NETIO.SYS NETIO.SYS+7efe Network I/O Subsystem Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\Minidump\072010-15319-01.dmp 4 15 7600
July 21, 2010 6:49:58 AM

There's definately resource conflict going on there. If all else fails then maybe you should get a new motherboard. In the end, trying to solve the problem might end up costing you more than just getting a new mobo
July 21, 2010 9:16:03 AM

Well i'm gonna buy a MSI GD-70 and test it, if it works, i'm sending in the old motherboard and let them test it.. see what they say :) 

You would also take a MSI GD-70 right?
July 21, 2010 1:06:48 PM

My personal experience with MSI mobos have all been ***. The BIOS sucks big time and the performance isn't worth the price. If you're gonna have it around only for testing then it should be ok

If you plan to have a mobo that you plan on using your pc for day to day tasks, gaming and such then I highly recommend a asus M4A89GTDPRO
July 26, 2010 8:18:00 PM

I got the MSI 790FX GD70. The bios is superb, nice menu lots of options, much better than the crappy M4A785TD-V EVO at least...

And yup, everything is working flawless!

Thanks alot guys!
January 8, 2011 9:51:05 PM

KERNEL_DATA_INPAGE_ERROR
bug check code 0x0000007a means three things possible-
memory, hard disk or cabling, or some driver error.
a c 207 Ĉ ASUS
a c 715 V Motherboard
January 8, 2011 10:53:10 PM

In the BIOS did you try Ganged and Unganged? If not try it. I assume you tried Clear CMOS via the Jumper method?

Q - Did you use the appropriate {per OS} 64-bit ATI drivers?

Q - After you installed Windows {by itself} were you getting BSOD galore?

Q - Have you tried disconnecting everything {USB} and try a different keyboard/mouse?

Q - Did you build this rig?

Q - Did you get any Windows Compatibility warnings?

Q - In the Device Manager are there any {? or !} or unknown Drivers?

Next, MSCONFIG -> Diagnostic is the BSOD are gone then it's a conflict.


Normally:
First I would F8 {safe mode} and run check disk - http://support.microsoft.com/kb/315265 and run both options {Fix System Errors & Scan/Recover bad sectors}. Next 'try' MSCONFIG -> Diagnostic. If you're still getting errors then Windows Repair -> http://windows.microsoft.com/en-US/windows7/products/fe...

A lot of those are HDD related, if it were 'me' I would copy my important data, FULL reformat then reinstall windows from scratch.
January 9, 2011 12:57:28 AM

Cool story bro, if you bothered reading the comments below.. I guess you would've seen that it's working :p 

But thanks anyways.
a c 207 Ĉ ASUS
a c 715 V Motherboard
January 9, 2011 12:27:30 PM

I missed it, and just NOW noticed the huge gap in time. I saw the prior post and assumed a problem still persisted. If Windows wasn't the cause the next step probably would be a new MOBO recommendation.

Good Luck! I hope the artifacts are gone...
!