Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: win 7 BSOD ZIP attached


27 Jan 2010   #1

Windows 7 Home x64
 
 
win 7 BSOD ZIP attached

mostly i get memory management 0x0000001A while browsing internet explorer or firefox, but today i got 0x0000003B

I've run both memtest86+ and prime95 blend for 24hrs with no errors, ram was set to proper voltage and timings

Can't figure this out please help

My System SpecsSystem Spec
.

27 Jan 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by fedz84 View Post
mostly i get memory management 0x0000001A while browsing internet explorer or firefox, but today i got 0x0000003B

I've run both memtest86+ and prime95 blend for 24hrs with no errors, ram was set to proper voltage and timings

Can't figure this out please help

Well now this is interesting. More memory corruption. what version of memtestx86, how many passes?

Ken J+



Code:
012710-17206-01.dmp    1/27/2010 3:17:36 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02d9fbb9    fffff880`08efea50    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\012710-17206-01.dmp    8    15    7600    
012610-18454-01.dmp    1/26/2010 2:24:58 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`001a57a0    00000000`0000ffff    00000000`00000000    MpFilter.sys    MpFilter.sys+1080c                    x64        C:\Users\K\Desktop\New folder\012610-18454-01.dmp    8    15    7600    
012610-17674-01.dmp    1/26/2010 2:11:44 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`00e04a20    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\012610-17674-01.dmp    8    15    7600    
012310-20857-01.dmp    1/23/2010 12:41:52 PM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`00782550    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\012310-20857-01.dmp    8    15    7600    
012010-16177-01.dmp    1/20/2010 10:53:12 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`007b1920    00000000`0000ffff    00000000`00000000    hal.dll    hal.dll+7b7f                    x64        C:\Users\K\Desktop\New folder\012010-16177-01.dmp    8    15    7600    
011910-17581-01.dmp    1/19/2010 9:50:58 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`0078e250    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    x64        C:\Users\K\Desktop\New folder\011910-17581-01.dmp    8    15    7600
EDIT: as you can see it is still coming back as mem corrupt. are you overclocking?, have a raid? something esoteric like a card reader?
My System SpecsSystem Spec
27 Jan 2010   #3

Windows 7 Home x64
 
 

memtest86+ is the newest version 4.0 it ran for 24hrs i thinks it was around 40 passes but im really not too sure
My System SpecsSystem Spec
.


27 Jan 2010   #4

Windows 7 Home x64
 
 

my 8400 gs had an old driver so i updated it, would that be a reason for any of this nonsense???
My System SpecsSystem Spec
28 Jan 2010   #5

Windows 7 Home x64
 
 

so far nothing today i also updated some other drivers for my mb yesturday
My System SpecsSystem Spec
29 Jan 2010   #6

Windows 7 Home x64
 
 

got the 0x0000001A this morning, firefox closed unexpectedly and then a minute later it BSOD. all my settings right now are on defualt. memtesting each stick individually but thats prob not gonna tell me anything since all 3 sticks passed for 24hrs. tomorrow i will try to generate a BSOD with each stick by itself.

Is it possible for the sticks to pass memtest86+ and prime95 even though one may be faulty??? I'm just having a hard time believing this right now. is there any other logical explanation??
My System SpecsSystem Spec
30 Jan 2010   #7
Microsoft MVP

 
 

Possible - yes, likely - no
I've only heard of it once (on the forums) - have never seen it happen on a system that I was working on.

Other logical suppositions:
- video memory is bad
- memory on the mobo (built in) is bad
- memory on the CPU is bad
- other hardware issues
- driver issues that cause memory management errors
- compatibility issues

Please update this older driver: WinRing0x64.sys Sat Jul 26 09:29:37 2008
It WinRing0 is a hardware access library for Windows made by OpenLibSys.org
This library allows x86/x64 Windows applications to access
- I/O port
- MSR (Model-Specific Register)
- PCI bus
etc...

Beyond that, I'd suggest running Driver Verifier to see if maybe we can catch the culprit that's causing the BSOD's. Please run it using these instructions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Summary of the BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 09:42:49.997 2010 (GMT-5)
System Uptime: 0 days 0:02:01.934
BugCheck 1A, {41790, fffffa800078e250, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 20 01:37:05.077 2010 (GMT-5)
System Uptime: 0 days 0:09:46.998
BugCheck 1A, {41790, fffffa80007b1920, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 12:38:38.344 2010 (GMT-5)
System Uptime: 0 days 0:29:05.296
BugCheck 1A, {41790, fffffa8000782550, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a98 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dllhost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 26 02:07:06.354 2010 (GMT-5)
System Uptime: 0 days 0:05:23.306
BugCheck 1A, {41790, fffffa8000e04a20, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jan 26 14:23:09.050 2010 (GMT-5)
System Uptime: 0 days 0:38:40.002
BugCheck 1A, {41790, fffffa80001a57a0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jan 27 15:14:19.046 2010 (GMT-5)
System Uptime: 0 days 0:04:10.999
BugCheck 3B, {c0000005, fffff80002d9fbb9, fffff88008efea50, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  msiexec.exe
My System SpecsSystem Spec
31 Jan 2010   #8

Windows 7 Home x64
 
 

what folder do i put the winring files in? not sure and their website isnt specific
My System SpecsSystem Spec
31 Jan 2010   #9

Windows 7 Home x64
 
 

did the verifier troubleshoot got it to crash within a couple minutes, minidump is uploaded

code was 0x000000c4 ans said something about asio.sys
My System SpecsSystem Spec
31 Jan 2010   #10

Windows 7 Home x64
 
 

i think my culprit is my Line6 toneport recording interface i was using as the sound card and after research people are saying it is not supported by windows 7 yet. Hopefully thats what is causing all these BSOD
Please check my minidump and see if there is anything else i need to be concerned about

By the way thanks for everyone that has been helping me out i really appreciate all your wisdom i've learned a lot about diagnosing problems in windows
My System SpecsSystem Spec
Reply

 win 7 BSOD ZIP attached




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:32 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33