Sign in with
Sign up | Sign in
Your question

BSOD Memory_Management every 3omin

Tags:
  • Blue Screen
  • Windows 8
  • Drivers
  • Memory Management
Last response: in Windows 8
Share
September 8, 2014 1:47:42 PM

Hi,

Yesterday i was having multiple BSOD,

irql_not_less_or_equal &
Memory_Management

I have re installed as many drivers as i could and it seems the irql_not_less_or_equal is not happening any more but i am still getting Memory Management BSOD's

Is it possible for someone to have a look at the attached dump file,

Many thanks

Dump file:
  1. Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\MEMORY.DMP]
  6. Kernel Bitmap Dump File: Only kernel address space is available
  7.  
  8.  
  9. ************* Symbol Path validation summary **************
  10. Response Time (ms) Location
  11. Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
  12. Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
  13. Executable search path is:
  14. Windows 8 Kernel Version 9600 MP (8 procs) Free x64
  15. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  16. Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
  17. Machine Name:
  18. Kernel base = 0xfffff800`21a02000 PsLoadedModuleList = 0xfffff800`21ccc350
  19. Debug session time: Mon Sep 8 13:47:08.488 2014 (UTC - 6:00)
  20. System Uptime: 0 days 0:02:00.215
  21. Loading Kernel Symbols
  22. ...............................................................
  23. ................................................................
  24. ...................Page 113301 not present in the dump file. Type ".hh dbgerr004" for details
  25. .Page 11d83a not present in the dump file. Type ".hh dbgerr004" for details
  26. ..........................
  27. Loading User Symbols
  28. PEB is paged out (Peb.Ldr = 00000000`fe863018). Type ".hh dbgerr001" for details
  29. Loading unloaded module list
  30. ...........
  31. *******************************************************************************
  32. * *
  33. * Bugcheck Analysis *
  34. * *
  35. *******************************************************************************
  36.  
  37. Use !analyze -v to get detailed debugging information.
  38.  
  39. BugCheck 1A, {5100, fffff6f0004d7ac8, 1, 1f3ca00000220}
  40.  
  41. Probably caused by : Npfs.SYS ( Npfs!NpAddDataQueueEntry+22b )
  42.  
  43. Followup: MachineOwner
  44. ---------
  45.  
  46. 1: kd> !analyze -v
  47. *******************************************************************************
  48. * *
  49. * Bugcheck Analysis *
  50. * *
  51. *******************************************************************************
  52.  
  53. MEMORY_MANAGEMENT (1a)
  54. # Any other values for parameter 1 must be individually examined.
  55. Arguments:
  56. Arg1: 0000000000005100, The subtype of the bugcheck.
  57. Arg2: fffff6f0004d7ac8
  58. Arg3: 0000000000000001
  59. Arg4: 0001f3ca00000220
  60.  
  61. Debugging Details:
  62. ------------------
  63.  
  64.  
  65. BUGCHECK_STR: 0x1a_5100
  66.  
  67. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  68.  
  69. PROCESS_NAME: chrome.exe
  70.  
  71. CURRENT_IRQL: 0
  72.  
  73. ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
  74.  
  75. LAST_CONTROL_TRANSFER: from fffff80021b80565 to fffff80021b55ca0
  76.  
  77. STACK_TEXT:
  78. ffffd000`23f922d8 fffff800`21b80565 : 00000000`0000001a 00000000`00005100 fffff6f0`004d7ac8 00000000`00000001 : nt!KeBugCheckEx
  79. ffffd000`23f922e0 fffff800`21a6b1ea : 00000000`00000006 00000000`00000000 00000000`00000006 00000000`00000308 : nt! ?? ::FNODOBFM::`string'+0x1a3b5
  80. ffffd000`23f92430 fffff800`21a6a512 : fffff800`00000002 00000000`00000200 fffff800`21cdf840 00000000`00000000 : nt!MiAllocatePoolPages+0x146
  81. ffffd000`23f92480 fffff800`21c96f23 : 00000000`00000000 00000000`7246704e 00000000`00001000 00000000`00005990 : nt!ExpAllocateBigPool+0xd2
  82. ffffd000`23f92580 fffff800`21a2b6ff : 00000000`00000000 00000000`00005990 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0xa73
  83. ffffd000`23f92650 fffff801`38fe845b : fffff800`21a02000 00000000`00000000 00000000`00001000 ffffe000`00000000 : nt!ExAllocatePoolWithQuotaTag+0x5f
  84. ffffd000`23f926e0 fffff801`38fe8824 : ffffc001`f1395210 ffffd000`23f92820 ffffc001`f1395258 ffffb953`00005990 : Npfs!NpAddDataQueueEntry+0x22b
  85. ffffd000`23f92740 fffff801`38fe85cf : ffffe000`94c51010 00000000`06a5b000 00000000`00000000 ffffe000`9a9e4880 : Npfs!NpCommonWrite+0x1f4
  86. ffffd000`23f927d0 fffff801`37a7a0f5 : ffffe000`9458e040 ffffe000`9aa27f20 ffffe000`94c51010 ffffd000`23f92850 : Npfs!NpFsdWrite+0x5f
  87. ffffd000`23f92840 fffff800`21da7498 : 00000000`00000001 ffffd000`23f92921 ffffe000`9aa27f20 ffffe000`9ada2301 : fltmgr!FltpDispatch+0xf5
  88. ffffd000`23f928a0 fffff800`21da6e44 : ffffe000`9aa27f04 ffffe000`9aa27f20 ffffb953`25eebb08 ffffe000`9aa27f20 : nt!IopSynchronousServiceTail+0x16c
  89. ffffd000`23f92970 fffff800`21b614b3 : ffffe000`9a9e4801 00000000`00000000 00000000`00000001 00000000`01249644 : nt!NtWriteFile+0x750
  90. ffffd000`23f92a90 00000000`00bf0002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
  91. 00000000`0053f108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xbf0002
  92.  
  93.  
  94. STACK_COMMAND: kb
  95.  
  96. FOLLOWUP_IP:
  97. Npfs!NpAddDataQueueEntry+22b
  98. fffff801`38fe845b 488bf8 mov rdi,rax
  99.  
  100. SYMBOL_STACK_INDEX: 6
  101.  
  102. SYMBOL_NAME: Npfs!NpAddDataQueueEntry+22b
  103.  
  104. FOLLOWUP_NAME: MachineOwner
  105.  
  106. MODULE_NAME: Npfs
  107.  
  108. IMAGE_NAME: Npfs.SYS
  109.  
  110. DEBUG_FLR_IMAGE_TIMESTAMP: 5215f8a9
  111.  
  112. BUCKET_ID_FUNC_OFFSET: 22b
  113.  
  114. FAILURE_BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  115.  
  116. BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  117.  
  118. ANALYSIS_SOURCE: KM
  119.  
  120. FAILURE_ID_HASH_STRING: km:0x1a_5100_npfs!npadddataqueueentry
  121.  
  122. FAILURE_ID_HASH: {062eda43-abef-230c-8dc0-4845c85a0f02}
  123.  
  124. Followup: MachineOwner
  125. ---------
  126.  
  127. 1: kd> !analyze -v
  128. *******************************************************************************
  129. * *
  130. * Bugcheck Analysis *
  131. * *
  132. *******************************************************************************
  133.  
  134. MEMORY_MANAGEMENT (1a)
  135. # Any other values for parameter 1 must be individually examined.
  136. Arguments:
  137. Arg1: 0000000000005100, The subtype of the bugcheck.
  138. Arg2: fffff6f0004d7ac8
  139. Arg3: 0000000000000001
  140. Arg4: 0001f3ca00000220
  141.  
  142. Debugging Details:
  143. ------------------
  144.  
  145.  
  146. BUGCHECK_STR: 0x1a_5100
  147.  
  148. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  149.  
  150. PROCESS_NAME: chrome.exe
  151.  
  152. CURRENT_IRQL: 0
  153.  
  154. ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
  155.  
  156. LAST_CONTROL_TRANSFER: from fffff80021b80565 to fffff80021b55ca0
  157.  
  158. STACK_TEXT:
  159. ffffd000`23f922d8 fffff800`21b80565 : 00000000`0000001a 00000000`00005100 fffff6f0`004d7ac8 00000000`00000001 : nt!KeBugCheckEx
  160. ffffd000`23f922e0 fffff800`21a6b1ea : 00000000`00000006 00000000`00000000 00000000`00000006 00000000`00000308 : nt! ?? ::FNODOBFM::`string'+0x1a3b5
  161. ffffd000`23f92430 fffff800`21a6a512 : fffff800`00000002 00000000`00000200 fffff800`21cdf840 00000000`00000000 : nt!MiAllocatePoolPages+0x146
  162. ffffd000`23f92480 fffff800`21c96f23 : 00000000`00000000 00000000`7246704e 00000000`00001000 00000000`00005990 : nt!ExpAllocateBigPool+0xd2
  163. ffffd000`23f92580 fffff800`21a2b6ff : 00000000`00000000 00000000`00005990 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0xa73
  164. ffffd000`23f92650 fffff801`38fe845b : fffff800`21a02000 00000000`00000000 00000000`00001000 ffffe000`00000000 : nt!ExAllocatePoolWithQuotaTag+0x5f
  165. ffffd000`23f926e0 fffff801`38fe8824 : ffffc001`f1395210 ffffd000`23f92820 ffffc001`f1395258 ffffb953`00005990 : Npfs!NpAddDataQueueEntry+0x22b
  166. ffffd000`23f92740 fffff801`38fe85cf : ffffe000`94c51010 00000000`06a5b000 00000000`00000000 ffffe000`9a9e4880 : Npfs!NpCommonWrite+0x1f4
  167. ffffd000`23f927d0 fffff801`37a7a0f5 : ffffe000`9458e040 ffffe000`9aa27f20 ffffe000`94c51010 ffffd000`23f92850 : Npfs!NpFsdWrite+0x5f
  168. ffffd000`23f92840 fffff800`21da7498 : 00000000`00000001 ffffd000`23f92921 ffffe000`9aa27f20 ffffe000`9ada2301 : fltmgr!FltpDispatch+0xf5
  169. ffffd000`23f928a0 fffff800`21da6e44 : ffffe000`9aa27f04 ffffe000`9aa27f20 ffffb953`25eebb08 ffffe000`9aa27f20 : nt!IopSynchronousServiceTail+0x16c
  170. ffffd000`23f92970 fffff800`21b614b3 : ffffe000`9a9e4801 00000000`00000000 00000000`00000001 00000000`01249644 : nt!NtWriteFile+0x750
  171. ffffd000`23f92a90 00000000`00bf0002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
  172. 00000000`0053f108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xbf0002
  173.  
  174.  
  175. STACK_COMMAND: kb
  176.  
  177. FOLLOWUP_IP:
  178. Npfs!NpAddDataQueueEntry+22b
  179. fffff801`38fe845b 488bf8 mov rdi,rax
  180.  
  181. SYMBOL_STACK_INDEX: 6
  182.  
  183. SYMBOL_NAME: Npfs!NpAddDataQueueEntry+22b
  184.  
  185. FOLLOWUP_NAME: MachineOwner
  186.  
  187. MODULE_NAME: Npfs
  188.  
  189. IMAGE_NAME: Npfs.SYS
  190.  
  191. DEBUG_FLR_IMAGE_TIMESTAMP: 5215f8a9
  192.  
  193. BUCKET_ID_FUNC_OFFSET: 22b
  194.  
  195. FAILURE_BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  196.  
  197. BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  198.  
  199. ANALYSIS_SOURCE: KM
  200.  
  201. FAILURE_ID_HASH_STRING: km:0x1a_5100_npfs!npadddataqueueentry
  202.  
  203. FAILURE_ID_HASH: {062eda43-abef-230c-8dc0-4845c85a0f02}
  204.  
  205. Followup: MachineOwner
  206. ---------
  207.  
  208. 1: kd> !analyze -v
  209. *******************************************************************************
  210. * *
  211. * Bugcheck Analysis *
  212. * *
  213. *******************************************************************************
  214.  
  215. MEMORY_MANAGEMENT (1a)
  216. # Any other values for parameter 1 must be individually examined.
  217. Arguments:
  218. Arg1: 0000000000005100, The subtype of the bugcheck.
  219. Arg2: fffff6f0004d7ac8
  220. Arg3: 0000000000000001
  221. Arg4: 0001f3ca00000220
  222.  
  223. Debugging Details:
  224. ------------------
  225.  
  226.  
  227. BUGCHECK_STR: 0x1a_5100
  228.  
  229. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  230.  
  231. PROCESS_NAME: chrome.exe
  232.  
  233. CURRENT_IRQL: 0
  234.  
  235. ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
  236.  
  237. LAST_CONTROL_TRANSFER: from fffff80021b80565 to fffff80021b55ca0
  238.  
  239. STACK_TEXT:
  240. ffffd000`23f922d8 fffff800`21b80565 : 00000000`0000001a 00000000`00005100 fffff6f0`004d7ac8 00000000`00000001 : nt!KeBugCheckEx
  241. ffffd000`23f922e0 fffff800`21a6b1ea : 00000000`00000006 00000000`00000000 00000000`00000006 00000000`00000308 : nt! ?? ::FNODOBFM::`string'+0x1a3b5
  242. ffffd000`23f92430 fffff800`21a6a512 : fffff800`00000002 00000000`00000200 fffff800`21cdf840 00000000`00000000 : nt!MiAllocatePoolPages+0x146
  243. ffffd000`23f92480 fffff800`21c96f23 : 00000000`00000000 00000000`7246704e 00000000`00001000 00000000`00005990 : nt!ExpAllocateBigPool+0xd2
  244. ffffd000`23f92580 fffff800`21a2b6ff : 00000000`00000000 00000000`00005990 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0xa73
  245. ffffd000`23f92650 fffff801`38fe845b : fffff800`21a02000 00000000`00000000 00000000`00001000 ffffe000`00000000 : nt!ExAllocatePoolWithQuotaTag+0x5f
  246. ffffd000`23f926e0 fffff801`38fe8824 : ffffc001`f1395210 ffffd000`23f92820 ffffc001`f1395258 ffffb953`00005990 : Npfs!NpAddDataQueueEntry+0x22b
  247. ffffd000`23f92740 fffff801`38fe85cf : ffffe000`94c51010 00000000`06a5b000 00000000`00000000 ffffe000`9a9e4880 : Npfs!NpCommonWrite+0x1f4
  248. ffffd000`23f927d0 fffff801`37a7a0f5 : ffffe000`9458e040 ffffe000`9aa27f20 ffffe000`94c51010 ffffd000`23f92850 : Npfs!NpFsdWrite+0x5f
  249. ffffd000`23f92840 fffff800`21da7498 : 00000000`00000001 ffffd000`23f92921 ffffe000`9aa27f20 ffffe000`9ada2301 : fltmgr!FltpDispatch+0xf5
  250. ffffd000`23f928a0 fffff800`21da6e44 : ffffe000`9aa27f04 ffffe000`9aa27f20 ffffb953`25eebb08 ffffe000`9aa27f20 : nt!IopSynchronousServiceTail+0x16c
  251. ffffd000`23f92970 fffff800`21b614b3 : ffffe000`9a9e4801 00000000`00000000 00000000`00000001 00000000`01249644 : nt!NtWriteFile+0x750
  252. ffffd000`23f92a90 00000000`00bf0002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
  253. 00000000`0053f108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xbf0002
  254.  
  255.  
  256. STACK_COMMAND: kb
  257.  
  258. FOLLOWUP_IP:
  259. Npfs!NpAddDataQueueEntry+22b
  260. fffff801`38fe845b 488bf8 mov rdi,rax
  261.  
  262. SYMBOL_STACK_INDEX: 6
  263.  
  264. SYMBOL_NAME: Npfs!NpAddDataQueueEntry+22b
  265.  
  266. FOLLOWUP_NAME: MachineOwner
  267.  
  268. MODULE_NAME: Npfs
  269.  
  270. IMAGE_NAME: Npfs.SYS
  271.  
  272. DEBUG_FLR_IMAGE_TIMESTAMP: 5215f8a9
  273.  
  274. BUCKET_ID_FUNC_OFFSET: 22b
  275.  
  276. FAILURE_BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  277.  
  278. BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  279.  
  280. ANALYSIS_SOURCE: KM
  281.  
  282. FAILURE_ID_HASH_STRING: km:0x1a_5100_npfs!npadddataqueueentry
  283.  
  284. FAILURE_ID_HASH: {062eda43-abef-230c-8dc0-4845c85a0f02}
  285.  
  286. Followup: MachineOwner
  287. ---------
  288.  
  289. 1: kd> !analyze -v
  290. *******************************************************************************
  291. * *
  292. * Bugcheck Analysis *
  293. * *
  294. *******************************************************************************
  295.  
  296. MEMORY_MANAGEMENT (1a)
  297. # Any other values for parameter 1 must be individually examined.
  298. Arguments:
  299. Arg1: 0000000000005100, The subtype of the bugcheck.
  300. Arg2: fffff6f0004d7ac8
  301. Arg3: 0000000000000001
  302. Arg4: 0001f3ca00000220
  303.  
  304. Debugging Details:
  305. ------------------
  306.  
  307.  
  308. BUGCHECK_STR: 0x1a_5100
  309.  
  310. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  311.  
  312. PROCESS_NAME: chrome.exe
  313.  
  314. CURRENT_IRQL: 0
  315.  
  316. ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
  317.  
  318. LAST_CONTROL_TRANSFER: from fffff80021b80565 to fffff80021b55ca0
  319.  
  320. STACK_TEXT:
  321. ffffd000`23f922d8 fffff800`21b80565 : 00000000`0000001a 00000000`00005100 fffff6f0`004d7ac8 00000000`00000001 : nt!KeBugCheckEx
  322. ffffd000`23f922e0 fffff800`21a6b1ea : 00000000`00000006 00000000`00000000 00000000`00000006 00000000`00000308 : nt! ?? ::FNODOBFM::`string'+0x1a3b5
  323. ffffd000`23f92430 fffff800`21a6a512 : fffff800`00000002 00000000`00000200 fffff800`21cdf840 00000000`00000000 : nt!MiAllocatePoolPages+0x146
  324. ffffd000`23f92480 fffff800`21c96f23 : 00000000`00000000 00000000`7246704e 00000000`00001000 00000000`00005990 : nt!ExpAllocateBigPool+0xd2
  325. ffffd000`23f92580 fffff800`21a2b6ff : 00000000`00000000 00000000`00005990 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0xa73
  326. ffffd000`23f92650 fffff801`38fe845b : fffff800`21a02000 00000000`00000000 00000000`00001000 ffffe000`00000000 : nt!ExAllocatePoolWithQuotaTag+0x5f
  327. ffffd000`23f926e0 fffff801`38fe8824 : ffffc001`f1395210 ffffd000`23f92820 ffffc001`f1395258 ffffb953`00005990 : Npfs!NpAddDataQueueEntry+0x22b
  328. ffffd000`23f92740 fffff801`38fe85cf : ffffe000`94c51010 00000000`06a5b000 00000000`00000000 ffffe000`9a9e4880 : Npfs!NpCommonWrite+0x1f4
  329. ffffd000`23f927d0 fffff801`37a7a0f5 : ffffe000`9458e040 ffffe000`9aa27f20 ffffe000`94c51010 ffffd000`23f92850 : Npfs!NpFsdWrite+0x5f
  330. ffffd000`23f92840 fffff800`21da7498 : 00000000`00000001 ffffd000`23f92921 ffffe000`9aa27f20 ffffe000`9ada2301 : fltmgr!FltpDispatch+0xf5
  331. ffffd000`23f928a0 fffff800`21da6e44 : ffffe000`9aa27f04 ffffe000`9aa27f20 ffffb953`25eebb08 ffffe000`9aa27f20 : nt!IopSynchronousServiceTail+0x16c
  332. ffffd000`23f92970 fffff800`21b614b3 : ffffe000`9a9e4801 00000000`00000000 00000000`00000001 00000000`01249644 : nt!NtWriteFile+0x750
  333. ffffd000`23f92a90 00000000`00bf0002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
  334. 00000000`0053f108 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xbf0002
  335.  
  336.  
  337. STACK_COMMAND: kb
  338.  
  339. FOLLOWUP_IP:
  340. Npfs!NpAddDataQueueEntry+22b
  341. fffff801`38fe845b 488bf8 mov rdi,rax
  342.  
  343. SYMBOL_STACK_INDEX: 6
  344.  
  345. SYMBOL_NAME: Npfs!NpAddDataQueueEntry+22b
  346.  
  347. FOLLOWUP_NAME: MachineOwner
  348.  
  349. MODULE_NAME: Npfs
  350.  
  351. IMAGE_NAME: Npfs.SYS
  352.  
  353. DEBUG_FLR_IMAGE_TIMESTAMP: 5215f8a9
  354.  
  355. BUCKET_ID_FUNC_OFFSET: 22b
  356.  
  357. FAILURE_BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  358.  
  359. BUCKET_ID: 0x1a_5100_Npfs!NpAddDataQueueEntry
  360.  
  361. ANALYSIS_SOURCE: KM
  362.  
  363. FAILURE_ID_HASH_STRING: km:0x1a_5100_npfs!npadddataqueueentry
  364.  
  365. FAILURE_ID_HASH: {062eda43-abef-230c-8dc0-4845c85a0f02}
  366.  
  367. Followup: MachineOwner
  368. ---------

More about : bsod memory management 3omin

September 22, 2014 8:17:26 AM

if u re on desktop, open up ur pc take off CMOS battery, and power supply to board and CPU socket for 1 hour, put them back..
if u re on a laptop, use the laptop so that the battery should be really empty-meaning that u should not be able to boot up without plugging in..then take the battery off leave it for an hour and put it back, plug it in, boot up and u should be good to go..

Note: if u have any drives encrypted with bitlocker, those will all lose encryption.. u will have to encrypt again..

Cheers,
Prahlad
m
0
l
Related resources
a b * Windows 8
a b \ Driver
September 22, 2014 8:35:45 AM

Actually, I would start by making sure you are updated to the most recent version of Chrome and see if this issue reoccurs.
m
0
l
September 30, 2014 3:46:25 PM

Updating chrome may help since that is the program that is running while the problem occurs. Resetting the bios is probably not going to solve this issue. Some more info would help, like, when does it happen? Are you using a specific program when this happens? How often does this happen? Every day, every hour, every few minutes? When was the last time you changed hardware, re applied the thermal compound? What kind of computer is this, a laptop, desktop. It looks like you have windows 8, that is about the only useful information the bug check will give us other than there was a problem with the memory management system and here are the hashes I was running when it occurred.
m
0
l
!