Sign in with
Sign up | Sign in
Your question
Solved

New Parts BSOD

Last response: in Windows 7
Share
May 6, 2013 11:28:18 AM

Hi,
I've recently change some parts of my PC:

Asrock Z77 Extreme4
i5 3570K
2x4GB Adata 1600 MHz cl9

My gpu is MSI GTX 660, PSU is BeQuiet 450W

Since then i'm having bsod's.
I've checked with 3 different version sets of drivers,
checked my memory with memtest - 8 passes no erros,
switched slots of my ddr3 and gpu
ran driver verifier - showed blue screen with my mouse drivers - I removed it but still didn't help.

What could be the reason ? I'm helpless.

Here is zip with all the minidumps sicne last windows reinstall:
https://docs.google.com/file/d/0BzZzjdmJquKYSmJ1NnIzdnd...

More about : parts bsod

a b $ Windows 7
a b \ Driver
May 6, 2013 1:17:49 PM

So you have a new MB... Did you do a fresh install of windows for that new MB?
m
0
l
May 6, 2013 1:40:02 PM

few, with different drivers
m
0
l
Related resources
May 11, 2013 1:57:40 AM

So i did all that. I was running verifier for few hours with runing game watchign stream and some other program in background. Nothing happened. So i turned it off, and when i was playing game next day - bsod.
Here are some more dumps:
https://docs.google.com/file/d/0BzZzjdmJquKYWnZLRDRjREt...
Could it be PSU ? Or ddr anyway although it went through 8 passes ? Should I run it again ?

Edit:
I also noticed that when i play game they crash a lot, and when they crash theres usually some corrupted file so they require reinstall or using some repair tool. Sometimes they freeze for split second like about to crash or bsod.
m
0
l
May 11, 2013 2:49:35 AM

Driver Verifier really needs to be run for 24-48 hours, or at least across several session - but - we may have the culprit.

There was 1x Driver Verified crash, it pointed to the Lachesis.sys driver:
Fri Oct 16 14:09:12 2009 (4AD87078)
Razer Lachesis Mouse driver
http://www.carrona.org/drivers/driver.php?id=Lachesis.sys

