Constant BSOD's! Replaced MB, Wireless NIC and GPU and Tested Memory!!! What Next?

Toggle sidebar Toggle sidebar
M

Mattdad1

Commendable
Jun 4, 2016
4
0
1,510
Longtime lurker, first time poster-newb. So please take it easy on me! BTW, I'm aware that I know just enough to be dangerous.
I built a W7 64bit system 4 years ago. Biostar TA970XE, Athlon II 2.3 ghz, 2X4 GB Corsair DDR3) I started getting BSOD's on W7, and also had some issues with Video (Radeon HD5570 1GB)and Wireless cards.
I scrubbed all traces of drivers, using some tool recommended here and no luck, Constant BSOD's. Then I ran the the extended tests in Windows Memory Diagnostics and no errors. No luck. Must be the wireless card! Cheap, so I bought one. Startech wirelessN model. Scrubbed drivers and installed. No luck, Constant BSOD's. Must be the Graphics card! Bought a 1GB GE Force 8400 GS, scrubbed drivers and installed. No luck, Constant BSOD's. No files of value, so I did a clean install from the original MS W7 disk. No luck, Constant BSOD's. Must be the MB! New ASRock 970 Pro 3 R2.0. (since I can use my existing PSU, CPU, Videocard(s), Wireless card(s), DDR3, right? Another clean install. No luck, Constant BSOD's.
BSOD's are all over the place. Since my newest install this AM, I've gotten these BSOD's- some of them a couple times: KMODE_EXCEPTION, CID_HANDLE_EXCEPTION, NTFS_FILE_SYSTEM, SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, BAD_POOL_CALLER, PAGE_FAULT_IN_NONPAGED_AREA.
I have BlueScreenView, but don't know where to post results, though I'm pretty sure it's not here.
There have been many, MANY more gyrations than these, but I think this is the important information. All I know at this point is that I've wasted a bunch of time and money. Would any of you kind people be able to assist me?
Many many, thanks, Matt

ADDED INFORMATION: Thanks! So just copy the .dmp files and post them to a public drive, or convert them to text and post them?
Also, I should have included that upon the latest clean install device manager showed Ethernet, Network and USB controller drivers were not installed.
"Mark Drivers Found in Crash Stack" in BlueSCreenView shows all 17 dumps list "ntoskrnl.exe", 5 list "Ntfs.sys", 2 list "fltmgr.sys", and 1 lists "ndis.sys"

Hope I posted dump files correctly:
https://drive.google.com/file/d/0B12NdaQj1Jy1NTJpMkU1eURkZ2M/view?usp=sharing
 
Solution
J
- the windows memory test is pretty basic, a more advanced test is memtest86
- you can get memory tests to pass it the defect happens to be in the same location where the test is loaded into memory.
-you can get memory sticks to pass while in one slot but not when placed in a different slot, just because of the slight timing changes.
- I have seen memory sticks all work individually but fail when all the memory slots were populated. I had a ASUS motherboard that actually indicated in the manual that you had to run your memory at a slower speed if you use all of the slots. Took me a while to figure that out, I used the vendor qualified memory at the correct speeds and setting but got memory failures. Then I found the little * in...
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
you would need to put your files on a cloud server like microsoft onedrive, google docs or mediafire, then share the files for public access and post a link here.

the files needed would be the minidump files located in c:\windows\minidump directory
the txt files from bluescreenview.exe or whocrashed.exe might be of help (maybe 20% of the time)
if they list a 3rd party driver as the cause of the failure. often the will just list the windows kernel or name a virus scanner by mistake. after identifying the driver you look it up at :http://www.carrona.org/dvrref.php
to see who the owner is and where to get a update.



 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
looks like something called into partition manager with a bad memory address.
Partition Management Driver it could be a random memory error but given the nature of the access I would be running a virus or malware scan.
IE run malwarebytes.

you are also running a very old version of windows on a new machine. for example you have usb drivers from 2009 and 2010 but have a bios that has the various USB spec changes from 2012 and 2013 already incorporated into it.

remove AsrAppCharger.sys Tue May 10 01:28:46 2011
or update it, the old versions of these can cause memory corruptions.

you also need to apply all the custom driver fixes for your motherboard to get windows 7 to work correctly
http://www.asrock.com/mb/AMD/970%20Pro3%20R2.0/?cat=Download&os=Win764

most of the drivers have been updated from the default generic versions windows has installed.
(you have microsoft 2009 and 2010 versions)

windows does not install and maintain update for custom versions of drivers that are on your motherboards website.

after you get the updates installed if you still get a bugcheck, then run memtest86 to confirm your memory timings.

most likely though one of the driver updates will have fixed the problem.




remove this driver:
\system32\DRIVERS\AsrAppCharger.sys Tue May 10 01:28:46 2011
this driver is suspect:
System32\framebuf.dll unavailable (00000000)

machine info:
BIOS Version P2.60
BIOS Starting Address Segment f000
BIOS Release Date 02/01/2016

Manufacturer ASRock
Product 970 Pro3 R2.0
Processor Version AMD Athlon(tm) II X4 605e Processor
Processor Voltage 8bh - 1.1V
External Clock 200MHz
Max Speed 2300MHz
Current Speed 2300MHz



 
Upvote 0 Downvote
M

Mattdad1

Commendable
Jun 4, 2016
4
0
1,510
Thanks for your time on this. What a PITA... Started crashing mid-boot. I'm going to reformat and start over with a W10 ISO file on a thumb drive. Do you think this could be a hardware problem, since I tried this path before and also had constant BSODs? Memory and HDD have passed tests, I have new MB and GPU. CPU? PSU? Any suggestions? I have a feeling I'll be re-posting under the W10 group. Thanks again for your help, JohnBL!





 
Upvote 0 Downvote
M

Mattdad1

Commendable
Jun 4, 2016
4
0
1,510
JohnBL in case you're interested... I pulled one of the two DIMMs just to see what happened. I got a full clean install. I haven't had a BSOD yet, but knock wood. Any idea why my DIMMs would show as good after numerous passes through the "advanced" memory tests in windows? One of the tests took at least 8 hours, I'm sure it was longer. Anyway, thanks for your help, it's VERY nice of you to assist a stranger in need. MT
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
- the windows memory test is pretty basic, a more advanced test is memtest86
- you can get memory tests to pass it the defect happens to be in the same location where the test is loaded into memory.
-you can get memory sticks to pass while in one slot but not when placed in a different slot, just because of the slight timing changes.
- I have seen memory sticks all work individually but fail when all the memory slots were populated. I had a ASUS motherboard that actually indicated in the manual that you had to run your memory at a slower speed if you use all of the slots. Took me a while to figure that out, I used the vendor qualified memory at the correct speeds and setting but got memory failures. Then I found the little * in the manual and the note at the bottom of the page that indicated I had to run at a slower memory clock speed if I used all of the slots.


Memory defects are pretty common, I think about 8 % of tested memory modules fail to run at spec. People just don't take the time to test them.




 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom