[SOLVED] Intermittent BSOD

k7leafclover · 04-19-2009, 06:54 PM

I am getting a 0x0000001e BSOD about once every twenty four hours... can't seem to figure it out. There haven't been any system changes. This occured both before and after SP2.

Here are my specs:
ASUS P5QPRO
Q6600 @ 3.6GHz W/ CoolerMaster V10
8GB (4x2) OCZ Platinum 1066
XFX GTX260 Black Edition
Seagate Barracuda 1TB
Seagate Barracuda 2x320GB
CoolerMaster Cosmos S
Vista HP x64 SP2

and attached is my most recent minidump. Any brilliant ideas?

**manic** · 04-19-2009, 08:12 PM

You didnt mention your power supply wattage and brand. What are
your temps like?

**jcgriff2** · 04-19-2009, 08:53 PM

Hi -

Please answer the questions posed by manic.

The bugcheck on your BSOD is 0x1e - kernel mode app generated an exception, which in your case is 0xc0000005 = memory access violation.

Your kernel symbols are wrong. Use -

Code:


SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Re-run the dump using Windbg GUI. Instead of clicking on !anayyze -v, enter the following at kd>

Code:

    
!analyze -v;r;kv;lmtn;lmtsmn

Then post the output.

However, if the dump names the NT Kernel or any other Microsoft driver as the probable cause, run the driver verifier. A dump telling us a MS module is at fault will be useless.

START | type cmd.exe | right-click on cmd.exe | Run as Admin | type verifier | do the following:

Code:

DRIVER VERIFIER
1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -• Special Pool 
• Pool Tracking 
• Force IRQL checking
• Deadlock Detection
• Miscellaneous Checks4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where Microsoft is not the Provider
7. Click on Finish 
8. Re-boot

If the Driver Verifier (DV) finds a violation, it will result in a BSOD. After re-boot, you may not be able to log on. If so, boot into SAFEMODE (select Last Known Good Configuration or System Restore). To see the status of Verifier - type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". To turn Driver Verifier off - verifier /reset then re-boot. Keep the verifier running as long as possible, even if the status screen appears clear.

If you get a BSOD, run the verifier-enabled dump through Windbg and post the results from it.

Regards. . .

jcgriff2

.

k7leafclover · 04-20-2009, 06:17 PM

I thank you all for the quick response and your attempts to help :) Sorry I forgot to list my PSU in the specs. I have an In Win Commander 850W.

Core Temps

idle 36 36 32 32
load 51 50 48 48

I ran verifier, and it booted just fine. I reloaded verifier to check that all tests ran, and the did with all drivers loading. I then ran memtest 86 on all chips individually, and they all passed.

Attached is my debug, with the settings you provided, however this is from todays BSOD, not the 19th's.

**jcgriff2** · 04-23-2009, 10:40 PM

Hi -

Now I see the reason for the symbol errors - you are running SP2 RC - Release Candidate. As you probably know, this is a test version of SP2 and can be unstable.

Code:


Windows Server 2008/Windows Vista Kernel Version 6002
 (Service Pack 2.286) MP (4 procs) Free x64

The bugcheck was 0x3b = system service exception
The exception = 0xc00000005 = memory access violation

A 0x3b w/0xc..5 exception usually the result of a bad driver - one that may need updating or removal. I went through the loaded driver listing and found these - you can go thru them and see if any need updating.

Code:


timntr.sys   Wed Aug 29 07:38:23 2007 (46D568BF)
tdrpman.sys  Mon Nov 12 07:36:33 2007 (473856E1)
snapman.sys  Thu Nov 22 02:19:33 2007 (47453B95) 
WMP54GSx64.sys Tue Dec 19 13:56:03 2006 (458843D3)
ASACPI.sys   Sun Mar 27 21:30:36 2005 (42476C4C)
msfwhlpr.sys Wed Nov 28 02:25:08 2007 (474D25E4)
NuidFltr.sys Wed Aug 15 03:45:30 2007 (46C2BD2A)
point64k.sys Wed Nov 08 01:27:43 2006 (455186EF)
tifsfilt.sys Wed Aug 29 07:37:29 2007 (46D56889)
RivaTuner64.sys Tue Jul 17 14:13:42 2007 (469D14E6)
msfwdrv.sys  Wed Nov 28 02:25:12 2007 (474D25E8)

The dump was not a Vista Driver Verifier enabled mini dump. As I mentioned, SP2 beta is a test version and means that it can be unstable. Those using SP2 beta should be prepared at any time to re-install Vista. If the driver verifier produced no results and updating the above drivers does not help alleviate the BSODs, I suggest that you re-install Vista SP1 to assure that your hardware is OK.

Regards. . .

jcgriff2

.

k7leafclover · 04-27-2009, 07:55 PM

Okay, tonight it went into a perpetual BSOD so I reinstalled. Within one hour of the clean install I had two BSOD's. Attached are the analysis's of them. I have only reinstalled a few of my programs, like Office and 7zip. Other than that it is just windows SP1....

