[SOLVED] A whole range of BSoDs

Apologies for double post.

Code: 
BugCheck D1, {[COLOR=#ff0000]fffff88001749c08[/COLOR], 2, 8, [COLOR=#0000ff]fffff88001749c08[/COLOR]}

Just noticed that parms 1 & 4 are identical. . .

The literal definition of 0xd1 =
Read More:

P1 = Memory referenced by P4
P2 = IRQL
P3 = 0x8 = execution
P4 = Address that referenced memory P1

So, the object in memory address 0x88001749c08 referenced itself during an execution??
If the first parameter has the same value as the fourth parameter, and the
third parameter indicates an execute operation, this bug check was likely caused
by a driver that was trying to execute code when the code itself was paged out.
Possible causes for the page fault include the following:

  • The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
  • The function call was made to a function in another driver, and that driver was unloaded.
  • The function was called by using a function pointer that was an invalid pointer.
Click to expand...

Run Driver Verifier - https://www.sysnative.com/forums/showthread.php/29-Driver-Verifier-BSOD-related
 
Last edited:
Thank you very much for your help here, John.

This 0xD1 BSOD is very rare, which is why I uploaded it. Almost all are 0x1E, with the occasional 0x3B and 0x4A (all have same IRQL, similar call stack, same memory contents at referenced address, etc. etc.)

Driver Verifier has been running constantly for about 8 months now, and I have looked at every dump produced - it has never given a driver, only ever these destroyed call stacks. I have also used the raw stack, and stack save area on every dump, and nothing interesting has ever shown up there either.

Hard disk situation is interesting. BSODs seem to be caused by my hard disk in some way. Attempting to copy around a large file almost guarantees a BSOD. Most seemingly "random" BSODs are usually caused by the process of MSE, which could be the result of background disk activity. Avoiding disk activity as much as possible makes the BSODs much rarer.

I will need to look up all the details for you, but it is a bit complicated! 1 SSD (64GB Crucial M4 - fully updated firmware), and 2 hard disks (both Western Digital 1TB Caviar Black). No RAID. Two different SATA controllers (need to look up details). One of the hard disks was a recent addition yesterday, and was put onto the other controller. BSODs have not changed because of it.

All BSODs to date have pointed to an unknown driver, AFAIK. I am unsure which disk drivers I can disable without killing the PC. I see a lot of references to ACPI in Device Manager, my SSD and both harddisks only have the following two Microsoft drivers listed as loaded: disk.sys, partmgr.sys, and I have one storage controller listed: JMicron JMB36X with jraid.sys v1.17.63.1. I have no idea whether I can safely disable this or not. I don't deliberately use RAID...

As you can see, I don't know a lot about hard disks and SSDs!

Thanks again.

Richard
 
http://uk.asus.com/Motherboards/Intel_Socket_1155/P8Z68V_PRO/

My motherboard's specs said:
Intel® Z68 chipset :
2 x SATA 6Gb/s port(s), gray
4 x SATA 3Gb/s port(s), blue
Support Raid 0, 1, 5, 10
Support Intel® Smart Response Technology on 2nd generation Intel® Core™ processor family
Marvell® PCIe SATA 6Gb/s controller : *2
2 x SATA 6Gb/s port(s), navy blue
JMicron® JMB362 controller : *2
1 x eSATA 3Gb/s port(s), red

*2: These SATA ports are for data hard drivers only. ATAPI devices are not supported.
Click to expand...

Thanks for any help anyone can offer.

EDIT: I do not use eSATA.

EDIT 2: So, my SSD and first harddisk are on the motherboard controller, but the harddisk I added yesterday, which has changed nothing, was on the Marvell controller.
 
Last edited:
niemiro said:
Thank you very much for your help here, John.
Click to expand...

My pleasure, Richard.

niemiro said:
This 0xD1 BSOD is very rare, which is why I uploaded it. Almost all are 0x1E, with the occasional 0x3B and 0x4A (all have same IRQL, similar call stack, same memory contents at referenced address, etc. etc.)
Click to expand...

0x3b = system service threw an exception. My guess = the exception codes were probably 0xc0000005 = memory access violation; otherwise maybe 0xc000001d = illegal instruction or perhaps 0xc0000185 = I/O error

0x4a = thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. (I have rarely seen this bugcheck)

0xd1 = basically the same as 0xa and very common. What I found odd was seeing ntfs.sys & fltmgr.sys on the stack. This points to SSD/HDD, IMO.



niemiro said:
Driver Verifier has been running constantly for about 8 months now, and I have looked at every dump produced - it has never given a driver, only ever these destroyed call stacks. I have also used the raw stack, and stack save area on every dump, and nothing interesting has ever shown up there either.
Click to expand...

If D/V never BSOD'd giving up a 3rd party driver after 8 months.... turn it off. You are undoubtedly dealing with hardware failure, not a rogue driver.


niemiro said:
Hard disk situation is interesting. BSODs seem to be caused by my hard disk in some way. Attempting to copy around a large file almost guarantees a BSOD. Most seemingly "random" BSODs are usually caused by the process of MSE, which could be the result of background disk activity. Avoiding disk activity as much as possible makes the BSODs much rarer.

I will need to look up all the details for you, but it is a bit complicated! 1 SSD (64GB Crucial M4 - fully updated firmware), and 2 hard disks (both Western Digital 1TB Caviar Black). No RAID. Two different SATA controllers (need to look up details). One of the hard disks was a recent addition yesterday, and was put onto the other controller. BSODs have not changed because of it.
Click to expand...

I would suspect the SSD. You should try installing W7 onto one SATA HDD (disconnect SSD + SATA #2). After install, see if the system is stable. If so, add the SSD & see what happens.


niemiro said:
All BSODs to date have pointed to an unknown driver, AFAIK. I am unsure which disk drivers I can disable without killing the PC. I see a lot of references to ACPI in Device Manager, my SSD and both harddisks only have the following two Microsoft drivers listed as loaded: disk.sys, partmgr.sys, and I have one storage controller listed: JMicron JMB36X with jraid.sys v1.17.63.1. I have no idea whether I can safely disable this or not. I don't deliberately use RAID...

As you can see, I don't know a lot about hard disks and SSDs!

Thanks again.

Richard
Click to expand...

Same here - I have SATA only; no SSD.



I'm running 19 dumps now..... see next post.

John
 
All of the 0x1e are identical -
Code: 
BugCheck 1E, {ffffffff[COLOR="#FF0000"]c0000005[/COLOR], fffff800032eef00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt![COLOR="#FF0000"]MiReplenishPageSlist[/COLOR]+c0 )

All of the 0x3b also have 0xc0000005 exceptions.

0xc0000005 = memory access violation

SSD & or RAM seems like the likely culprit.

Video is another possibility -
- several 0x116 TDR timeouts early on & named ATI
- 0xa named DirectX (default in this case)
- 0x3b named win32k - another indicator video involved

The 0x4a named NT (default), but shows a system service is involved -
Code: 
( nt![COLOR="#FF0000"]KiSystemServiceExit[/COLOR]+245 )

Bugcheck Summaries -
Read More:

Read More:
Read More:


SYSTEM UP-TIME ~5 = just over 1 minute before BSOD
Read More:





I still recommend:

jcgriff2 said:
I would suspect the SSD. You should try installing W7 onto one SATA HDD (disconnect SSD + SATA #2). After install, see if the system is stable. If so, add the SSD & see what happens.
Click to expand...

Regards. . .

John



BSOD SUMMARY

Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031212-9968-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Mar 12 13:27:30.477 2012 (GMT-4)
System Uptime: 0 days 0:02:16.305
BugCheck 4A, {77a2137a, 2, 0, fffff8800d989b60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  RAISED_IRQL_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_svchost.exe_nt!KiSystemServiceExit+245
Bugcheck code 0000004A
Arguments 00000000`77a2137a 00000000`00000002 00000000`00000000 fffff880`0d989b60
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031012-7971-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Mar 10 04:30:50.941 2012 (GMT-4)
System Uptime: 0 days 0:40:45.768
BugCheck 1E, {ffffffffc0000005, fffff80003304f00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`03304f00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\031012-7690-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Mar 10 03:49:19.015 2012 (GMT-4)
System Uptime: 0 days 0:18:17.843
BugCheck 1E, {ffffffffc0000005, fffff800032a8f90, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+150 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+150
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`032a8f90 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030312-8876-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Mar  3 05:23:46.414 2012 (GMT-4)
System Uptime: 0 days 0:22:05.242
BugCheck 3B, {c0000005, fffff800032a2f00, fffff8800c52aed0, 0}
Probably caused by : win32k.sys ( win32k!memset+b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SnippingTool.e
FAILURE_BUCKET_ID:  X64_0x3B_win32k!memset+b0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`032a2f00 fffff880`0c52aed0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030312-8985-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Mar  3 05:01:02.596 2012 (GMT-4)
System Uptime: 0 days 0:08:34.424
BugCheck 3B, {c0000005, fffff800032f3f00, fffff8800c20bd10, 0}
Probably caused by : win32k.sys ( win32k!memset+b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SnippingTool.e
FAILURE_BUCKET_ID:  X64_0x3B_win32k!memset+b0
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`032f3f00 fffff880`0c20bd10 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030312-27081-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Mar  3 04:37:44.378 2012 (GMT-4)
System Uptime: 0 days 0:01:11.206
BugCheck 1E, {ffffffffc0000005, fffff800032aef90, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+150 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  postgres.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+150
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`032aef90 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030312-28329-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Mar  3 04:35:46.215 2012 (GMT-4)
System Uptime: 0 days 0:01:07.042
BugCheck 1E, {ffffffffc0000005, fffff800032bef00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`032bef00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030312-29218-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Mar  3 04:33:47.918 2012 (GMT-4)
System Uptime: 0 days 0:01:22.635
BugCheck 1E, {ffffffffc0000005, fffff800032eef00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  nexserv.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`032eef00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012912-32713-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 14:34:54.497 2012 (GMT-4)
System Uptime: 0 days 7:51:00.325
BugCheck 1E, {ffffffffc0000005, fffff800030abf00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`030abf00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012912-34023-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 06:42:55.324 2012 (GMT-4)
System Uptime: 0 days 2:32:16.153
BugCheck A, {2632a000, 2, 0, fffff800030b52f8}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229
Bugcheck code 0000000A
Arguments 00000000`2632a000 00000000`00000002 00000000`00000000 fffff800`030b52f8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012712-27409-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 27 16:33:45.380 2012 (GMT-4)
System Uptime: 0 days 0:10:12.207
BugCheck 4A, {77131dea, 2, 0, fffff8800cf63b60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  RAISED_IRQL_FAULT
PROCESS_NAME:  MpCmdRun.exe
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_MpCmdRun.exe_nt!KiSystemServiceExit+245
Bugcheck code 0000004A
Arguments 00000000`77131dea 00000000`00000002 00000000`00000000 fffff880`0cf63b60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012112-22339-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 21 05:42:18.922 2012 (GMT-4)
System Uptime: 0 days 0:01:06.750
BugCheck 1E, {ffffffffc0000005, fffff800030a8f00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x1E
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0x1E_VRF_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`030a8f00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012112-29265-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 21 05:37:11.105 2012 (GMT-4)
System Uptime: 0 days 0:00:43.822
BugCheck 1E, {ffffffffc0000005, fffff800030a9f00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x1E
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  X64_0x1E_VRF_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`030a9f00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012112-35708-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 21 05:35:19.369 2012 (GMT-4)
System Uptime: 0 days 1:33:47.070
BugCheck 1E, {ffffffffc0000005, fffff800030b6f00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x1E
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x1E_VRF_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`030b6f00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011812-33680-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 18 15:30:43.601 2012 (GMT-4)
System Uptime: 0 days 1:14:52.429
BugCheck 1E, {ffffffffc0000005, fffff80003101f00, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x1E
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x1E_VRF_nt!MiReplenishPageSlist+c0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`03101f00 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\011812-25318-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 18 13:58:56.795 2012 (GMT-4)
System Uptime: 0 days 0:07:34.512
BugCheck 4A, {747830da, 2, 0, fffff88008685b60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  RAISED_IRQL_FAULT
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_iexplore.exe_nt!KiSystemServiceExit+245
Bugcheck code 0000004A
Arguments 00000000`747830da 00000000`00000002 00000000`00000000 fffff880`08685b60
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\120411-26005-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Dec  4 15:51:23.959 2011 (GMT-4)
System Uptime: 0 days 12:08:02.164
BugCheck 116, {fffffa801653b4e0, fffff880016718b8, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78b8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`1653b4e0 fffff880`016718b8 00000000`00000000 00000000`00000002
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\112711-27783-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Nov 27 11:26:20.630 2011 (GMT-4)
System Uptime: 0 days 5:51:47.457
BugCheck 116, {fffffa800cfc1010, fffff88004a5c8b8, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78b8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`0cfc1010 fffff880`04a5c8b8 00000000`00000000 00000000`00000002
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3401
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\112311-24445-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Nov 22 21:40:38.147 2011 (GMT-4)
System Uptime: 0 days 1:49:09.223
BugCheck 116, {fffffa800cddb4e0, fffff88001665ba8, 0, 2}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+7ba8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`0cddb4e0 fffff880`01665ba8 00000000`00000000 00000000`00000002
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3400
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   


           [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   


           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]

           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


[/font]
 
Thank you very much again, John. Your detailed replies are greatly appreciated.

DV has been disabled. It didn't seem to be doing a lot of good, anyway.

There was a time when I had a lot of 0x117s also. I have had 56 in total, but they seem to have almost stopped now, around the same time as the 0x116s stopped (I removed CCC, and tried various versions of their drivers - I currently have a driver only install which seems almost stable. Whereas I used to get 0x117 and 0x116 almost daily, I have since only had one 0x117 since May. I will investigate the SSD/HDD/memory before going down the video route again, as I think that is pretty good ATM.

I will try out what you have recommended with the SSD/HDD and report back.

Thanks again :)
 
Yes... absolutely you will experience 0x117 "Live Kernel Reports" 5x, 10x or more than 0x116 bugcheck BSODS. These are called WATCHDOG dumps and can be found in

C:\Windows\LiveKernelReports\WATCHDOG
​

0x116 = video TDR Timeout; video driver cannot reset in alloted time (30000ms); system BSODs

0x117 = video TDR Timeout; video driver cannot reset in alloted time (30000ms); but does ultimately recovers; rarely BSODs



Glad to hear you'll try the single HDD SATA install. Wipe that disk with Killdisk.

https://www.sysnative.com/forums/showthread.php/449-Format-HDD-(low-level-format)-KillDisk

So as not to cause problems with your current Windows 7 x64 install/ licensing, download Windows 7 Enterprise 90-day Trial - http://technet.microsoft.com/en-us/evalcenter/cc442495

Or 180-day trial Server 2008R2 SP1 (same build as W7) - http://technet.microsoft.com/en-US/evalcenter/dd459137.aspx

Burn ISO to DVD or USB and install that copy onto a HDD (disconnect SSD + 2nd HDD)

USB - http://www.intowindows.com/how-to-install-windows-7vista-from-usb-drive-detailed-100-working-guide/

ImgBurn - http://www.imgburn.com/index.php?act=download

Kind Regards. . .

John
 
I downloaded the trial, and burned the disk, and was just about to do it...when the BSODs mysteriously stopped (not a single one in last 6+ days). I honestly have no idea why, as I am sure that I haven't changed anything at all. Whatever has changed, I don't know about/was accidental/was not directly by my hand. I am not very hopeful yet though - it hasn't yet been long enough to be sure, but it is going to be hard to test when my normal install isn't BSODing. I will wait for next BSOD, and then try. Thanks again for all your help.
 
It knew we were ganging up on it!

Seriously though... hope BSOD-free status continues.

We're here either way!
 
Thank you all very much for your wonderful help :)

So far, the BSODs have not come back. I shall tentatively mark this as solved now. If they come back, I shall be back.

Thank you all so much again!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top