BSOD! *grrr*

[icecreamsellah]

Ive been getting bsod errors,
they are so random its hard to put my finger on what it could be that causes it,
the first time i can remember it happening was when ive had the computer running for ~3 days and woke up with a bsod, and now the last time i went afk and came back to the screen saver login screen and clicked password field then BAM! BSOD. And one other time i was just messing around doing nothing really in windows and got bsod.

memory management, system service exception, apc index mismatch

Ive had memtest86+ running 10 passes and no errors
I have the bios RAM option set to manual using the RAM specs
Hdd is recently defragmented, and chkdsk reports no errors
I have no random external devices installed/plugged in
Windows update is fully updated, and all the win7 available drivers from ASUSTeK support download for my P5Q DELUXE has been installed

Using Panda AVPRO2009

Attaching DxDiag & Minidumps

Please help,
Thanks

System Manufacturer/Model Number
System manufacturer
OS
Windows 7 Ultimate 64-bit
CPU
Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz (2 CPUs), ~3
Motherboard
P5Q DELUXE
Memory
Corsair Dominator TWIN2X PC8500 4GB DDR2
Graphics Card(s)
NVIDIA GeForce GTX 260
Sound Card
SoundMAX Integrated Digital HD Audio
Monitor(s) Displays
SyncMaster 206BW (Digital)
Screen Resolution
N/A
Hard Drives
WD VelociRaptor WD3000HLFS - 300 GB - SATA-300
PSU
Corsair TX750W
Case
Antec Three Hundred - EU - tower - ATX
Cooling
Cooler Master Vortex 752 / x2 Case Fans + 1x ZALMAN ZM F3
Keyboard
Logitech G11
Mouse
Logitech MX518
Internet Speed
24/1 DSL
Other Info
N/A

 

[Dzomlija]

It's a long shot, but try resetting your BIOS to defaults. Particularly, the settings governing memory. See what happens then...

 

[icecreamsellah]

Ive already tried that, it didnt help :\

Also, just ran a Western Digital Lifeguard Diag and passed without problems on quick and extended tests

 

[Ex14]

were u running anysort of programs when the BSOD happen?

The only BSOD i got was when i tried playing a specific game...

 

[icecreamsellah]

Well.. yes, but as i said its random, i could get it while im ingame, or just running WLM/IE/WINAMP, and as with the most recent bsod, at the logon screen after screen saver,

 

[icecreamsellah]

Happened again

^^^

 

[usasma]