Dracia · 04-28-2009, 03:29 AM

Are you able to update this driver?

Code:

ASACPI.sys   Sun Mar 27 21:30:36 2005 (42476C4C)

It was made before Vista was, so therefore too old to be on there and possibly causing conflicts.

**jcgriff2** · 04-28-2009, 03:59 PM

This Broadcom driver is problematic as well - needs update

Code:

bcmwl664.sys Tue Oct 03 21:39:37 2006 (45231EE9)

Do you have a Microsoft USB mouse & or keyboard from the days of XP?

Code:


 point64k.sys Wed Nov 08 01:27:43 2006 (455186EF)

 NuidFltr.sys Wed Aug 15 03:45:30 2007 (46C2BD2A)

Code:

DRIVER VERIFIER
1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -• Special Pool 
• Pool Tracking 
• Force IRQL checking
• Deadlock Detection
• Miscellaneous Checks4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where Microsoft is not the Provider
7. Click on Finish 
8. Re-boot

If the Driver Verifier (DV) finds a violation, it will result in a BSOD. After re-boot, you may not be able to log on. If so, boot into SAFEMODE (select Last Known Good Configuration or System Restore). To see the status of Verifier - type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". To turn Driver Verifier off - verifier /reset then re-boot. Keep the verifier running as long as possible, even if the status screen appears clear.

If no results w/ driver verifier, test RAM -
memtest86+ - http://www.memtest.org/

Regards. . .

jcgriff2

.

k7leafclover · 04-29-2009, 04:52 AM

The fact that it BSOD'ed immediately after a clean install, definitely pointed to hardware. I figured that RAM was the easiest to test, so I ran memtest86 overnight. Found some errors. I have 4x2GB in dual channel kits, so I ran each kit seperately the following day. One kit failed epically and the other passed multiple runs with no errors. Shazaam we have a BSOD cause :)

**jcgriff2** · 04-30-2009, 10:53 PM

Thanks for posting back w/ solution.

Regards. . .

jcgriff2

.

04-19-2009, 08:12 PM	#2 (permalink)
manic Mod Hardware Team Join Date: Aug 2005 Location: Florida Posts: 5,253 OS: xp	Re: Intermittent BSOD You didnt mention your power supply wattage and brand. What are your temps like? __________________

04-19-2009, 08:53 PM	#3 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: The Great State of New Jersey - away from the gross corruption of the Riverside County, CA, SO office. SHAMEFUL ! Posts: 10,160 OS: Windows 7, Vista Ultimate My System	Re: Intermittent BSOD Hi - Please answer the questions posed by manic. The bugcheck on your BSOD is 0x1e - kernel mode app generated an exception, which in your case is 0xc0000005 = memory access violation. Your kernel symbols are wrong. Use - Code: SRVc:\symbolshttp://msdl.microsoft.com/download/symbols Re-run the dump using Windbg GUI. Instead of clicking on !anayyze -v, enter the following at kd> Code: !analyze -v;r;kv;lmtn;lmtsmn Then post the output. However, if the dump names the NT Kernel or any other Microsoft driver as the probable cause, run the driver verifier. A dump telling us a MS module is at fault will be useless. START \| type cmd.exe \| right-click on cmd.exe \| Run as Admin \| type verifier \| do the following: Code: DRIVER VERIFIER 1. Select 2nd option - "Create custom settings (for code developers)" 2. Select 2nd option - "Select individual settings from a full list" 3. Check these boxes - • Special Pool • Pool Tracking • Force IRQL checking • Deadlock Detection • Miscellaneous Checks 4. Select last option - "Select driver names from a list" 5. Click on the Provider heading - sorts list by Provider 6. Check ALL boxes where Microsoft is not the Provider 7. Click on Finish 8. Re-boot If the Driver Verifier (DV) finds a violation, it will result in a BSOD. After re-boot, you may not be able to log on. If so, boot into SAFEMODE (select Last Known Good Configuration or System Restore). To see the status of Verifier - type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". To turn Driver Verifier off - verifier /reset then re-boot. Keep the verifier running as long as possible, even if the status screen appears clear. If you get a BSOD, run the verifier-enabled dump through Windbg and post the results from it. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread Glad to be home in the Great State of New Jersey ! !

