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: New here ~ BSOD help

27 Jan 2010   #11
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jp916 View Post
ok got memtest to work, on pass 3 with no errors so far, still going to let it run for another couple of pass
While you are. It might be a heat issue. you should grab a copy of cpu-z, and gpu-z. They are free and will keep track of your temps.

Let us know the results.

Ken


My System SpecsSystem Spec
.
28 Jan 2010   #12
Jp916

windows 7
 
 

So i ran memtest to 5 passes with no errors. I downloaded cpuz and gpuz and posted the screen shot of what I got. I tried to check the temperature on gpuz, but when I clicked on the sensor tab, there's nothing there. Maybe because its a laptop? I'm not sure. I don't know where to go from here. Any help please?
My System SpecsSystem Spec
28 Jan 2010   #13
Jp916

windows 7
 
 

anyone?
My System SpecsSystem Spec
.

30 Jan 2010   #14
Jp916

windows 7
 
 

got 2 more today...where should i go from here?
My System SpecsSystem Spec
30 Jan 2010   #15
usasma
Microsoft MVP

 
 

Diagnostic tests:
Quote:
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)

*****
Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS
Also try this:
Quote:
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.
I'd run the Hard Drive diagnostic and CHKDSK stuff first if it were me.
Both dump files blame NTFS.SYS - a files system driver for the Windows OS
That brings the hard drive and file system under suspicion - so the Hard Drive diagnostic and CHKDSK are the most appropriate tests to rule out problems there.

Also, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall/remove:
Quote:
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Code:
mdmxsdk.sys  Mon Jun 19 17:27:26 2006 -Conexant Diagnostic Interface Driver
HpqKbFiltr.sys Mon Jun 18 18:13:11 2007 - HP Quick Launch Buttons HpqKbFiltr Keyboard Filter Driver                                                              
PxHlpa64.sys Wed Mar 12 21:58:17 2008 - Sonic CD/DVD driver (common to several CD/DVD burning programs)
IntcHdmi.sys Mon Jun 30 08:52:42 2008 - Intel High Definition Audio HDMI                                                              
CHDRT64.sys  Fri Oct 03 14:40:10 2008 - Conexant High Definition SmartAudio
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 - Research In Motion Virtual COM Port Tunnel driver
Summary of the BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 29 21:53:00.638 2010 (GMT-5)
System Uptime: 0 days 8:32:40.667
BugCheck 24, {1904fb, fffff88008545598, fffff88008544df0, fffff80002e62517}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 30 01:55:45.576 2010 (GMT-5)
System Uptime: 0 days 4:01:53.480
BugCheck 24, {1904fb, fffff88002fcb598, fffff88002fcadf0, fffff80002eb4517}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
My System SpecsSystem Spec
31 Jan 2010   #16
Jp916

windows 7
 
 

Hey thanks usama, here's the results of the chkdsk. I'm still working on hard drive diagnostic and will post back

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)...
339968 file records processed. File verification completed.
159 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)...
395192 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
339968 file SDs/SIDs processed. Cleaning up 5696 unused index entries from index $SII of file 0x9.
Cleaning up 5696 unused index entries from index $SDH of file 0x9.
Cleaning up 5696 unused security descriptors.
CHKDSK is compacting the security descriptor stream
27613 data files processed. CHKDSK is verifying Usn Journal...
37276392 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
339952 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
36454554 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

231316479 KB total disk space.
85001604 KB in 144985 files.
107908 KB in 27616 indexes.
0 KB in bad sectors.
388747 KB in use by the system.
4096 KB occupied by the log file.
145818220 KB available on disk.

4096 bytes in each allocation unit.
57829119 total allocation units on disk.
36454555 allocation units available on disk.

Internal Info:
00 30 05 00 42 a2 02 00 72 ad 04 00 00 00 00 00 .0..B...r.......
e3 6e 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 .n..,...........
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.
My System SpecsSystem Spec
08 Feb 2010   #17
Jp916

windows 7
 
 

This is getting frustrating. Here are some more minidumps. Any more suggestions?
My System SpecsSystem Spec
11 Feb 2010   #18
usasma
Microsoft MVP

 
 

Quote:
Windows has made corrections to the file system
This makes the hard drive diagnostic more important to complete.
It's a long story, but the NTFS file system has serious trouble if CHKDSK has to fix it.

