Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Vista BSOD help


  • Please log in to reply

#1
Dems

Dems

    New Member

  • Member
  • Pip
  • 4 posts
I got this computer back in August and have been having issues ever since. I did a search online and came up with a few solutions, none of which have solved this issue.

I tried all the things on this thread, none of which gave any help.
http://www.geekstogo...en-t250164.html

And I tried the "Verifier" solution in this link, and when I rebooted, Windows failed. Went back to "Last good config" to get my computer to come back.
http://www.geekstogo...th-t224077.html

The only thing I haven't tried is re-installing Vista, which I'd like to avoid if at all possible, but I'm open to anything at this moment. I'm providing my dump files in the attachment (complements of BlueScreenView). If there is any other information you need, feel free to ask.

Windows Vista Ultimate (64 bit) - Service Pack 2
Processor: Intel Core 2 Duo CPU, T7800, 2.60Ghz
Memory: 2GB (one stick)


<EDIT>
Forgot to mention my computer got left at a friends house from 10/15/09 till 1/5/10, hence the time gap.
</EDIT>

Attached Files

  • Attached File  BSOD.txt   16.79KB   323 downloads

Edited by Dems, 04 February 2010 - 06:03 PM.

  • 0

Advertisements


#2
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Since this is 6 months old computer (bought in August and first error is listed already in September), I'd seriously consider checking it out under warranty.
  • 0

#3
jcgriff2

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP

And I tried the "Verifier" solution in this link, and when I rebooted, Windows failed. Went back to "Last good config" to get my computer to come back.
http://www.geekstogo...th-t224077.html


The sheer fact that you could not log back into Vista after the Driver Verifier ran means that the D/V flagged a driver. This is perfectly normal for the Driver Verifier - it means it did its job. Did you see the bugcheck (STOP error) or the driver name on the Blue Screen - maybe a 0x000000c4? If not, the "VERIFIER_ENABLED" mini kernel dump file can tell us. Hopefully it will contain the name of the 3rd party offending driver

Your attachment contained the results for 14 BSOD dumps, 13 of which occurred between 9/13/2009 and 10/12/2009 then all was quiet until the most recent BSOD on 2/3/2010. I'm not sure at this time whether that was the verifier-enabled Vista minidump or not.

Look in c:\windows\minidump - the files that I am looking for will be named Mini020310-01.dmp or similar. Copy all dumps in the \minidump folder to your Documents folder. Also, run msinfo32, which will provide me with basic system information.

msinfo32 -
START | type msinfo32 | save as an NFO file (NFO = file ext default)

Zip up the dump files + the msinfo32 NFO file and attach to your next post.

Contacting the manufacturer is certainly a good idea; however, the first thing they will have you do is re-install Vista (not always a bad idea). They will not attempt to trouble-shoot the issues surrounding the BSODs until the OS is re-installed. So let's take a look at the software side of this first.

Any ideas what brought the BSODs back after a 4 month absence? Any newly installed software or hardware?

Regards. . .

jcgriff2

.
  • 0

#4
Dems

Dems

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Alright, I re-ran the verifier and it came up with a BSOD (which disappeared before I could see the issue), but it didn't leave a minidump file. There are two new crashes in my minidump now, both of which happened while I was trying to get back to this thread.

I forgot to mention before but my computer was left at a friends house during those months hence there not being any BSODs to report in that time frame. I got it back January 5th and didn't have an issue until a few days ago so don't know what to say on that.

Any reason why I'm not getting a dump file for the verifier run?

Attached Files


  • 0

#5
jcgriff2

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP
Hi -

The bugchecks on the 16 mini kernel dumps -
(15) 0x4a = a thread is returning to user mode from a system call with an improper IRQL. The probable cause of each = NT Kernel; all failed under Zone Alarm

