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: Several Different BSODs


06 Jul 2010   #1

Windows 7 Home Premium 64-bit
 
 
Several Different BSODs

Hi, I recently had a computer built that was running flawlessly until about 1 week ago (it was finished on June 12th). BSODs keep happening randomly anywhere from 1 to 4 times per day, and I have received 4 different ones so far: 1e, 3b, 1000007e, and a. They have all happened while doing various different things, and even during my normal computing habits they still seem to be random. I am by no means a computer expert and am still fairly new to a lot of this.

Below are the reports from the SF diagnostic tool and a document I've made of most of the BSOD error reports after restart.

Thanks.


Attachment 83610

Attachment 83611

Attachment 83612

Attachment 83613

Attachment 83614

Attachment 83615

My System SpecsSystem Spec
.

07 Jul 2010   #2
Microsoft MVP

 
 

10 Memory dumps, from 22 Jun to 06 Jul 2010
4 different STOP error codes, blaming 2 different causes
While this hasn't established a pattern yet, I'd first suspect driver issues - with hardware problems being a possibility if we rule out driver issues.

First, please replace these 2 older drivers by installing the latest Windows 7 drivers available from the manufacturer's website:
Code:
nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) - http://www.carrona.org/dvrref.html#nvm62x64.sys
skfiltv.sys  Thu Aug 14 02:48:33 2008 -    probably Pilote USB audio (WDM); Creative wireless  headset; Hs-1200   Digital Wireless Headset - http://www.carrona.org/dvrref.html#skfiltv.sys
Once that's done, please monitor for further BSOD's. If you get any within the next 12 hours of operation - please follow these directions for running Driver Verifier (there's no need to run this if you don't get BSOD's of the type that you've been having):
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 01:07:37.916 2010 (UTC - 4:00)
System Uptime: 0 days 7:06:23.370
BugCheck A, {780002ff8f48, 2, 1, fffff80002e7d4f3}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+133 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul  5 02:57:19.233 2010 (UTC - 4:00)
System Uptime: 0 days 8:03:34.592
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 18:52:50.598 2010 (UTC - 4:00)
System Uptime: 0 days 1:05:41.958
BugCheck 1000007E, {ffffffffc0000005, fffff80002fff66a, fffff88007ba3888, fffff88007ba30f0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+5ba )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 17:46:27.895 2010 (UTC - 4:00)
System Uptime: 0 days 1:47:50.239
BugCheck 3B, {c0000005, fffff80002fb5257, fffff88003ffb580, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+1a7 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avgnsa.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 15:58:00.351 2010 (UTC - 4:00)
System Uptime: 0 days 1:29:04.710
BugCheck 1000007E, {ffffffffc0000005, fffff80002fb9257, fffff880031538b8, fffff88003153120}
Probably caused by : ndis.sys ( ndis!ndisQueuedCheckForHang+1a5 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 04:20:39.429 2010 (UTC - 4:00)
System Uptime: 0 days 0:36:57.789
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 03:42:34.682 2010 (UTC - 4:00)
System Uptime: 0 days 5:42:57.041
BugCheck 3B, {c0000005, fffff80003001257, fffff8800888c0b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+1a7 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  daorigins.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 21:58:55.973 2010 (UTC - 4:00)
System Uptime: 0 days 7:08:03.333
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 01:01:54.193 2010 (UTC - 4:00)
System Uptime: 0 days 9:21:29.630
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 22 23:24:34.640 2010 (UTC - 4:00)
System Uptime: 0 days 7:52:46.000
BugCheck 1000007E, {ffffffffc0000096, fffff80002edd770, fffff8800336a748, fffff88003369fb0}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+1f0 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
  
  
 
My System SpecsSystem Spec
08 Jul 2010   #3

Windows 7 Home Premium 64-bit
 
 

Thanks for the response

I updated both of those drivers but still received a similar BSOD a few hours later; Running the Driver Verifier I picked up two of them, the first immediately after reboot, and the second an hour or so later while playing Crysis.

The first DMP file is from the BSOD after driver updates, and the other two while running the Driver Verifier:

Attachment 83920
My System SpecsSystem Spec
.


08 Jul 2010   #4

Windows 7 x64, Windows XP SP3, Fedora
 
 

Hi,

BUGCHECK SUMMARY
Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  8 20:14:00.625 2010 (GMT+12)
System Uptime: 0 days 1:01:13.000
BugCheck A, {fffff88003341000, c, 1, fffff80002e7943d}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  WmiPrvSE.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  8 19:12:21.968 2010 (GMT+12)
System Uptime: 0 days 0:00:14.343
BugCheck A, {1, 2, 0, fffff80002ea7306}
Probably caused by : Pool_Corruption ( nt!ExFreePool+d34 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  8 16:46:47.772 2010 (GMT+12)
System Uptime: 0 days 4:05:33.225
BugCheck 3B, {c0000005, fffff80003003257, fffff880043cf0b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+1a7 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Crysis.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
The dumps were VERIFIER_ENABLED however they did not pick up on any 3rd party drivers making it even more likely that it is hardware.

Code:

skfiltv.sys  Thu Aug 14 18:48:33 2008 (48A3D541)
That driver is still present on your system, as usasma said it is probably a driver for an USB headset. If you cannot find an update for this from the manufacturer's site then please uninstall it so we can see if it is the cause.

It is still likely that it is hardware.

Start hardware testing with a memtest:
Quote   Quote: Originally Posted by reventon
Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here Memtest86+ - Advanced Memory Diagnostic Tool

Then (if you have chosen the ISO) burn the ISO using ImgBurn: The Official ImgBurn Website

Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.
Regards,
Reventon
My System SpecsSystem Spec
Reply

 Several Different BSODs




Thread Tools



Similar help and support threads for2: Several Different BSODs
Thread Forum
Solved Many BSODs while doing anything! BSOD Help and Support
BSODs, lots of BSODS BSOD Help and Support
A few different BSODs.. BSOD Help and Support
Bsods help BSOD Help and Support
BSODs every day... need help BSOD Help and Support
BSODs - need help! BSOD Help and Support

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 02:06 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