04-23-2009, 10:40 PM	#5 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: The Great State of New Jersey - away from the gross corruption of the Riverside County, CA, SO office. SHAMEFUL ! Posts: 10,160 OS: Windows 7, Vista Ultimate My System	Re: Intermittent BSOD Hi - Now I see the reason for the symbol errors - you are running SP2 RC - Release Candidate. As you probably know, this is a test version of SP2 and can be unstable. Code: Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2.286) MP (4 procs) Free x64 The bugcheck was 0x3b = system service exception The exception = 0xc00000005 = memory access violation A 0x3b w/0xc..5 exception usually the result of a bad driver - one that may need updating or removal. I went through the loaded driver listing and found these - you can go thru them and see if any need updating. Code: timntr.sys Wed Aug 29 07:38:23 2007 (46D568BF) tdrpman.sys Mon Nov 12 07:36:33 2007 (473856E1) snapman.sys Thu Nov 22 02:19:33 2007 (47453B95) WMP54GSx64.sys Tue Dec 19 13:56:03 2006 (458843D3) ASACPI.sys Sun Mar 27 21:30:36 2005 (42476C4C) msfwhlpr.sys Wed Nov 28 02:25:08 2007 (474D25E4) NuidFltr.sys Wed Aug 15 03:45:30 2007 (46C2BD2A) point64k.sys Wed Nov 08 01:27:43 2006 (455186EF) tifsfilt.sys Wed Aug 29 07:37:29 2007 (46D56889) RivaTuner64.sys Tue Jul 17 14:13:42 2007 (469D14E6) msfwdrv.sys Wed Nov 28 02:25:12 2007 (474D25E8) The dump was not a Vista Driver Verifier enabled mini dump. As I mentioned, SP2 beta is a test version and means that it can be unstable. Those using SP2 beta should be prepared at any time to re-install Vista. If the driver verifier produced no results and updating the above drivers does not help alleviate the BSODs, I suggest that you re-install Vista SP1 to assure that your hardware is OK. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread Glad to be home in the Great State of New Jersey ! ! Last edited by jcgriff2; 04-30-2009 at 10:52 PM.

04-28-2009, 03:29 AM	#7 (permalink)
Dracia Registered User Join Date: Mar 2008 Location: Surrey, UK Posts: 470 OS: Windows Vista Home Premium SP1 My System	Re: Intermittent BSOD Are you able to update this driver? Code: ASACPI.sys Sun Mar 27 21:30:36 2005 (42476C4C) It was made before Vista was, so therefore too old to be on there and possibly causing conflicts. __________________ Please do not PM me for support or add me to Windows Live Messenger. It's better for questions to be answered in the forum for others to read. You may PM me if you were expecting a response from me and 72 hours have passed.

04-28-2009, 03:59 PM	#8 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: The Great State of New Jersey - away from the gross corruption of the Riverside County, CA, SO office. SHAMEFUL ! Posts: 10,160 OS: Windows 7, Vista Ultimate My System	Re: Intermittent BSOD This Broadcom driver is problematic as well - needs update Code: bcmwl664.sys Tue Oct 03 21:39:37 2006 (45231EE9) Do you have a Microsoft USB mouse & or keyboard from the days of XP? Code: point64k.sys Wed Nov 08 01:27:43 2006 (455186EF) NuidFltr.sys Wed Aug 15 03:45:30 2007 (46C2BD2A) I do see you are now Vista SP1. After driver updates, run driver verifier - START \| type cmd.exe \| right-click on cmd.exe \| Run as Admin \| type verifier \| do the following: Code: DRIVER VERIFIER 1. Select 2nd option - "Create custom settings (for code developers)" 2. Select 2nd option - "Select individual settings from a full list" 3. Check these boxes - • Special Pool • Pool Tracking • Force IRQL checking • Deadlock Detection • Miscellaneous Checks 4. Select last option - "Select driver names from a list" 5. Click on the Provider heading - sorts list by Provider 6. Check ALL boxes where Microsoft is not the Provider 7. Click on Finish 8. Re-boot If the Driver Verifier (DV) finds a violation, it will result in a BSOD. After re-boot, you may not be able to log on. If so, boot into SAFEMODE (select Last Known Good Configuration or System Restore). To see the status of Verifier - type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". To turn Driver Verifier off - verifier /reset then re-boot. Keep the verifier running as long as possible, even if the status screen appears clear. If no results w/ driver verifier, test RAM - memtest86+ - http://www.memtest.org/ Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread Glad to be home in the Great State of New Jersey ! !

04-29-2009, 04:52 AM	#9 (permalink)
k7leafclover Registered User Join Date: Apr 2009 Posts: 4 OS: Vista HP x64 SP2	Re: Intermittent BSOD The fact that it BSOD'ed immediately after a clean install, definitely pointed to hardware. I figured that RAM was the easiest to test, so I ran memtest86 overnight. Found some errors. I have 4x2GB in dual channel kits, so I ran each kit seperately the following day. One kit failed epically and the other passed multiple runs with no errors. Shazaam we have a BSOD cause :)

04-30-2009, 10:53 PM	#10 (permalink)
jcgriff2 Moderator, Microsoft Supp Join Date: Sep 2007 Location: The Great State of New Jersey - away from the gross corruption of the Riverside County, CA, SO office. SHAMEFUL ! Posts: 10,160 OS: Windows 7, Vista Ultimate My System	Re: Intermittent BSOD Thanks for posting back w/ solution. Regards. . . jcgriff2 . __________________ . . . . . . . . BSOD Posting Instructions B Expecting a reply and waiting > 36 hours ? Send a PM to me containing a link to your thread Glad to be home in the Great State of New Jersey ! !