(1) [0x9f (0x3,,,) = driver in an inconsistant power state - blocking an IRP (I/O Request Packet) for too long a time. The probable cause = Intel wifi driver; Zone Alarm involved in this one as well.

All of these drivers should be updated -
btwaudio.sys Thu Mar 29 14:52:36 2007 (460C0AF4) - Bluetooth<BR>btwavdt.sys  Mon Feb 26 00:06:58 2007 (45E26AF2)<BR>btwrchid.sys Mon Feb 26 00:08:50 2007 (45E26B62)<BR>CAX_CNXT.sys Fri Dec 22 15:29:46 2006 (458C403A) - Conexant<BR>CAX_DPV.sys  Fri Dec 22 15:33:24 2006 (458C4114)<BR>CAXHWAZL.sys Fri Dec 22 15:30:47 2006 (458C4077)<BR><BR>cpqbttn64.sysWed Jun 28 11:40:47 2006 (44A2A2FF)<BR>DLABMFSE.SYS Thu Oct 26 19:19:26 2006 (4541427E) - SONIC Solutions<BR>DLABOIOE.SYS Thu Oct 26 19:19:22 2006 (4541427A)<BR>DLACDBHE.SYS Thu Feb 08 23:05:10 2007 (45CBF2F6)<BR>DLADResE.SYS Thu Oct 26 19:20:30 2006 (454142BE)<BR>DLAIFS_E.SYS Thu Oct 26 19:18:00 2006 (45414228)<BR>DLAOPIOE.SYS Thu Oct 26 19:20:01 2006 (454142A1)<BR>DLAPoolE.SYS Thu Oct 26 19:18:37 2006 (4541424D)<BR>DLARTL_E.SYS Thu Feb 08 23:04:36 2007 (45CBF2D4)<BR>DLAUDF_E.SYS Thu Oct 26 19:19:00 2006 (45414264)<BR>DLAUDFAE.SYS Thu Oct 26 19:19:20 2006 (45414278)<BR>DRVECDB.SYS  Fri Jul 21 14:21:08 2006 (44C11B14)<BR>DRVEDDM.SYS  Fri Feb 09 15:34:03 2007 (45CCDABB)<BR><BR>erometer.sys Fri Jan 05 14:42:07 2007 (459EAA0F)<BR>HECIx64.sys  Fri Apr 06 12:27:37 2007 (461674F9)<BR>hpdskflt.sys Fri Jan 05 14:42:08 2007 (459EAA10)<BR>HpqKbFiltr.syMon Jun 18 18:13:11 2007 (46770377) - HP<BR>mdmxsdk.sys  Mon Jun 19 17:27:26 2006 (449716BE) - HP<BR><BR>NETw4v64.sys Sun Feb 25 09:19:09 2007 (45E19ADD) - Intel wifi<BR><BR>psd.sys	  Tue Jan 23 14:07:40 2007 (45B65CFC)<BR><BR>rismcx64.sys Wed Aug 16 01:59:16 2006 (44E2B434)<BR>rixdpx64.sys Fri Nov 17 23:07:46 2006 (455E8712)<BR>RsvLock.SYS  Thu Apr 26 14:23:36 2007 (4630EE28)<BR>SafeBoot.sys Thu Apr 26 14:23:18 2007 (4630EE16)<BR>SbAlg.sys	Thu Oct 05 12:43:20 2006 (45253628)<BR>SbFsLock.sys Thu Mar 29 11:54:08 2007 (460BE120)<BR>secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)<BR>xaudio64.sys Tue Nov 28 19:45:04 2006 (456CD810)

`

`
WERCON shows 145 application crahses beginning on 8-25-2009 -
- 48 on 9-16-09
- 58 on 11-7-09

They were primarily network-related incidents. Then all was quiet until 2-1-2010

I believe several factors contributed to these appcrashes as they temselves are listed as crashing -
- uTorrent
- Zone Alarm

I would suggets that you remove both, specifically Zone Alarm as I believe it to be responsible for most of your system troubles - especially those relating to netowrk activity. The firwall found in Zone Alarm and other products like it tend to block local NETBIOS ports which in turn cause Vista (& now Windows 7) system services to crash usually with a 0xc0000005 excception - a memory access violation. In this case "access denied".

Zone Alarm Removal --> http://server.iad.li...amp;action=view

Upon removal completion, reset Windows Firewall, then re-boot.

To reset the Windows Firewall to its default settings -
START | type FirewallSettings.exe into the start search box | click on FirewallSettings.exe above | select the Advanced Tab | click on "Restore Defaults" | Click Apply, OK


uTorrent is notorious for utilizing high amounts of Intenet Activity which slows your other Internet activities down.

Your HP System Sevices are old, failing and should be disabled as they serve no real purpose and do not belong in a Vista SP2 system
HPHC_Scheduler 2.0.9.1  3/12/2007 11:54 AM<BR>HpqToaster 1.10.1.3 1/30/2007 2:58 PM<BR>hpwamain 3.0.5.1  3/1/2007 12:18 PM<BR>hpwuschd2 80.1.0.0 12/8/2008 2:50 PM

Go into System Services and disable them -
START | type services.msc