Update the Razer drivers if you can (they don't update very often), if there's no update, uninstall it from Device Manager, when it asks about deleting the drivers, select to delete them. Disconnect the mouse and reconnect it, this time, only install it as a standard mouse.

Then turn DV back on and test again.
m
0
l
May 11, 2013 3:12:40 AM

I did update, it was newest. Reinstalled it, its still the same so i just removed it.
m
0
l
a b $ Windows 7
a b \ Driver
May 11, 2013 8:44:02 AM

Quote:
Did you do a fresh install of windows for that new MB?

m
0
l
May 12, 2013 5:04:23 PM

Yes, it does look like the crash was blamed on the nVidia drivers, however, the Lachesis.sys driver could well be the trigger (mouse drivers are tied into the graphics or there'd be no cursor onscreen interaction); also the DaemonTools drivers are still there, they can cause very strange effects.

Turn off Driver Verifier, uninstall the Lachesis (test with a standard mouse for a few days), uninstall DaemonTools completely, reinstall (or install a different version of) the nVidia drivers. Then turn DV back on, test for 1-2 days; try to collect 3x DV verified dumps.


intelppm.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
Intel Processor driver
http://www.carrona.org/drivers/driver.php?id=intelppm.sys

MBfilt64.sys Fri Jul 31 04:40:32 2009 (4A7267B0)
Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys

Lachesis.sys Fri Oct 16 14:09:12 2009 (4AD87078)
Razer Lachesis Mouse driver
http://www.carrona.org/drivers/driver.php?id=Lachesis.sys

amdxata.sys Fri Mar 19 16:18:18 2010 (4BA3A3CA)
AMD storage controller driver - usually from the Windows 7 DVD
http://www.carrona.org/drivers/driver.php?id=amdxata.sys

asmtxhci.sys Fri Mar 4 07:54:59 2011 (4D709AD3)
Asmedia USB 3.0 driver
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys

asmthub3.sys Fri Mar 4 07:55:10 2011 (4D709ADE)
ASMedia USB 3.0 Hub driver
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys

k57nd60a.sys Tue May 10 05:42:30 2011 (4DC8C236)
Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver
http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys

asahci64.sys Wed Sep 21 10:42:57 2011 (4E79B1A1)
Asmedia 106x SATA Host Controller Driver
http://www.carrona.org/drivers/driver.php?id=asahci64.sys

RTKVHD64.sys Tue Jan 31 10:55:06 2012 (4F27C88A)
Realtek High Definition Audio Function Driver
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys

iusb3hub.sys Mon Feb 27 10:56:50 2012 (4F4B6172)
Intel(R) USB 3.0 Hub Driver
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys

iusb3xhc.sys Mon Feb 27 10:56:53 2012 (4F4B6175)
Intel(R) USB 3.0 eXtensible Host Controller Driver
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys

iusb3hcs.sys Mon Feb 27 10:58:49 2012 (4F4B61E9)
Intel(R) USB 3.0 Host Controller Switch Driver
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys

IntcDAud.sys Tue Jun 19 15:40:51 2012 (4FE08F73)
Intel Graphics Media Accelerator HD Driver
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys

HECIx64.sys Mon Jul 2 23:14:58 2012 (4FF21D62)
Intel Management Engine Interface
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys

sptd.sys Sat Aug 18 22:05:38 2012 (503003A2)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
http://www.carrona.org/drivers/driver.php?id=sptd.sys

MpFilter.sys Wed Oct 31 22:43:06 2012 (5091A97A)
Microsoft Windows AntiMalware protection system
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys

igdkmd64.sys Thu Dec 13 00:42:26 2012 (50C92472)
Intel Graphics driver
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys

nvhda64v.sys Wed Dec 19 05:41:41 2012 (50D15395)
nVidia HDMI Audio Device (nForce chipset driver)
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys

HWiNFO64A.SYS Sat Jan 26 12:28:11 2013 (5103CBDB)
HWiNFO32 Kernel Driver
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS

nvlddmkm.sys Fri Mar 15 01:37:00 2013 (51427B3C)
nVidia Video drivers
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys

RzFilter.sys Wed May 1 01:47:49 2013 (51806635)

RzFilter.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

RzDxgk.sys Wed May 1 01:47:51 2013 (51806637)

RzDxgk.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

BSOD BUGCHECK SUMMARY
  1. System Uptime: 0 days 1:11:10.059
  2. *** WARNING: Unable to verify timestamp for nvlddmkm.sys
  3. *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
  4. Probably caused by : nvlddmkm.sys ( nvlddmkm+19c62d )
  5. BugCheck D6, {fffff980546b7ba8, 1, fffff88004bcb62d, 0}
  6. BugCheck Info: [urlExt=http://www.carrona.org/bsodindx.html#0x000000D6]DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)[/urlExt]
  7. Bugcheck code 000000d6
  8. Arguments:
  9. Arg1: fffff980546b7ba8, memory referenced
  10. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation
  11. Arg3: fffff88004bcb62d, if non-zero, the address which referenced memory.
  12. Arg4: 0000000000000000, (reserved)
  13. BUGCHECK_STR: 0xD6
  14. DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
  15. PROCESS_NAME: dota.exe
  16. FAILURE_BUCKET_ID: X64_0xD6_VRF_nvlddmkm+19c62d
  17. MaxSpeed: 3400
  18. CurrentSpeed: 3400
  19. BiosVersion = P2.80
  20. BiosReleaseDate = 01/17/2013[/font]
m
0
l
May 13, 2013 1:07:53 AM

Ok, I uninstalled sptd, but when I uninstall Lachesis the Lachesis.sys is still there. When i remove it manually then my mouse doesnt work, even if I unplug and plug in again. So no idea how to remove it.
m
0
l
May 13, 2013 1:21:13 AM

First get hold of a standard mouse for testing with then connect it, remove the Lachesis and uninstall it. Go to Device Manager > View > Show hidden devices and look for it in the Non-Plug and Play section and uninstall it from there, you should get a pop up asking if you also want to remove the drivers for it, choose yes/ok to that.

Have you updated/switched graphics drivers yet, just in case they were buggy?
m
0
l
May 13, 2013 1:53:45 AM

Ive installed other version of graphics drivers, but there is no lachesis in the Non-Plug and Play section.

UPDATE: I've found lachesis under HID section and deleted it.
m
0
l
May 13, 2013 2:02:04 AM

Try renaming it to Lachesis.old from Safe Mode.

Reply to Update: Good work!
m
0
l
May 13, 2013 3:57:15 PM

This dump was a 0x1A Memory Management, that's usually caused by a driver, bad memory/slot or, very rarely, kernel. I don't see any further clues; can you carefully read and follow the Sticky here please:http://www.sysnative.com/forums/bsod-crashes-kernel-deb... and upload the required zipped folder?

With some extra details, it should be easier to get an overview of what's happening.
m
0
l
May 14, 2013 9:48:55 AM

I can see nothing conclusive; there's 1 unknown device in Device Manager, that looks like Intel Smart Connect, you could install that for completeness.

Windows Error Reporting does flag application crashes from Razercore.exe in the moments before some of the BSODs, I would remove both the remaining Razer software then continue testing with Driver Verifier.
m
0
l
May 14, 2013 10:01:57 AM

razercore is razer comms - communication software it crashed first time probably caused by some other bsod that corrupted its files. I reinstalled it.
m
0
l
May 14, 2013 10:15:20 AM

Last time Razercore crashed was 2013-05-13 13:48, uninstall it during testing is best, there are no Razer mouse drivers listed now so nothing for it to interact with.
m
0
l
May 17, 2013 2:47:32 AM

The latest crash was a 0x1A, frequently caused by a device driver or memory. The drivers look recent with no known 'bad' ones but there's a question mark hanging over the most recent ones - from Razer, by the look of the file names. Uninstall the software that relates to these drivers.

The next stage would be to rule out bad memory/slots, MemTest86+ for at least 7+ runs on each individual stick is best. Do this overnight or while you are away at work or sleeping is best, it takes a long time. Details here: http://www.carrona.org/memdiag.html sections #2 and 7-10.

  1. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
  2. Product: WinNt, suite: TerminalServer SingleUserTS
  3. Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
  4. Machine Name:
  5. Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03250670
  6. Debug session time: Fri May 17 08:53:24.729 2013 (GMT+1)
  7. System Uptime: 0 days 0:42:29.572
  8. Loading Kernel Symbols
  9. ...............................................................
  10. ................................................................
  11. .........................
  12. Loading User Symbols
  13. Loading unloaded module list
  14. .....
  15. *******************************************************************************
  16. * *
  17. * Bugcheck Analysis *
  18. * *
  19. *******************************************************************************
  20.  
  21. Use !analyze -v to get detailed debugging information.
  22.  
  23. BugCheck 1A, {41790, fffffa8000cd8f60, ffff, 0}
  24.  
  25. Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
  26.  
  27. Followup: MachineOwner
  28. ---------
  29.  
  30. 1: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
  31. *******************************************************************************
  32. * *
  33. * Bugcheck Analysis *
  34. * *
  35. *******************************************************************************
  36.  
  37. MEMORY_MANAGEMENT (1a)
  38. # Any other values for parameter 1 must be individually examined.
  39. Arguments:
  40. Arg1: 0000000000041790, The subtype of the bugcheck.
  41. Arg2: fffffa8000cd8f60
  42. Arg3: 000000000000ffff
  43. Arg4: 0000000000000000
  44.  
  45. Debugging Details:
  46. ------------------
  47.  
  48.  
  49. BUGCHECK_STR: 0x1a_41790
  50.  
  51. CUSTOMER_CRASH_COUNT: 1
  52.  
  53. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  54.  
  55. PROCESS_NAME: opera.exe
  56.  
  57. CURRENT_IRQL: 0
  58.  
  59. LAST_CONTROL_TRANSFER: from fffff800030f2e10 to fffff80003081c40
  60.  
  61. STACK_TEXT:
  62. fffff880`0a5594b8 fffff800`030f2e10 : 00000000`0000001a 00000000`00041790 fffffa80`00cd8f60 00000000`0000ffff : nt!KeBugCheckEx
  63. fffff880`0a5594c0 fffff800`0306e42f : fffffa80`00000000 00000000`3c79ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
  64. fffff880`0a559680 fffff800`03080ed3 : ffffffff`ffffffff fffff880`0a559950 fffff880`0a559958 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
  65. fffff880`0a559780 fffff800`0307d490 : fffff800`03303fdb 00000000`00000010 00000000`00000082 fffff880`0a559948 : nt!KiSystemServiceCopyEnd+0x13
  66. fffff880`0a559918 fffff800`03303fdb : 00000000`00000010 00000000`00000082 fffff880`0a559948 00000000`00000000 : nt!KiServiceLinkage
  67. fffff880`0a559920 fffff800`0335a0cd : 00000000`3c6a0000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlFreeUserStack+0x27
  68. fffff880`0a559950 fffff800`0335a42d : fffff880`00000000 00000000`2fdae100 00000000`fff1a000 00000000`00000000 : nt!PspExitThread+0x5dd
  69. fffff880`0a559a50 fffff800`0335a535 : fffffa80`0b144060 00000000`00000000 fffffa80`0b144060 00000000`fff1a000 : nt!PspTerminateThreadByPointer+0x4d
  70. fffff880`0a559aa0 fffff800`03080ed3 : 00000000`00000008 fffff880`0a559b60 00000000`fff1a000 00000000`0be9faf0 : nt!NtTerminateThread+0x45
  71. fffff880`0a559ae0 00000000`76d8184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
  72. 00000000`2fdae1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d8184a
  73.  
  74.  
  75. STACK_COMMAND: kb
  76.  
  77. FOLLOWUP_IP:
  78. nt! ?? ::FNODOBFM::`string'+35084
  79. fffff800`030f2e10 cc int 3
  80.  
  81. SYMBOL_STACK_INDEX: 1
  82.  
  83. SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+35084
  84.  
  85. FOLLOWUP_NAME: MachineOwner
  86.  
  87. MODULE_NAME: nt
  88.  
  89. IMAGE_NAME: ntkrnlmp.exe
  90.  
  91. DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935
  92.  
  93. FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
  94.  
  95. BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
3rd party driver list:

  1. HECIx64.sys Mon Jul 2 23:14:58 2012 (4FF21D62)
  2. HWiNFO64A.SYS Sat Jan 26 12:28:11 2013 (5103CBDB)
  3. IntcDAud.sys Tue Jun 19 15:40:51 2012 (4FE08F73)
  4. MBfilt64.sys Fri Jul 31 04:40:32 2009 (4A7267B0)
  5. MpFilter.sys Wed Oct 31 22:43:06 2012 (5091A97A)
  6. RTKVHD64.sys Tue Jan 31 10:55:06 2012 (4F27C88A)
  7. RzDxgk.sys Wed May 1 01:47:51 2013 (51806637)
  8. RzFilter.sys Wed May 1 01:47:49 2013 (51806635)
  9. amdxata.sys Fri Mar 19 16:18:18 2010 (4BA3A3CA)
  10. asahci64.sys Wed Sep 21 10:42:57 2011 (4E79B1A1)
  11. asmthub3.sys Fri Mar 4 07:55:10 2011 (4D709ADE)
  12. asmtxhci.sys Fri Mar 4 07:54:59 2011 (4D709AD3)
  13. igdkmd64.sys Thu Dec 13 00:42:26 2012 (50C92472)
  14. intelppm.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
  15. iusb3hcs.sys Mon Feb 27 10:58:49 2012 (4F4B61E9)
  16. iusb3hub.sys Mon Feb 27 10:56:50 2012 (4F4B6172)
  17. iusb3xhc.sys Mon Feb 27 10:56:53 2012 (4F4B6175)
  18. k57nd60a.sys Tue May 10 05:42:30 2011 (4DC8C236)
  19. nvhda64v.sys Wed Dec 19 05:41:41 2012 (50D15395)
  20. nvlddmkm.sys Fri Mar 15 01:37:00 2013 (51427B3C)


m
0
l
May 17, 2013 4:05:42 AM

I did test memory and slots - 8 passes on memtest with no errors
m
0
l
May 19, 2013 12:40:09 AM

The latest dump was a 0xBE, usually drivers or memory.

Your drivers are now looking pretty good but there could be updates available for your hardware drivers, also there are many more recent versions of HWInfo.

You could turn on Driver Verifier on 3rd party drivers to try to flush out any bad driver, info here: http://www.sysnative.com/forums/showthread.php/29-Drive...

BSOD BUGCHECK SUMMARY
Debug session time: Sat May 18 10:59:01.089 2013 (GMT+1)
System Uptime: 0 days 2:53:18.323
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44cde )
BugCheck BE, {fffff8a003fa8767, 80000001951e3121, fffff88009d221f0, b}
BugCheck Info: ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
Bugcheck code 000000bE
Arguments:
Arg1: fffff8a003fa8767, Virtual address for the attempted write.
Arg2: 80000001951e3121, PTE contents.
Arg3: fffff88009d221f0, (reserved)
Arg4: 000000000000000b, (reserved)
BUGCHECK_STR: 0xBE
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: GameOverlayUI.
FAILURE_BUCKET_ID: X64_0xBE_nt!_??_::FNODOBFM::_string_+44cde
MaxSpeed: 3400
CurrentSpeed: 3400
BiosVersion = P2.80
BiosReleaseDate = 01/17/2013

3rd party drivers loaded:

intelppm.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD)
Intel Processor driver
http://www.carrona.org/drivers/driver.php?id=intelppm.sys

MBfilt64.sys Fri Jul 31 04:40:32 2009 (4A7267B0)
Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys

amdxata.sys Fri Mar 19 16:18:18 2010 (4BA3A3CA)
AMD storage controller driver - usually from the Windows 7 DVD
http://www.carrona.org/drivers/driver.php?id=amdxata.sys

asmtxhci.sys Fri Mar 4 07:54:59 2011 (4D709AD3)
Asmedia USB 3.0 driver
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys

asmthub3.sys Fri Mar 4 07:55:10 2011 (4D709ADE)
ASMedia USB 3.0 Hub driver
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys

k57nd60a.sys Tue May 10 05:42:30 2011 (4DC8C236)
Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver
http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys

asahci64.sys Wed Sep 21 10:42:57 2011 (4E79B1A1)
Asmedia 106x SATA Host Controller Driver
http://www.carrona.org/drivers/driver.php?id=asahci64.sys

RTKVHD64.sys Tue Jan 31 10:55:06 2012 (4F27C88A)
Realtek High Definition Audio Function Driver
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys

iusb3hub.sys Mon Feb 27 10:56:50 2012 (4F4B6172)
Intel(R) USB 3.0 Hub Driver
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys

iusb3xhc.sys Mon Feb 27 10:56:53 2012 (4F4B6175)
Intel(R) USB 3.0 eXtensible Host Controller Driver
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys

iusb3hcs.sys Mon Feb 27 10:58:49 2012 (4F4B61E9)
Intel(R) USB 3.0 Host Controller Switch Driver
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys

IntcDAud.sys Tue Jun 19 15:40:51 2012 (4FE08F73)
Intel Graphics Media Accelerator HD Driver
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys

HECIx64.sys Mon Jul 2 23:14:58 2012 (4FF21D62)
Intel Management Engine Interface
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys

MpFilter.sys Wed Oct 31 22:43:06 2012 (5091A97A)
Microsoft Windows AntiMalware protection system
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys

igdkmd64.sys Thu Dec 13 00:42:26 2012 (50C92472)
Intel Graphics driver
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys

nvhda64v.sys Wed Dec 19 05:41:41 2012 (50D15395)
nVidia HDMI Audio Device (nForce chipset driver)
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys

HWiNFO64A.SYS Sat Jan 26 12:28:11 2013 (5103CBDB)
HWiNFO32 Kernel Driver
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS

nvlddmkm.sys Fri Mar 15 01:37:00 2013 (51427B3C)
nVidia Video drivers
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
m
0
l
May 19, 2013 3:01:30 AM

this is what i got from 'verifier /query':

Quote:
Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.

C:\Users\qalix>verifier /query
2013-05-19, 11:58:11
Poziom: 0000092B
RaiseIrqls: 0
AcquireSpinLocks: 112476
SynchronizeExecutions: 69
AllocationsAttempted: 58686
AllocationsSucceeded: 58686
AllocationsSucceededSpecialPool: 58686
AllocationsWithNoTag: 37
AllocationsFailed: 0
AllocationsFailedDeliberately: 0
Trims: 75024
UnTrackedPool: 1

Zweryfikowane sterowniki:

Nazwa: iusb3hcs.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Nazwa: asahci64.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Nazwa: amdxata.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Nazwa: serial.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 5
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 7
PeakNonPagedPoolAllocations: 2
PagedPoolUsageInBytes: 256
NonPagedPoolUsageInBytes: 32
PeakPagedPoolUsageInBytes: 1088
PeakNonPagedPoolUsageInBytes: 4144

Nazwa: hwinfo64a.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Nazwa: nvlddmkm.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 122
CurrentNonPagedPoolAllocations: 5847
PeakPagedPoolAllocations: 140
PeakNonPagedPoolAllocations: 5864
PagedPoolUsageInBytes: 804844
NonPagedPoolUsageInBytes: 7200548
PeakPagedPoolUsageInBytes: 1915036
PeakNonPagedPoolUsageInBytes: 7203036

Nazwa: igdkmd64.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 11
CurrentNonPagedPoolAllocations: 1097
PeakPagedPoolAllocations: 13
PeakNonPagedPoolAllocations: 1104
PagedPoolUsageInBytes: 2376328
NonPagedPoolUsageInBytes: 4730912
PeakPagedPoolUsageInBytes: 2380440
PeakNonPagedPoolUsageInBytes: 4732924

Nazwa: iusb3xhc.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 4
CurrentNonPagedPoolAllocations: 262
PeakPagedPoolAllocations: 5
PeakNonPagedPoolAllocations: 265
PagedPoolUsageInBytes: 484
NonPagedPoolUsageInBytes: 620876
PeakPagedPoolUsageInBytes: 528
PeakNonPagedPoolUsageInBytes: 690444

Nazwa: hecix64.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 2
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 4
PagedPoolUsageInBytes: 112
NonPagedPoolUsageInBytes: 240
PeakPagedPoolUsageInBytes: 112
PeakNonPagedPoolUsageInBytes: 852

Nazwa: k57nd60a.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 3
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 3
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 516240
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 516240

Nazwa: ndis.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 6
CurrentNonPagedPoolAllocations: 954
PeakPagedPoolAllocations: 8
PeakNonPagedPoolAllocations: 982
PagedPoolUsageInBytes: 984
NonPagedPoolUsageInBytes: 731048
PeakPagedPoolUsageInBytes: 1296
PeakNonPagedPoolUsageInBytes: 756368

Nazwa: asmtxhci.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 178
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 185
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 455684
PeakPagedPoolUsageInBytes: 288
PeakNonPagedPoolUsageInBytes: 456796

Nazwa: nvhda64v.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 16
CurrentNonPagedPoolAllocations: 42
PeakPagedPoolAllocations: 17
PeakNonPagedPoolAllocations: 42
PagedPoolUsageInBytes: 10048
NonPagedPoolUsageInBytes: 26616
PeakPagedPoolUsageInBytes: 10068
PeakNonPagedPoolUsageInBytes: 26616

Nazwa: iusb3hub.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 3
CurrentNonPagedPoolAllocations: 13
PeakPagedPoolAllocations: 5
PeakNonPagedPoolAllocations: 14
PagedPoolUsageInBytes: 8340
NonPagedPoolUsageInBytes: 2056
PeakPagedPoolUsageInBytes: 9956
PeakNonPagedPoolUsageInBytes: 2220

Nazwa: rtkvhd64.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1190
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 1191
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 1394316
PeakPagedPoolUsageInBytes: 233056
PeakNonPagedPoolUsageInBytes: 1394332

Nazwa: mbfilt64.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 144
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 144

Nazwa: intcdaud.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 35
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 37
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 17000
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 22128

Nazwa: asmthub3.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 70
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 73
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 62996
PeakPagedPoolUsageInBytes: 128
PeakNonPagedPoolUsageInBytes: 63324

Nazwa: dump_dumpata.sys ładowania: 0, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Nazwa: dump_msahci.sys ładowania: 2, usunięcia: 1.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Nazwa: dump_dumpfve.sys ładowania: 2, usunięcia: 1.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 16400
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 16400

Nazwa: atmfd.dll ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Nazwa: secdrv.sys ładowania: 1, usunięcia: 0.
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 72
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 316
PeakNonPagedPoolUsageInBytes: 0
m
0
l
May 19, 2013 3:18:33 AM

Study the page again:
Spoiler
DRIVER VERIFIER
Windows 8, Windows 7, Vista

If your BSODs are software related, Driver Verifier can help by subjecting 3rd party drivers to a variety of stresses and tests to find improper behavior. Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system.

If Driver Verifier detects a violation, it will flag (disable) the offending driver and force a BSOD. The additional info added to the memory dump file will hopefully yield clues.

1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"

2. Run Driver Verifier -
START | type verifier | make these selections -
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
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ 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 you are unable to boot into normal Windows after VERIFIER_ENABLED BSOD -
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1

To check Driver Verifier status -
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot


- Driver Verifier needs to run for 24 hours minimum - even if the status screen appears clear.

If a VERIFIER_ENABLED BSOD occurs, please get the dump file from c:\windows\minidump, zip it up & attach to your next post.
m
0
l
May 20, 2013 12:59:08 AM

There was no driver flagged in that dump, that usually means a hardware error.

Run MemTest86+ on each stick individually in Slot #1 for 7+ passes, if they both pass, test one of the sticks in each of the remaing slots individually for a further 7+ passes.

Check your RAM settings for compatibility.

Run hard drive diags: http://www.carrona.org/hddiag.html
m
0
l
a b $ Windows 7
May 20, 2013 1:54:01 AM

Honestly, I'm not going to read through all of that, could you please verify what model is your MSI GTX 660, there are 5 different models.
http://www.msi.com/product/vga/#?fp=GeForce 600 Series&sk=Geforce GTX 660

Assuming general Nvidia references, the Nvidia GTX 660 requires a 450 watt PSU and 1 x 6-pin power connector.
What model type is your PSU, there are 2 different ones for the 450 watt Be Quiet brand - Straight Power and System Power.
http://www.bequiet.com/en/powersupply/328

Also, Your OS install is in German so you'd need to install drivers that were also German location, perhaps. What is your OS version?

The German version of Windows 7 does not include Internet Explorer, is that your version?

m
0
l
May 20, 2013 2:40:23 AM

My friend has same setup - CPU, mobo and ddr so it should be compatible. I'm just gonna run that memtest for each stick individually.

EDIT:
My GPU is: N660-2GD5/OC [link]
PSU: Straight Power(E6) 450W [link]

and i was running that GPU with that PSU before i changed mobo CPU and ddr and there was no bsod.

My OS is in polish and its Windows 7 Professional Sp1 x64 - it does include IE
m
0
l
a b $ Windows 7
May 20, 2013 4:38:51 AM

Thank you for adding the details. Sorry about the German reference, I should have looked more closely at the language. I was in a bit of a hurry, the Be Quiet site that gives the lists of PSU's and all their specs, has a long running script that really bogs down my system and I thought I'd lose my browser!

When you do your updates, do you select Polish language?
Do you update from the MSI site or the Nvidia site for the video card?

Motherboard -
http://www.asrock.com/mb/Intel/Z77%20Extreme4/?cat=Spec...


You do realise that if you use the same hdd with another motherboard, the chipset has to be the same?
If the new motherboard is an earlier version to the one it replaced then the chipsets might be different.

What was the brand / model of the replaced motherboard?
m
0
l
May 20, 2013 7:36:15 AM

I update video card from nvidia site.
My previous mobo was MSI EP45-DS3L - but i did reinstall windows after i changed mobo.
m
0
l
a b $ Windows 7
May 20, 2013 3:38:07 PM

Sometimes distributors of Nvidia products tweak the gpu for a slight different setting, you might want to consider updating directly fronm the MSI site. One would assume that any tweaking would not inmpact on the drivers themselves but clock ratios might be different and settings may cause some sort of issue. Nvidia do get quite disgruntled when distributors tweak preset settings so there must be a reason as to why they would feel "disgruntled".

"The Drivers provided here are exclusively for MSI products only." Why only MSI? Do they include something that is not included with Nvidia drivers for the same product?
MSI Graphics Driver 306.97
http://www.msi.com/product/vga/N660-2GD5-OC.html#/?div=...

Have you done any Windows updates?

Edit -
Bug Check - "Probably caused by : nvlddmkm.sys" - this is a Vista Nvidia driver....
m
0
l
May 21, 2013 4:30:11 AM

I'm doing updates quiet regularly.
There are many other bsod's cause by lots of different things so its not conclusive
m
0
l
a b $ Windows 7
May 21, 2013 12:57:14 PM

It is never anything conclusive, you could fix one error then another error will result.
Update from the MSI site, not from Nvidia. MSI drivers can only be used with MSI products, have you ever wondered why that is so if they are the "same" as Nvidia drivers?

If your friend has the same parts then go ask him what drivers he updates and from what provider.
m
0
l
May 22, 2013 10:45:55 AM

This dump is Driver Verified but no 3rd party driver was flagged, this usually points to hardware.

The bugcheck type was 0x77 KERNEL_STACK_INPAGE_ERROR:
Quote:
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware
So the most likely offender is somewhere between the disk controller and the data on the drive, probably a bad block in the paging file.

Turn off Driver Verifier: verifier /reset.

Remove the paging file, reboot and run chkdsk /r /f and allow the machine to reboot again to complete the disk check. Create a new paging file and check the System/Application logs for details of the chkdsk findings/repairs.

Spoiler
2: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 0000000000000000, (page was retrieved from page cache)
Arg2: fffffa8007fae0a0, value found in stack where signature should be
Arg3: 0000000000000000, 0
Arg4: fffff8800ae347c0, address of signature on kernel stack

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x77_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000334e551 to fffff800032c9c00

STACK_TEXT:
fffff880`033b0a18 fffff800`0334e551 : 00000000`00000077 00000000`00000000 fffffa80`07fae0a0 00000000`00000000 : nt!KeBugCheckEx
fffff880`033b0a20 fffff800`032fd8d0 : fffffa80`07fae6a0 00000000`00000000 fffffa80`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x51e71
fffff880`033b0b30 fffff800`032fd85f : 00000000`00000000 00000000`00000001 fffffa80`069fb9e0 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`033b0b90 fffff800`032fd5a4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`069fb900 : nt!KiInSwapKernelStacks+0x1f
fffff880`033b0bc0 fffff800`03567ede : 6473dbae`561889de 22ed0bb3`9bb708c6 4d71c749`a23172fa d240bf0c`e4567817 : nt!KeSwapProcessOrStack+0x84
fffff880`033b0c00 fffff800`032ba906 : fffff880`02f65180 fffffa80`07252040 fffff880`02f6ffc0 fd1e8454`49caddd8 : nt!PspSystemThreadStartup+0x5a
fffff880`033b0c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+51e71
fffff800`0334e551 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+51e71

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6

FAILURE_BUCKET_ID: X64_0x77_0_VRF_nt!_??_::FNODOBFM::_string_+51e71

BUCKET_ID: X64_0x77_0_VRF_nt!_??_::FNODOBFM::_string_+51e71

Followup: MachineOwner
m
0
l
May 23, 2013 1:15:32 AM

Did that. Chkdsk haven't found anything.

EDIT:
Got another BSOD but there was no dump - file that caused it was dxgmms1.sys
m
0
l
a b $ Windows 7
May 23, 2013 12:01:21 PM

dxgmms1.sys refers to Directx, lots of people have been having issues with Directx and have oinly resoned it by re-installing Directx. Some games install their own version of Directx during installation, sometimes asking for permission first but may other games do it automatically.

Re-install Directx
m
0
l
May 23, 2013 2:46:30 PM

how do you reinstall directx ?
m
0
l
May 24, 2013 5:10:02 AM

If the problem is bad hardware (as indicated in http://www.tomshardware.co.uk/answers/id-1669820/parts-... ), no amount of replacing files/drivers etc. will fix it. Try a new/known good hard drive and a fresh Windows install - if, after several sessions (days), you have no BSOD problems, begin importing your old data over by connecting the old drive as a slave (D: or E: ).
m
0
l

Best solution

May 26, 2013 7:24:56 PM

I placed this on another post. Thought it might help. I chased Direct X and software problems for 2 months. Today I found the issue. Considering you moved stuff around I think you had the same problem as me. Hope the following helps:
-------------------------------------

The very same problem has plagued me since March 29th and it has been driving me nuts. I have gone through a TON of troubleshooting too and had replaced a hard drive and a sound card. At times I even felt it was fixed then sadly found out an hour later that it was not. My PC is only 3 years old and I felt it was not old enough to be experiencing problems.

Well today I am confident I found the solution.

Below was the exact error I was receiving:

This would randomly occur in games normally a few minutes in. Just prior to it horrible loud static would come through the speakers. Sometimes it would not blue screen at all it would just reboot or go to a black screen and not recover. I have even had this happen watching YouTube.

What I did to fix: (some of these may not be relevant but it is what i did.)

1.) I found a post where someone reseated their CPU and stated there must have been dirt on the pins because it started working afterwards. I did not see that at all on mine or understand how that could practically happen but I did find that my CPU was stuck in the socket even though I had the lock bar released. After I got it to release with much work I reseated it. I think the weight of the heatsink may had jammed it in. I had had problems in the past with too much pressure on the CPU and it caused games to freeze up. So I reseated it and applied new thermal paste.

2.) I have four DIMMs. I took all of the ram out while I had the CPU heat sink off and make sure I had them paired in accordance with their serial #s so they were in their original sets.

3.) If you have a video card with dual DVI ports try the 2nd DVI port if you are using the first one and vice versa. My thoughts today that maybe one of them went bad or if I used the 2nd one the data flow would be different and it would be less prone to error.

From what I read STOP errors tend to be hardware related. I think my CPU just got wedged down or the 1st DVI port on my video card went bad.

Not sure which but it has been working great even after powering it off and rebooting.

One other note: Most of the help sites I have found refer to this as a Direct X problem or an AMD or Nvidia problem.

In my particular case it was not a software issue at all. I can state this because I bought a brand new Western Digital hard drive, did a fresh install of Windows 7, flashed the bios, then loaded the current version of Catalyst drivers from AMD. This did not fix anything. It just allowed me to run two rounds of a game before a crash. I have seen posts from both Nvidia and AMD users with this problem and therefore believe in many cases it is not a driver issue from either company.

When I shifted my focus from software to checking the hardware I already had I got results.

FYI - possible solution: if your power supply has multiple 6 pin PCI Express power connectors try using the other one / set. Or use an adapter on the molexs

Check all of your power cabling. Especially if you have a 4pin extension cable going to the motherboard's power port for the memory. Reseat it if it does not look secure.

If you only have 2 sticks of ram try seating them in the other set of DIMM slots.

Hope this helps. If not post a response. As I said I have been troubleshooting for nearly 2 months so I can tell you other things I did / tried. Highly frustrating issue. I have seen many of the sites which you have which did not lend much help.
Share
May 28, 2013 10:45:12 AM

Thanks so much for helping. I've changed my graphics power connector for adapter and I think it worked! No bsod since then. Thank you all for trying to help me - love you !
m
0
l
!