Articles about the APC_INDEX_MISMATCH error (it's odd to get this error):
BSOD links (link may change - it's my new website)
You receive a Stop error message on a Windows Vista-based computer: "Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000)"
Stop error message when you try to print content that includes a bitmap on a Windows Vista-based computer: "Stop 0x00000001"

Onto the dump files:
A quick look shows a lot of video involvement - most likely either driver issues, a program that you're running that has video issue, or a hardware problem (video or mobo).

There's a real mix of different BSOD's - so this is gonna take a bit to look at. Will be back with the results in a bit....

 

[usasma]

The first thing of note is the ASACPI.sys file that's dated from 2006 - this version is known to cause issues with Win7 and must be updated. It's present in all but 2 of the dump files - so it's a strong suspect for the cause. Here's a link to a topic that describes how to get the updated (Win7) version: Asus ASACPI.sys driver for Win7

Just as an aside, the P5 series of boards has seen more than it's fair share of issues with Win7. It appears to be very, very picky about drivers and you've gotta be very careful when installing anything (drivers or programs).

This "feels" like an incompatible program to me - but it's still possible that it could be a hardware issue (most likely with the video card). As mentioned before, there's a lot of video involvement - but this can be caused by an incompatible program issuing incompatible instructions.

Two things to do:
- Download and run the Windows 7 Upgrade Advisor (free here: http://www.microsoft.com/downloads/...90-7659-4BD9-9E51-2497C146AF15&displaylang=en ) and post the results in your next post.
- Go to Start and type in "msinfo32" (without the quotes) and press Enter. Save the report as an .nfo file, zip it up and upload it with your next post.

Summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 10 12:35:15.505 2009 (GMT-4)
System Uptime: 0 days 0:01:20.097
BugCheck D1, {fffff880009fb870, 2, 8, fffff880009fb870}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+14e9e0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 10 15:21:43.201 2009 (GMT-4)
System Uptime: 0 days 1:42:43.793
BugCheck 3B, {c0000005, fffff88004d949c3, fffff8800a1cc6a0, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+58c9c3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 10 17:49:15.640 2009 (GMT-4)
System Uptime: 0 days 2:26:37.232
BugCheck 10E, {1f, fffff8a0082e2b60, 0, ddc61f}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 10 13:17:28.948 2009 (GMT-4)
System Uptime: 0 days 0:41:18.540
BugCheck 1000007E, {ffffffffc0000005, fffff80002be8a31, fffff880029d3508, fffff880029d2d60}
Probably caused by : msrpc.sys ( msrpc!LRPC_FAST_BINDING_HANDLE::`scalar deleting destructor'+52 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 12:02:36.868 2009 (GMT-4)
System Uptime: 0 days 0:03:34.413
BugCheck 3B, {c0000005, fffff96000223546, fffff8800988a780, 0}
Probably caused by : win32k.sys ( win32k!NtGdiBitBltInternal+846 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 09:01:46.497 2009 (GMT-4)
System Uptime: 0 days 7:56:32.044
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  acclient.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 11:58:19.284 2009 (GMT-4)
System Uptime: 0 days 2:55:45.830
BugCheck 3B, {c0000005, fffff800028d6105, fffff880070c2f90, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 12:24:25.462 2009 (GMT-4)
System Uptime: 0 days 0:17:07.008
BugCheck 1A, {41201, fffff68000000d28, 89b000003b52c847, fffffa8006b89ac0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 12:28:19.973 2009 (GMT-4)
System Uptime: 0 days 0:01:06.378
BugCheck 1000007E, {ffffffffc0000096, fffff88003dc17f0, fffff88002bd7cb8, fffff88002bd7510}
Probably caused by : hardware ( dxgmms1!VidSchiSubmitCommandPacketToQueue+28 )
PROCESS_NAME:  csrss.exe
DEFAULT_BUCKET_ID:  STATUS_PRIVILEGED_INSTRUCTION
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 19:28:30.274 2009 (GMT-4)
System Uptime: 0 days 0:22:25.820
BugCheck 1, {776e17ba, 0, 1000000, fffff880092d7c60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 19:02:42.256 2009 (GMT-4)
System Uptime: 0 days 0:00:06.801
BugCheck 124, {0, fffffa8004c568f8, 0, 0}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 19:30:26.031 2009 (GMT-4)
System Uptime: 0 days 0:00:20.576
BugCheck 1000007E, {ffffffffc0000005, fffff800028dc4a7, fffff880037f5488, fffff880037f4ce0}
Probably caused by : cdd.dll ( cdd!PresentWorkerThread+532 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 13 19:03:05.841 2009 (GMT-4)
System Uptime: 0 days 0:00:30.387
BugCheck A, {48000002, c, 1, fffff800028e0fd6}
Probably caused by : ntkrnlmp.exe ( nt!KiIpiSendRequest+96 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Sep 15 03:20:10.857 2009 (GMT-4)
System Uptime: 0 days 0:13:35.262
BugCheck 3B, {c0000005, fffff88003d52bbc, fffff88007a560e0, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkGetPresentHistory+f0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep 14 21:09:52.108 2009 (GMT-4)
System Uptime: 0 days 14:50:14.653
BugCheck 1A, {5003, fffff70001080000, 3448, 344a00006810}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21bc6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe

 

[icecreamsellah]

Hi, thanks for looking into my case

I tried "Asus ASACPI.sys driver for Win7" but it doesnt work, just takes me back to Seven forum , not the post i think it was supposed to refer to

And the Windows 7 Upgrade Advisor Beta gives me "Windows 7 Upgrade Advisor was unable to reach the Microsoft server for compatibility information. Check your internet connection or see if there is a new version of Windows 7 Upgrade Advisor available" after clicking Start check, and my internet connection is working just fine

 

[icecreamsellah]

the link was missing the /general-discussion/
looking into it now

 

[icecreamsellah]

Ok,
ASUS AI Suite V1.05.29 for Windows 32/64bit XP & 32/64bit Vista & 32/64bit Windows 7 - Installed

btw i wasnt able to install the hotfix (http://support.microsoft.com/kb/935936) you referred me to, wasnt suitable for my system, however it described one of the situations where ive experienced bsod,

 

[adrift]

usasma may be onto something here, but I think it may be your RAM. Corsair RAM has been giving a lot of folks issues lately. I have their Ballistix RAM, and have had all sorts of BSODs with it, first randomly in Vista, then a bit more regularly in Windows 7. I'm not sure what it is about Windows 7 that makes it crash, but if you look at reviews on something like Newegg for later model versions of Corsair you'll see all types of folks complaining about their RAM crashing their OS's on them after about 6 to 9 months of use.

My RAM issues in Windows 7 always went sort of like this: After about 6 months of virtually no issues I'd have my PC powered on for a few days, and then, out of the blue, I'd get a BSOD. Typically this wouldn't even happen under load (though I would have a memory hogging Firefox window up for a couple days). I'd restart the PC without actually booting completely down, just going through the start menu and doing a soft restart there. I'd get another BSOD not long after... sometimes a few hours later. If I completely booted down, then booted back up, I'd be okay for another few days until it would start all over again. Running Memtest86+ I saw some very odd things. If I restarted my system into Memtest with a soft restart after a BSOD I'd see all types of memory errors. If I booted completely down and then booted into Memtest I'd see no memory errors. I thought this was totally bizarre and thought that maybe it wasn't the memory, but after doing a bit of online research this appears to be a common theme among folks having issues with Corsair.

Two solutions:
1.) Try swapping out the Corsair for another brand if you have anything laying around just to see if you still get the BSODs. This will help you confirm whether or not it really is the RAM. I did this with some slower OCZ RAM and found I had zero issues with BSODs.
2.) Corsair is very picky about the timings set in the BIOS. You said you have the timings already manually set, but you might want to experiment a little with the voltage. I had fewer issues with my default timing in Vista, but under Windows 7 I've experimented with the timings and voltage a bit and the system seems to be a bit more stable (knock on wood).

 

[chev65]

I agree with adrift, that particular Ram can be a real pain to get stable. It might be a good idea to try and run a stablity program like Prime Blend to see if the problem shows up. If it shows to be unstable then some voltage adjustments in bios might help. The Auto voltage settings very often just aren't good enough.

 

[akatarmo]

Hi, see this thread, I have found a solution after searching a long time (at least works for me):

http://www.sevenforums.com/general-discussion/8822-mystery-problem-resume-sleep-3.html

Post #26

Regards

 

[jfar]

Hi, why did you install this program, if you dont mind me asking you,

ASUS AI Suite V1.05.29 for Windows 32/64bit XP & 32/64bit Vista & 32/64bit Windows 7 - Installed

 

[usasma]

Something seems to happen when the forum software "simplifies" the link. Here's the text version:

http://www.sevenforums.com/general-discussion/14477-contast-bsods-2.html#post157051

 

[usasma]

jfar - The file ASACPI.SYS from his BSOD file was dated from 2006. That version of the file is a Windows Vista version and it's known to have issues with Windows 7.

The program that installed it is most likely the Asus AISuite - but there's other Asus tools that seem to use it. So the safest thing was to install the AISuite - which will update the driver to a 2008/9 version (which doesn't have any known issues with Win7)

 

[usasma]

Now that the file is installed - sit back and wait for another BSOD.

If you don't get one in the next 24 hours, there's hope that we may have fixed it.
If you don't get one in the next 3 days, then it's probably, hopefully, most likely, etc that we've fixed it.
If you don't get one in the next week, then it's most likely that we have fixed it - and it probably ain't worth worrying about anymore!

Good luck!

 

[jfar]

jfar - The fileASACPI.SYS from his BSOD file was dated from 2006. That version of the file is a Windows Vista version and it's known to have issues with Windows 7.

The program that installed it is most likely the Asus AISuite - but there's other Asus tools that seem to use it. So the safest thing was to install the AISuite - which will update the driver to a 2008/9 version (which doesn't have any known issues with Win7)

Thanks, I just didn't see where that suddenly came up from, and I was going to recommend to the OP NOT to install it because of what you said.

 

[icecreamsellah]

Again!

Ive had my computer running through the night, woke up, was fine for like 4 hours then bam bsod, did a soft restart and immediately after entering windows i got another bsod,

My RAM issues in Windows 7 always went sort of like this: After about 6 months of virtually no issues I'd have my PC powered on for a few days, and then, out of the blue, I'd get a BSOD. Typically this wouldn't even happen under load (though I would have a memory hogging Firefox window up for a couple days). I'd restart the PC without actually booting completely down, just going through the start menu and doing a soft restart there. I'd get another BSOD not long after... sometimes a few hours later. If I completely booted down, then booted back up, I'd be okay for another few days until it would start all over again. Running Memtest86+ I saw some very odd things. If I restarted my system into Memtest with a soft restart after a BSOD I'd see all types of memory errors. If I booted completely down and then booted into Memtest I'd see no memory errors. I thought this was totally bizarre and thought that maybe it wasn't the memory, but after doing a bit of online research this appears to be a common theme among folks having issues with Corsair.

And yes adrift! that is exactly my problem, if i run memtest86+ directly after getting a bsod and doing a restart without shutting power off completely i get like 5k+ errors, and if i reboot like 5 times or turn off the power completely i get no errors at all, ive changed the settings a bit now and im going to try it out, unfortunately i have no other ram available to tests it out :\
Think i should keep on tweaking this ram or simply just return it for another brand/type or the same memory?

But what causes this type of error? is this a hardware ram problem or is it just the settings?

Attaching the dumps