![]() |
|
28 Jan 2010 | #1 |
|
Windows 7 multiple BSOD problems
The BSODs have been happening since I've built this computer at the end of October 2009. At first it was a few that didn't bother me. As of now the BSODs have accumulated and have been quite bothersome. I'm hoping somebody can help with my problem.
Microsoft Windows 7 Ultimate x64 Intel Core 2 Quad Q9650 3.0Ghz (not overclocked) Gigabyte GA-EP45-UD3R LGA 775 Intel P45 ATX Intel Motherboard G.Skill 4GB (2 x 2GB) 240-pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel EVGA GeForce GTX 260 Core 216 Superclocked edition 4 x Western Digital Caviar Black WD6401AALS 640GB 7200 RPM Sata 3.0Gb/s (Raid 10) I do recall switching the slots i put my RAM in decreasing the amounts of BSODs when installing Windows 7, but I'm not sure if this is the whole problem with my system. From the most occurring BSOD codes to the least, I've recorded: 0x3b 0x4a 0x24 0x7e 0x50 (happend very rarely) and a new one I've seen recently is 0x1e Most of these BSODs are random, and even happen when my computer is idle when I'm away. I've ran virus and spyware tests. And I have tried cleaning my registries, which has cut down the amount of BSODs from four a day to one every two days. Probably should have fixed these problems from the start. I hope somebody can help me. Also sorry for the amount of files in the zip folder. |
My System Specs![]() |
. |
|
28 Jan 2010 | #2 |
|
The BSODs have been happening since I've built this computer at the end of October 2009. At first it was a few that didn't bother me. As of now the BSODs have accumulated and have been quite bothersome. I'm hoping somebody can help with my problem.
Microsoft Windows 7 Ultimate x64 Intel Core 2 Quad Q9650 3.0Ghz (not overclocked) Gigabyte GA-EP45-UD3R LGA 775 Intel P45 ATX Intel Motherboard G.Skill 4GB (2 x 2GB) 240-pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel EVGA GeForce GTX 260 Core 216 Superclocked edition 4 x Western Digital Caviar Black WD6401AALS 640GB 7200 RPM Sata 3.0Gb/s (Raid 10) I do recall switching the slots i put my RAM in decreasing the amounts of BSODs when installing Windows 7, but I'm not sure if this is the whole problem with my system. From the most occurring BSOD codes to the least, I've recorded: 0x3b 0x4a 0x24 0x7e 0x50 (happend very rarely) and a new one I've seen recently is 0x1e Most of these BSODs are random, and even happen when my computer is idle when I'm away. I've ran virus and spyware tests. And I have tried cleaning my registries, which has cut down the amount of BSODs from four a day to one every two days. Probably should have fixed these problems from the start. I hope somebody can help me. Also sorry for the amount of files in the zip folder. Hi and welcome I think you hpld the record for the most number of DMP's. They report back as various probable causes. I suspect 1-RAID 2-RAM 3-hardware lets do this download memtestx86 and run for 5 passes. the fact that the bsod frequency changed when you moved ram aound I suspect ram Update your raid driver run a system file check typs cmd in search>right click and run as admin>sfc /scannow If you are overclocking STOP Let us know the results Code:
010810-31465-01.dmp 1/8/2010 5:51:36 PM ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY 0x000000fc fffff880`05bcf010 f6e00000`84d40121 fffff880`0a3fd7a0 00000000`00000002 portcls.sys portcls.sys+1d010 x64 C:\Users\K\Desktop\Minidump\010810-31465-01.dmp 4 15 7600 121709-20030-01.dmp 12/17/2009 8:43:36 PM DRIVER_PORTION_MUST_BE_NONPAGED 0x000000d3 fffff960`003599ac 00000000`00000002 00000000`00000000 fffff800`02aa01b9 win32k.sys win32k.sys+2e99ac x64 C:\Users\K\Desktop\Minidump\121709-20030-01.dmp 4 15 7600 121509-25802-01.dmp 12/15/2009 12:17:00 AM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`7742021a 00000000`00000002 00000000`00000000 fffff880`087c0c60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\121509-25802-01.dmp 4 15 7600 121909-20623-01.dmp 12/19/2009 9:55:02 PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`77cf021a 00000000`00000002 00000000`00000000 fffff880`0686bc60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\121909-20623-01.dmp 4 15 7600 010510-20560-01.dmp 1/5/2010 3:09:00 PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`7721021a 00000000`00000002 00000000`00000000 fffff880`06393c60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\010510-20560-01.dmp 4 15 7600 010610-28906-01.dmp 1/6/2010 8:50:12 PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`770d021a 00000000`00000002 00000000`00000000 fffff880`0671ac60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\010610-28906-01.dmp 4 15 7600 010810-25303-01.dmp 1/8/2010 1:08:20 PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`7703021a 00000000`00000002 00000000`00000000 fffff880`0652cc60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\010810-25303-01.dmp 4 15 7600 010910-25958-01.dmp 1/9/2010 4:39:26 PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`7735021a 00000000`00000002 00000000`00000000 fffff880`07b38c60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\010910-25958-01.dmp 4 15 7600 011210-25209-01.dmp 1/12/2010 10:52:50 AM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`76fc021a 00000000`00000002 00000000`00000000 fffff880`07033c60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\011210-25209-01.dmp 4 15 7600 012410-144300-01.dmp 1/24/2010 3:08:42 PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`7738021a 00000000`00000002 00000000`00000000 fffff880`06abcc60 iaStor.sys iaStor.sys+56057 x64 C:\Users\K\Desktop\Minidump\012410-144300-01.dmp 4 15 7600 012810-30778-01.dmp 1/28/2010 8:48:28 AM IRQL_GT_ZERO_AT_SYSTEM_SERVICE 0x0000004a 00000000`7783021a 00000000`00000002 00000000`00000000 fffff880`066c3c60 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\012810-30778-01.dmp 4 15 7600 010810-20732-01.dmp 1/8/2010 3:40:30 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff880`0ab3af00 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\010810-20732-01.dmp 4 15 7600 012410-26145-01.dmp 1/24/2010 7:52:48 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71ed0 x64 C:\Users\K\Desktop\Minidump\012410-26145-01.dmp 4 15 7600 012810-28563-01.dmp 1/28/2010 10:02:28 AM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c000001d fffffa80`043d2347 00000000`00000002 fffff800`02c0b000 sptd.sys sptd.sys+42260 x64 C:\Users\K\Desktop\Minidump\012810-28563-01.dmp 4 15 7600 121709-23899-01.dmp 12/17/2009 12:47:52 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`02d846b8 fffff880`02d83f10 fffff800`02a9c4ec Ntfs.sys Ntfs.sys+213d8 x64 C:\Users\K\Desktop\Minidump\121709-23899-01.dmp 4 15 7600 122409-39967-01.dmp 12/24/2009 3:12:14 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`078fcee8 fffff880`078fc740 fffff800`02aacc1a Ntfs.sys Ntfs.sys+213d8 x64 C:\Users\K\Desktop\Minidump\122409-39967-01.dmp 4 15 7600 011110-25786-01.dmp 1/11/2010 8:54:52 PM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`08f5e598 fffff880`08f5ddf0 fffff800`02cb251a Ntfs.sys Ntfs.sys+213d8 x64 C:\Users\K\Desktop\Minidump\011110-25786-01.dmp 4 15 7600 011510-22479-01.dmp 1/15/2010 1:45:44 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`035856a8 fffff880`03584f00 fffff800`02c65dd9 Ntfs.sys Ntfs.sys+213d8 x64 C:\Users\K\Desktop\Minidump\011510-22479-01.dmp 4 15 7600 010410-27736-01.dmp 1/4/2010 11:26:02 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff140`18acc750 00000000`00000001 fffff880`046cdde4 00000000`00000007 dxgmms1.sys dxgmms1.sys+3a9a0 x64 C:\Users\K\Desktop\Minidump\010410-27736-01.dmp 4 15 7600 011010-26613-01.dmp 1/10/2010 2:20:36 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`ffffff8b 00000000`00000001 fffff960`00313403 00000000`00000000 win32k.sys win32k.sys+227781 x64 C:\Users\K\Desktop\Minidump\011010-26613-01.dmp 4 15 7600 011310-26691-01.dmp 1/13/2010 12:12:24 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`0a38a000 00000000`00000000 fffff800`02ccfd0a 00000000`00000000 USBPORT.SYS USBPORT.SYS+1277e x64 C:\Users\K\Desktop\Minidump\011310-26691-01.dmp 4 15 7600 012010-24102-01.dmp 1/20/2010 3:12:00 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff960`003b0480 00000000`00000000 fffff960`001b67cb 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\012010-24102-01.dmp 4 15 7600 121909-24086-01.dmp 12/19/2009 9:43:12 PM REFERENCE_BY_POINTER 0x00000018 00000000`00000000 fffffa80`053420f0 00000000`00000002 ff000000`00000001 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\121909-24086-01.dmp 4 15 7600 010410-25069-01.dmp 1/4/2010 7:41:52 PM REFERENCE_BY_POINTER 0x00000018 00000000`00000000 fffffa80`03ee3670 00000000`00000002 ff000000`0000000d fileinfo.sys fileinfo.sys+9763 x64 C:\Users\K\Desktop\Minidump\010410-25069-01.dmp 4 15 7600 121109-20545-01.dmp 12/11/2009 8:01:18 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`001657c6 fffff880`09c37e40 00000000`00000000 win32k.sys win32k.sys+c57c6 x64 C:\Users\K\Desktop\Minidump\121109-20545-01.dmp 4 15 7600 121309-19453-01.dmp 12/13/2009 1:18:52 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02a7f145 fffff880`041feb30 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\121309-19453-01.dmp 4 15 7600 121909-24211-01.dmp 12/19/2009 3:57:20 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`08eca9f5 fffff880`0a703c50 00000000`00000000 SRTSP64.SYS SRTSP64.SYS+449f5 x64 C:\Users\K\Desktop\Minidump\121909-24211-01.dmp 4 15 7600 122209-32105-01.dmp 12/22/2009 7:34:46 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`01553df8 fffff880`0a0b17b0 00000000`00000000 fltmgr.sys fltmgr.sys+6df8 x64 C:\Users\K\Desktop\Minidump\122209-32105-01.dmp 4 15 7600 010510-23836-01.dmp 1/5/2010 1:05:50 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02cde4d8 fffff880`09047f90 00000000`00000000 dxgmms1.sys dxgmms1.sys+83f1 x64 C:\Users\K\Desktop\Minidump\010510-23836-01.dmp 4 15 7600 010510-33212-01.dmp 1/5/2010 7:25:22 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02f7067c fffff880`0a63b040 00000000`00000000 win32k.sys win32k.sys+0 x64 C:\Users\K\Desktop\Minidump\010510-33212-01.dmp 4 15 7600 010610-25615-01.dmp 1/6/2010 1:00:02 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`0020b50e fffff880`074921d0 00000000`00000000 win32k.sys win32k.sys+18b50e x64 C:\Users\K\Desktop\Minidump\010610-25615-01.dmp 4 15 7600 010910-30981-01.dmp 1/9/2010 10:28:32 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02cd0324 fffff880`075893d0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\010910-30981-01.dmp 4 15 7600 011010-32557-01.dmp 1/10/2010 11:41:22 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02ccf0b6 fffff880`09d51130 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\011010-32557-01.dmp 4 15 7600 011110-29047-01.dmp 1/11/2010 1:54:08 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`0145daac fffff880`067b84d0 00000000`00000000 SYMEFA64.SYS SYMEFA64.SYS+5daac x64 C:\Users\K\Desktop\Minidump\011110-29047-01.dmp 4 15 7600 011110-24258-01.dmp 1/11/2010 2:31:44 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02c53c5f fffff880`073e3d30 00000000`00000000 Ntfs.sys Ntfs.sys+117b5 x64 C:\Users\K\Desktop\Minidump\011110-24258-01.dmp 4 15 7600 011910-23961-01.dmp 1/19/2010 10:07:28 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`03069aab fffff880`08a80fe0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\011910-23961-01.dmp 4 15 7600 012010-26566-01.dmp 1/20/2010 10:03:20 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02d7cb67 fffff880`06b89c60 00000000`00000000 BHDrvx64.sys BHDrvx64.sys+26a27 x64 C:\Users\K\Desktop\Minidump\012010-26566-01.dmp 4 15 7600 012210-24804-01.dmp 1/22/2010 1:50:42 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02c91b7c fffff880`04a32ca0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\012210-24804-01.dmp 4 15 7600 012310-28376-01.dmp 1/23/2010 3:03:28 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02c6d41c fffff880`0acc3dc0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\012310-28376-01.dmp 4 15 7600 012410-26738-01.dmp 1/24/2010 11:51:50 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02ce0136 fffff880`0affef30 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\012410-26738-01.dmp 4 15 7600 012710-26847-01.dmp 1/27/2010 4:53:36 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02cd618c fffff880`0670e0f0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\012710-26847-01.dmp 4 15 7600 121309-26161-01.dmp 12/13/2009 9:59:34 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`0471ccee fffff880`08900668 fffff880`088ffec0 dxgmms1.sys dxgmms1.sys+1ded3 x64 C:\Users\K\Desktop\Minidump\121309-26161-01.dmp 4 15 7600 122409-30388-01.dmp 12/24/2009 11:54:52 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`0154bfa9 fffff880`035fc4d8 fffff880`035fbd30 fltmgr.sys fltmgr.sys+432e x64 C:\Users\K\Desktop\Minidump\122409-30388-01.dmp 4 15 7600 123109-29780-01.dmp 12/31/2009 12:49:22 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02f8a3f5 fffff880`035fc858 fffff880`035fc0b0 ntoskrnl.exe ntoskrnl.exe+3853f5 x64 C:\Users\K\Desktop\Minidump\123109-29780-01.dmp 4 15 7600 123109-21824-01.dmp 12/31/2009 3:06:14 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`04997ecf fffff880`065be868 fffff880`065be0c0 dxgmms1.sys dxgmms1.sys+38ecf x64 C:\Users\K\Desktop\Minidump\123109-21824-01.dmp 4 15 7600 010810-18969-01.dmp 1/8/2010 8:44:06 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`103aaacc fffff880`02f2ae38 fffff880`02f2a690 nvlddmkm.sys nvlddmkm.sys+e020f x64 C:\Users\K\Desktop\Minidump\010810-18969-01.dmp 4 15 7600 011810-21106-01.dmp 1/18/2010 8:19:36 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`02caf8e8 fffff880`0351d8e8 fffff880`0351d140 hal.dll hal.dll+7b7f x64 C:\Users\K\Desktop\Minidump\011810-21106-01.dmp 4 15 7600 012510-28548-01.dmp 1/25/2010 8:32:34 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`049d0ff0 fffff880`060ff658 fffff880`060feeb0 dxgmms1.sys dxgmms1.sys+20d4b x64 C:\Users\K\Desktop\Minidump\012510-28548-01.dmp 4 15 7600 012610-31137-01.dmp 1/26/2010 8:45:26 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`01484e5f fffff880`03948a28 fffff880`03948280 iaStor.sys iaStor.sys+30df8 x64 C:\Users\K\Desktop\Minidump\012610-31137-01.dmp 4 15 7600 010510-25864-01.dmp 1/5/2010 8:26:04 PM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 fffff800`02c9218e ntoskrnl.exe ntoskrnl.exe+71f00 x64 C:\Users\K\Desktop\Minidump\010510-25864-01.dmp 4 15 7600 |
My System Specs![]() |
29 Jan 2010 | #3 |
|
Took quite a while but I bring results.
I ran memtest86+ v 4.00 for separate memory sticks for 5 passes each and switched them to different slots. I found why moving the sticks to the 2nd dual channel slots reduced the BSOD frequency. All slots are fine except for the 3rd slot which gave 4000+ errors. Luckily this slot is unused, so this shouldn't be a problem. Lastly, I ran memtest86 for 5 passes with both sticks in and found no errors. I went to the official gigabyte motherboard website to search for an updated Raid Driver. The driver on the website is actually a downgrade from the version I currently have installed. Should I downgrade the driver or should I leave that alone? I have ran a system file check and got these results: Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. |
My System Specs![]() |
. |
|
29 Jan 2010 | #4 |
|
Took quite a while but I bring results.
I ran memtest86+ v 4.00 for separate memory sticks for 5 passes each and switched them to different slots. I found why moving the sticks to the 2nd dual channel slots reduced the BSOD frequency. All slots are fine except for the 3rd slot which gave 4000+ errors. Luckily this slot is unused, so this shouldn't be a problem. Lastly, I ran memtest86 for 5 passes with both sticks in and found no errors. I went to the official gigabyte motherboard website to search for an updated Raid Driver. The driver on the website is actually a downgrade from the version I currently have installed. Should I downgrade the driver or should I leave that alone? I have ran a system file check and got these results: Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. Are you bsod free or did the frequency get better? |
My System Specs![]() |
29 Jan 2010 | #5 |
|
I shall let you know. The BSOD frequency was quite low to begin with. So if it happens again I will post back. Thank you for helping.
|
My System Specs![]() |
29 Jan 2010 | #6 |
|
So while I was away at class this morning from 9 to 11, my computer BSODed. The code was 0x4a. This was when my computer was idle.
Here is the minidump file. |
My System Specs![]() |
30 Jan 2010 | #7 |
|
bump
|
My System Specs![]() |
31 Jan 2010 | #8 |
|
Another BSOD, happened while playing Battlefield Bad Company 2 Beta.
Stop code 0x3D Here is the dmp file. And this was when I was playing another game. i got 0x50 Lol this is terrible.. i just got another one again 0x7e 2/01/2010 Another 0x3b error while idle. |
My System Specs![]() |
01 Feb 2010 | #9 |
|
Been getting multiple BSODs with the following codes. 0x3b 0x7e. My drivers are all up to date. I'm thinking that the problem may lie in my gpu.
How would i go about this problem? Any help would be much appreciated. |
My System Specs![]() |
01 Feb 2010 | #10 |
|
Hi and welcome This crash was probably caused by cdrom.sys. I would update the cd/dvd driver, and run a system File check rype cmd in seacg>right click and run as admin>sfc /scannow. Let us know the resukts Ken Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\020110-20514-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50 Debug session time: Mon Feb 1 14:24:51.158 2010 (GMT-5) System Uptime: 0 days 0:44:05.000 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff88000e92946, fffff880035a1828, fffff880035a1080} Probably caused by : cdrom.sys ( cdrom!RequestSetSentTime+1d ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff88000e92946, The address that the exception occurred at Arg3: fffff880035a1828, Exception Record Address Arg4: fffff880035a1080, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: Wdf01000!imp_WdfObjectGetTypedContextWorker+1e fffff880`00e92946 4c8b5110 mov r10,qword ptr [rcx+10h] EXCEPTION_RECORD: fffff880035a1828 -- (.exr 0xfffff880035a1828) ExceptionAddress: fffff88000e92946 (Wdf01000!imp_WdfObjectGetTypedContextWorker+0x000000000000001e) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880035a1080 -- (.cxr 0xfffff880035a1080) rax=0000000000000000 rbx=fffffa8007885b80 rcx=bdb2acfffeffeef8 rdx=424d530001001100 rsi=0000000000000000 rdi=fffffa8007de0c90 rip=fffff88000e92946 rsp=fffff880035a1a60 rbp=0000057ff8851b18 r8=fffff880031b0188 r9=0000000000000000 r10=fffffa80046eac80 r11=fffff880035a1b00 r12=00000000002d0940 r13=0000000000000001 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210246 Wdf01000!imp_WdfObjectGetTypedContextWorker+0x1e: fffff880`00e92946 4c8b5110 mov r10,qword ptr [rcx+10h] ds:002b:bdb2acff`feffef08=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efc0e0 ffffffffffffffff FOLLOWUP_IP: cdrom!RequestSetSentTime+1d fffff880`031a35d5 48bb2003000080f7ffff mov rbx,0FFFFF78000000320h BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff880031a35d5 to fffff88000e92946 STACK_TEXT: fffff880`035a1a60 fffff880`031a35d5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!imp_WdfObjectGetTypedContextWorker+0x1e fffff880`035a1ab0 fffff880`031bdfd8 : 00000000`00000018 00000000`c00000bb 00000000`00000000 fffff880`033d3180 : cdrom!RequestSetSentTime+0x1d fffff880`035a1ae0 fffff880`031b4dab : fffffa80`07de0c90 0000057f`f8851b18 00000000`00000000 fffff880`04c8b110 : cdrom!RequestSendMcnRequest+0x20 fffff880`035a1b30 fffff880`00e756fb : 00000000`00000000 fffffa80`07753db0 fffffa80`07687b80 fffff800`02e695f8 : cdrom!RequestProcessSerializedIoctl+0x583 fffff880`035a1c10 fffff800`02fbf527 : fffffa80`074d1e20 fffffa80`07753d00 fffffa80`036fd680 fffffa80`036fd680 : Wdf01000!FxWorkItem::WorkItemThunk+0x113 fffff880`035a1c40 fffff800`02cd3161 : fffff800`02e69500 fffff800`02fbf504 fffffa80`036fd680 00000000`00000000 : nt!IopProcessWorkItem+0x23 fffff880`035a1c70 fffff800`02f69166 : 00000000`00000000 fffffa80`036fd680 00000000`00000080 fffffa80`036e6040 : nt!ExpWorkerThread+0x111 fffff880`035a1d00 fffff800`02ca4486 : fffff880`03363180 fffffa80`036fd680 fffff880`0336dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`035a1d40 00000000`00000000 : fffff880`035a2000 fffff880`0359c000 fffff880`035a19b0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: cdrom!RequestSetSentTime+1d FOLLOWUP_NAME: MachineOwner MODULE_NAME: cdrom IMAGE_NAME: cdrom.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11a STACK_COMMAND: .cxr 0xfffff880035a1080 ; kb FAILURE_BUCKET_ID: X64_0x7E_cdrom!RequestSetSentTime+1d BUCKET_ID: X64_0x7E_cdrom!RequestSetSentTime+1d Followup: MachineOwner --------- |
My System Specs![]() |
![]() |
Thread Tools | |
Similar help and support threads | ||||
Thread | Forum | |||
Having problems with multiple BSOD Lately I have been getting some BSOD, first by memory management, then by pool corruption. It's getting incredibly annoying, I don't know what's the reason for it because they started randomly, I uninstalled bluestacks and updated the drivers on my laptop but the bsod only got worse. If I... |
BSOD Help and Support | |||
Multiple BSOD problems. Hey, at random times i get these BSODs Memory Management (most frequent) System Service PFN server list NTFS file system. Im not sure if its the voltage of my ram or the hard drive...and sometimes it causes all my browsers except IE to fail loading a page. ive ran memtest and found no... |
BSOD Help and Support | |||
Multiple BSOD followed by problems booting. Hey guys. I have had amazing results with this site in the past, I am hoping it will happen again. So thanks in advance. I dont know much at the moment, but I'll tell you what I know. Please let me know if there is anything missing. At the moment it is BSODing multiple times a week now. Sometimes... |
BSOD Help and Support | |||
Multiple Bsod Problems Fresh Install Win 7 64 Bit Hello, all i have rencently fitted a new ssd and installed fresh win 7 64 however on two occasions the system has halted and turned off due to a bsod hopefully someone can help The first bsod details are Problem signature: Problem Event Name: BlueScreen |
BSOD Help and Support | |||
Multiple BSOD Problems! Hi! I Recently installed windows 7 onto my harddrive, installed all the necessary drivers/updates but i keep getting different BSOD. I've run through 3 runs of memtest without an error, the bsod's usually happens when im playing World of Warcraft or Counter-Strike and using ventrilo at the same... |
BSOD Help and Support |
Our Sites |
Site Links |
About Us |
Find Us |
Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd All times are GMT -5. The time now is 00:01. |
![]() ![]() ![]() ![]() ![]() |