win 7 BSOD ZIP attached

[fedz84]

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

 

[zigzag3143]

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+

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?

 

[fedz84]

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

 

[fedz84]

my 8400 gs had an old driver so i updated it, would that be a reason for any of this nonsense???

 

[fedz84]

so far nothing today i also updated some other drivers for my mb yesturday

 

[fedz84]

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??

 

[usasma]

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:

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/Win7 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:

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

 

[fedz84]

what folder do i put the winring files in? not sure and their website isnt specific

 

[fedz84]

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

code was 0x000000c4 ans said something about asio.sys

 

[fedz84]

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

 

[fedz84]

so i uninstalled the line6 drivers and then ran verifier again bsod before i got onto my log in screen

attached the lastest dump files

codes 0x000000A and 0x00000024

 

[fedz84]

bump

 

[usasma]

Post #9 -

131full.zip (87.1 KB, 0 views)
Post #11 -

131full.zip (87.1 KB, 0 views)

Were these 2 uploads supposed to be identical?

You have 4 memory dumps, 3 of which are Verifier Enabled Memory Dumps - and they have 3 different errors and causes.

Most likely this is a hardware problem with your system, less likely is that there are 3 separate problems that we've gotta fix.

Please turn Driver Verifier off (Delete existing settings).

Then, let's start with these hardware diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, please run this test:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt.
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.

Please post back with the results and we'll move on to further troubleshooting.

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 04:58:28.207 2010 (GMT-5)
System Uptime: 0 days 0:15:08.003
BugCheck 1A, {41790, fffffa80007c8420, ffff, 0}
[U][B]Probably caused by : ntkrnlmp.exe [/B][/U]( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  [U][B]VISTA_DRIVER_FAULT[/B][/U]
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 11:51:32.966 2010 (GMT-5)
System Uptime: 0 days 0:02:28.075
BugCheck C4, {f6, 134, fffffa8008350b30, fffff88002c186f6}
*** WARNING: Unable to verify timestamp for AsIO.sys
*** ERROR: Module load completed but symbols could not be loaded for AsIO.sys
[U][B]Probably caused by : AsIO.sys[/B][/U] ( AsIO+16f6 )
DEFAULT_BUCKET_ID:  [U][B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B][/U]
PROCESS_NAME:  UpdateChecker.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 12:54:00.466 2010 (GMT-5)
System Uptime: 0 days 0:00:12.402
BugCheck 24, {1904fb, fffff880033759a8, fffff88003375200, fffff80002aefa83}
[U][B]Probably caused by : Ntfs.sys[/B][/U] ( Ntfs!NtfsNonCachedIo+23f )
DEFAULT_BUCKET_ID:  [U][B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B][/U]
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 31 12:55:57.165 2010 (GMT-5)
System Uptime: 0 days 0:00:25.211
BugCheck A, {0, 2, 0, fffff80002ad90b6}
*** WARNING: Unable to verify timestamp for MCfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MCfilt64.sys
[U][B]Probably caused by : MCfilt64.sys [/B][/U]( MCfilt64+1817 )
DEFAULT_BUCKET_ID:  [U][B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B][/U]
PROCESS_NAME:  System

 

[fedz84]

check disk log file

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
132608 file records processed. File verification completed.
65 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
177594 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file DREF_H~3.HTM (76246) into directory file 58887.
Recovering orphaned file dref=http%253A%252F%252Fads.ak.facebook.com%252Fads%252Fcreative%252Fmsn%252Fus-120groupevent[1].html (76246) into directory file 58887.
2 unindexed files scanned. Recovering orphaned file MPCMDR~1.LOC (76509) into directory file 2174.
Recovering orphaned file MpCmdRun-AF-53C9D589-6B66-4F30-9BAB-9A0193B0BAFC.lock (76509) into directory file 2174.
0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
132608 file SDs/SIDs processed. Cleaning up 63 unused index entries from index $SII of file 0x9.
Cleaning up 63 unused index entries from index $SDH of file 0x9.
Cleaning up 63 unused security descriptors.
Security descriptor verification completed.
22494 data files processed. CHKDSK is verifying Usn Journal...
33984112 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
132592 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
40222932 free clusters processed. Free space verification is complete.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
209611775 KB total disk space.
48414612 KB in 107937 files.
66764 KB in 22495 indexes.
0 KB in bad sectors.
238671 KB in use by the system.
65536 KB occupied by the log file.
160891728 KB available on disk.
4096 bytes in each allocation unit.
52402943 total allocation units on disk.
40222932 allocation units available on disk.
Internal Info:
00 06 02 00 8c fd 01 00 e6 ee 03 00 00 00 00 00 ................
cc 0b 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.

 

[fedz84]

ran the hd diagnostics utility from samsung and it came back saying:
can't open cd driver cd001
SHSUCDX can't install
out of memory error
bad command file

note: on the samsung website the utiliy doesn't seem to be updated for the spinpoint f3s, not sure if this could of screwed up the test

 

[fedz84]

I ran HD tune and the error scan came back clean but when i ran commmand prompt sfc /scannow, during the scan it failed with a mesage saying something about windows resource protection, so i tried it again same thing at a different part of the scan and on the third try it BSOD with a bad pool caller code 0x000000C2...file attached

I'm thinking about just reinstalling the OS and just start from scratch but up until today since i uninstalled that line6 driver i stopped getting that memory management bsod while surfing the web

 

[fedz84]

so i did a fresh install on the OS and updated drivers n bios first then have been running driver verifier with no promblems since last night with no bsod's. im gonna run it for a couple of days and if no bsod's occur is it safe to say the system is stable or is there any other tests i should take???? since prime95 and memtest86+ ran fine before the reinstall i dont think it will be necessary to run them again. I believe the problem occured with the Line6 driver that was not compatible with windows 7. i hope, knock on wood.

 

[usasma]

There's no use in running Driver Verifier at this point. It's not designed as a general troubleshooting tool, and it may actually cause BSOD's when there's nothing wrong.

It's good to hear that you're not having problems tho' - thanks for letting us know!