11 crash dumps (13 if we include the previous 2) - 2 STOP 0x1A; 4 STOP 0x24; 6 STOP 0x50; and 1 STOP 0x7E. 6 blame memory corruption, 4 blame NTFS.SYS, 2 blame ntkrnlmp.exe (the kernel of the OS), and one blames AVGIDSFilter.sys (an AVG filter driver).

Let's start with the AVG:
Quote:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the AVG from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of AVG using this free tool: AVG Antivirus and Security Software - Tools download
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
This may be the start of a pattern of differing BSOD's - which usually indicates a hardware problem. In this case, I'd suspect the hard drive or the controller on your motherboard as the most likely problem (DO NOT purchase new hardware because of this suspicion). If the hard drive passes the diagnostics, then ensure that the motherboard storage controller/chipset drivers are replaced with fresh copies.

Then, please update these older drivers:
Code:
mdmxsdk.sys  Mon Jun 19 17:27:26 2006
PxHlpa64.sys Wed Mar 12 21:58:17 2008
SynTP.sys    Thu Mar 27 21:15:32 2008
You'll find the links for downloading/updating these drivers at: Driver Reference

So, after finishing all the above stuff (to include the hard drive diagnostic), let's wait to see if there's further BSOD's.

Summary of the BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 11:37:57.034 2010 (GMT-5)
System Uptime: 0 days 14:03:01.063
BugCheck 1A, {31, fffffa800690b700, fffff8800ee31000, fffff8a0021ee036}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6378 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb  4 18:55:58.820 2010 (GMT-5)
System Uptime: 0 days 7:17:27.849
BugCheck 1A, {41790, fffffa8001df7f60, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LogonUI.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 13:55:53.354 2010 (GMT-5)
System Uptime: 0 days 9:13:58.258
BugCheck 24, {1904fb, fffff88002faf548, fffff88002faeda0, fffff80002e60517}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 19:59:10.580 2010 (GMT-5)
System Uptime: 0 days 5:57:47.609
BugCheck 50, {fffffb4003419efb, 0, fffff80002ed2d3b, 7}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 13:34:18.780 2010 (GMT-5)
System Uptime: 0 days 8:56:59.808
BugCheck 24, {1904fb, fffff88004648508, fffff88004647d60, fffff80002eb6517}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Feb  7 01:56:28.560 2010 (GMT-5)
System Uptime: 0 days 7:47:09.589
BugCheck 1000007E, {ffffffffc0000005, fffff80002eb6517, fffff880031245a8, fffff88003123e00}
*** WARNING: Unable to verify timestamp for AVGIDSFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.sys
Probably caused by : AVGIDSFilter.sys ( AVGIDSFilter+5c8e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 18:08:48.515 2010 (GMT-5)
System Uptime: 0 days 4:34:01.419
BugCheck 50, {fffffb4000653be8, 0, fffff80002f10bd1, 7}
Probably caused by : memory_corruption ( nt!MiFreeWsleList+111 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb  5 20:24:52.580 2010 (GMT-5)
System Uptime: 0 days 0:25:15.609
BugCheck 50, {fffffb400095e6d8, 0, fffff80002e4b091, 7}
Probably caused by : memory_corruption ( nt!MiRemoveWorkingSetPages+361 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Feb  7 11:49:16.532 2010 (GMT-5)
System Uptime: 0 days 9:51:54.561
BugCheck 50, {fffffb4001da4798, 0, fffff80002ea9091, 7}
Probably caused by : memory_corruption ( nt!MiRemoveWorkingSetPages+361 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WLIDSVC.EXE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Feb  7 12:51:45.671 2010 (GMT-5)
System Uptime: 0 days 1:02:19.204
BugCheck 50, {fffffb400091894b, 0, fffff80002ed4d3b, 7}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Feb  8 12:12:59.562 2010 (GMT-5)
System Uptime: 0 days 10:52:09.591
BugCheck 50, {fffff6a0000030b0, 0, fffff80002fc3e77, 5}
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LogonUI.exe
My System SpecsSystem Spec
12 Feb 2010   #19
Jp916

windows 7
 
 

thanks alot usasma, I will do as recommended and keep you posted
My System SpecsSystem Spec
Reply

 New here ~ BSOD help




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 06:13.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App