I see that you have Avira installed. I would get rid of it in favor of the free Microsoft Security Essentials that recently came out -

Avira Removal Tool --> http://dlpro.antivir...ol-win32-en.exe

MS Security Essentials --> http://www.microsoft...ity_Essentials/

Regards. . .

jcgriff2

`

<BR>Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339<BR>Debug session time: Sat Feb  6 14:00:40.070 2010 (GMT-5)<BR>System Uptime: 0 days 0:10:26.898<BR>BugCheck 4A, {75a0385e, 2, 0, fffffa600a5b8ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339<BR>Debug session time: Sat Feb  6 13:16:18.570 2010 (GMT-5)<BR>System Uptime: 0 days 0:02:18.414<BR>BugCheck 4A, {7527385e, 2, 0, fffffa6009f60ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339<BR>Debug session time: Wed Feb  3 20:00:04.322 2010 (GMT-5)<BR>System Uptime: 0 days 0:33:40.304<BR>BugCheck 4A, {7511385e, 2, 0, fffffa600a388ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Mon Oct 12 23:03:13.311 2009 (GMT-5)<BR>System Uptime: 0 days 0:01:53.155<BR>BugCheck 4A, {7573385e, 2, 0, fffffa6009eb0ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Mon Oct 12 23:00:40.278 2009 (GMT-5)<BR>System Uptime: 0 days 0:14:41.172<BR>BugCheck 4A, {7538385e, 2, 0, fffffa6009f34ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Mon Oct 12 18:53:56.937 2009 (GMT-5)<BR>System Uptime: 0 days 0:13:16.782<BR>BugCheck 4A, {757c385e, 2, 0, fffffa600a39cca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Sun Oct  4 14:47:26.894 2009 (GMT-5)<BR>System Uptime: 0 days 21:46:35.895<BR>BugCheck 9F, {3, fffffa8002811060, fffffa8003f58050, fffffa800aabc010}<BR>*** WARNING: Unable to verify timestamp for NETw4v64.sys<BR>*** ERROR: Module load completed but symbols could not be loaded for NETw4v64.sys<BR>Probably caused by : NETw4v64.sys<BR>BUGCHECK_STR:  0x9F<BR>PROCESS_NAME:  System<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Wed Sep 23 18:53:01.216 2009 (GMT-5)<BR>System Uptime: 0 days 0:08:12.044<BR>BugCheck 4A, {753a385e, 2, 0, fffffa600a5f3ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Wed Sep 23 18:43:42.610 2009 (GMT-5)<BR>System Uptime: 0 days 1:01:20.446<BR>BugCheck 4A, {7567385e, 2, 0, fffffa600989aca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Wed Sep 23 17:41:44.563 2009 (GMT-5)<BR>System Uptime: 0 days 0:01:29.282<BR>BugCheck 4A, {757f385e, 2, 0, fffffa600a7baca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Mon Sep 21 20:51:43.141 2009 (GMT-5)<BR>System Uptime: 0 days 0:24:54.004<BR>BugCheck 4A, {75c0385e, 2, 0, fffffa600a7d1ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Wed Sep 16 19:42:42.142 2009 (GMT-5)<BR>System Uptime: 0 days 0:16:36.972<BR>BugCheck 4A, {74f1385e, 2, 0, fffffa600a204ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Tue Sep 15 21:28:00.068 2009 (GMT-5)<BR>System Uptime: 0 days 0:37:59.900<BR>BugCheck 4A, {759c385e, 2, 0, fffffa6008dc6ca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Mon Sep 14 01:42:56.393 2009 (GMT-5)<BR>System Uptime: 0 days 1:10:59.246<BR>BugCheck 4A, {7597385e, 2, 0, fffffa600a73dca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Sun Sep 13 23:26:42.532 2009 (GMT-5)<BR>System Uptime: 0 days 0:22:47.362<BR>BugCheck 4A, {7505385e, 2, 0, fffffa600a9fcca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830<BR>Debug session time: Sun Sep 13 23:02:52.184 2009 (GMT-5)<BR>System Uptime: 0 days 0:26:31.031<BR>BugCheck 4A, {750c385e, 2, 0, fffffa600a34cca0}<BR>Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )<BR>PROCESS_NAME:  [color=red]vsmon.exe[/color]<BR>BUGCHECK_STR:  RAISED_IRQL_FAULT<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>by jcgriff2<BR>J. C. Griffith<BR>Microsoft MVP<BR>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ<BR>


.

Edited by jcgriff2, 07 February 2010 - 01:52 AM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP