API tools faq
paste
Advertisement
Guest User

BSOD Page Fault In NonPaged Area - REPORT

a guest
Nov 5th, 2014
236
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.29 KB | None | 0 0
raw download clone embed print report
  1. --------------------------------------------------------------------------------
  2. System Information (local)
  3. --------------------------------------------------------------------------------
  4.  
  5. computer name: GARLOTCH-LAPTOP
  6. windows version: Windows 7 , 6.1, build: 7600
  7. windows dir: C:\Windows
  8. Hardware: 300E5EV/300E4EV/270E5EV/270E4EV/2470EV, SAMSUNG ELECTRONICS CO., LTD., SAMSUNG_NP1234567890
  9. CPU: GenuineIntel Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz Intel586, level: 6
  10. 4 logical processors, active mask: 15
  11. RAM: 4162686976 total
  12.  
  13.  
  14.  
  15.  
  16. --------------------------------------------------------------------------------
  17. Crash Dump Analysis
  18. --------------------------------------------------------------------------------
  19.  
  20. Crash dump directory: C:\Windows\Minidump
  21.  
  22. Crash dumps are enabled on your computer.
  23.  
  24. On Wed 5/11/2014 6:01:51 a.m. GMT your computer crashed
  25. crash dump file: C:\Windows\Minidump\110514-23696-01.dmp
  26. This was probably caused by the following module: cdd.dll (0xFFFFF9600079DC51)
  27. Bugcheck code: 0x50 (0xFFFFF900C018D7A0, 0x0, 0xFFFFF9600079DC51, 0x0)
  28. Error: PAGE_FAULT_IN_NONPAGED_AREA
  29. file path: C:\Windows\system32\cdd.dll
  30. product: Microsoft® Windows® Operating System
  31. company: Microsoft Corporation
  32. description: Canonical Display Driver
  33. Bug check description: This indicates that invalid system memory has been referenced.
  34. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  35. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  36.  
  37.  
  38.  
  39. On Wed 5/11/2014 6:01:51 a.m. GMT your computer crashed
  40. crash dump file: C:\Windows\memory.dmp
  41. This was probably caused by the following module: cdd.dll (cdd+0xDC51)
  42. Bugcheck code: 0x50 (0xFFFFF900C018D7A0, 0x0, 0xFFFFF9600079DC51, 0x0)
  43. Error: PAGE_FAULT_IN_NONPAGED_AREA
  44. file path: C:\Windows\system32\cdd.dll
  45. product: Microsoft® Windows® Operating System
  46. company: Microsoft Corporation
  47. description: Canonical Display Driver
  48. Bug check description: This indicates that invalid system memory has been referenced.
  49. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  50. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  51.  
  52.  
  53.  
  54. On Wed 5/11/2014 2:18:12 a.m. GMT your computer crashed
  55. crash dump file: C:\Windows\Minidump\110514-23680-01.dmp
  56. This was probably caused by the following module: win32k.sys (win32k+0xC6373)
  57. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000106373, 0xFFFFF880067D6030, 0x0)
  58. Error: SYSTEM_SERVICE_EXCEPTION
  59. file path: C:\Windows\system32\win32k.sys
  60. product: Microsoft® Windows® Operating System
  61. company: Microsoft Corporation
  62. description: Multi-User Win32 Driver
  63. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  64. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  65. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  66.  
  67.  
  68.  
  69. On Tue 4/11/2014 7:40:49 a.m. GMT your computer crashed
  70. crash dump file: C:\Windows\Minidump\110414-35833-01.dmp
  71. This was probably caused by the following module: win32k.sys (win32k+0x2328C9)
  72. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960003028C9, 0xFFFFF88009B88110, 0x0)
  73. Error: SYSTEM_SERVICE_EXCEPTION
  74. file path: C:\Windows\system32\win32k.sys
  75. product: Microsoft® Windows® Operating System
  76. company: Microsoft Corporation
  77. description: Multi-User Win32 Driver
  78. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  79. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  80. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  81.  
  82.  
  83.  
  84. On Fri 19/09/2014 11:07:04 a.m. GMT your computer crashed
  85. crash dump file: C:\Windows\Minidump\091914-44366-01.dmp
  86. This was probably caused by the following module: win32k.sys (win32k+0xC6373)
  87. Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001A6373, 0xFFFFF8800611C030, 0x0)
  88. Error: SYSTEM_SERVICE_EXCEPTION
  89. file path: C:\Windows\system32\win32k.sys
  90. product: Microsoft® Windows® Operating System
  91. company: Microsoft Corporation
  92. description: Multi-User Win32 Driver
  93. Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
  94. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
  95. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  96.  
  97.  
  98.  
  99.  
  100. --------------------------------------------------------------------------------
  101. Conclusion
  102. --------------------------------------------------------------------------------
  103.  
  104. 5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
  105.  
  106.  
  107. Read the topic general suggestions for troubleshooting system crashes for more information.
  108.  
  109. Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!