• BSOD's everywhere, need help
    17 replies, posted
Okay, ever since i've gotten my computer around 2013, i've had bluescreens, but recently they've become really bad. Usually going on for 10 mins without a bluescreen, and around a hour in safemode. I've looked around, saying to boost my RAM and CPU voltage, Should I?
[url]http://www.nirsoft.net/utils/blue_screen_view.html[/url] Download, run, copy-paste the error (looks like things like DRIVER_IRQ_LESS_THAN_OR_EQUALS, also include the 0x030434b whatever STOP code) from the top of the list, which is the most recent BSOD.
Downloading it,but the errors are DRIVER_IRQ_LESS_THAN_OR_EQUALS, MEMORY_MANAGEMENT, PAGE_FAULT_IN_NON_PAGED_SOURCE or something along those lines. [editline]14th November 2014[/editline] I've also bumped up the voltage, seems to be running smoothly. oh ffs my father deleted all my dumps "because they take up too much space and are slowing your computer down, they also dont do anything" yesterday. So now we play the waiting game.
The first and last of those three errors is more or less bad drivers making Windows shit the bed unexpectedly. This is not limited to your video drivers, but can include sound drivers and keyboard/mouse/etc. I'd start updating them, one by one, starting with video and sound, and see if that helps.
Right. Going to update now.
page fault in nonpaged area is almost always RAM. Run memtest86+ to be sure. [url]http://www.memtest.org/[/url] bad RAM could also be corrupting the drivers and other bits while they in the memory causing those other BSOD's.
Update time. I'm still getting the crashes, even though i've updated my driver. Heres an whocrashed log if you're intrested. [QUOTE] On Mon 11/24/2014 6:28:54 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-19219-01.dmp This was probably caused by the following module: dxgmms1.sys (0xFFFFF880103BDEB0) Bugcheck code: 0x50 (0xFFFFF9A00462FF50, 0x0, 0xFFFFF880103BDEB0, 0x5) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. On Mon 11/24/2014 6:28:54 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x125F0) Bugcheck code: 0x50 (0xFFFFF9A00462FF50, 0x0, 0xFFFFF880103BDEB0, 0x5) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\dxgmms1.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics MMS Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. On Mon 11/24/2014 12:27:02 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-19141-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41201, 0xFFFFF680003B8FE0, 0xF300100A35B3005, 0xFFFFFA800380F410) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 11/24/2014 12:22:32 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-18486-01.dmp This was probably caused by the following module: ndis.sys (ndis+0x63110) Bugcheck code: 0xCF (0xFFFFF900046DF239, 0x8, 0xFFFFF900046DF239, 0x7) Error: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE file path: C:\Windows\system32\drivers\ndis.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NDIS 6.20 driver Bug check description: This indicates that a driver has been incorrectly ported to the terminal server. 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. On Mon 11/24/2014 11:46:19 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-16692-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x50 (0xFFFFFA83019622EB, 0x0, 0xFFFFF8000473545F, 0x5) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 11/24/2014 11:39:33 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-18252-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x5002, 0xFFFFF780C0000000, 0x4685, 0x57BDFFFFFFFE) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 11/24/2014 11:07:17 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-20264-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x80C, 0xFFFFF6FB7DA0F009) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 11/24/2014 10:58:20 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-20248-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xD1 (0xFFFFE50004684A8A, 0x2, 0x8, 0xFFFFE50004684A8A) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 11/24/2014 10:53:13 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-21418-01.dmp This was probably caused by the following module: fltmgr.sys (fltmgr+0x51D1) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880012051D1, 0x0, 0x80000000020) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\fltmgr.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Microsoft Filesystem Filter Manager Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. On Mon 11/24/2014 10:08:37 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\112414-16192-01.dmp This was probably caused by the following module: ntfs.sys (0xFFFFF880016E9506) Bugcheck code: 0x50 (0xFFFFFCA01BAA0B98, 0x1, 0xFFFFF880016E9506, 0x7) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates that invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. [/QUOTE]
Let Memtest86 run tomorrow night and see what it comes up with. I think it's one of the RAM modules being faulty You also shouldn't be fiddling with your voltages unless you've over/underclocked something
Okay. Did memtest after hoping it didnt fuck up like my dads computer did. let it run overnight.. Um.. 816 errors over the course of 11 hours? How fucked am i out of ten?
Well, good. Now we know for sure what the problem is. Do you have more than one stick of RAM? If so, test them individually, to find the faulty one. If you're lucky, it may still be covered by warranty, and thus you can just RMA it. You should've begun troubleshooting the moment you experienced a bluescreen the first time.
[QUOTE=Rixxz2;46571948]Well, good. Now we know for sure what the problem is. Do you have more than one stick of RAM? If so, test them individually, to find the faulty one. If you're lucky, it may still be covered by warranty, and thus you can just RMA it. You should've begun troubleshooting the moment you experienced a bluescreen the first time.[/QUOTE] One stick, and i doubt it still under warrenty. It's been a year or so. And I have, never knew memtest existed. I allways thought the problem was with the HDD, and it only happened ever so often. [editline]25th November 2014[/editline] Or not, RAMS got lifetime warrenty :dance:
Right, Uh, I can't find a reciept or anything for the warrenty, so i guess I'm screwed, unless theirs any other way to vertify I brought it.
Did they ask for a receipt when you tried to initiate the RMA? You may not even need it if not, because about 75% of the time for my RAM RMA's I haven't needed any proof of purchase.
Hm. Jiggled the RAM around a bit, cleaned out some stuff with a q-tip.. And odly enough, Now It's working! Like, I've taken it out and done this so many times, but for some reason it's working. Played an entire 2 hours of ME2 without crashes. [SP] still buying another stick because 4gig is shite [/sp] But, I'll check on it with memtest tommrow to see if i encounter any bugs. [editline]30th November 2014[/editline] And, of course as soon as i go to turn it off i get a blue screen.
Okay. Did memtest again for the same ammount of hours almost 2 errors, same place. Does that still mean i'm fucked? I mean, its a step down from [B]817 ERRORS.[/B] But, is there a way to disable that little bit of memory?
No way to disable it. If you take it out and look at the contact pins, do any look corroded or oxidized at all? If so, take a pencil eraser and lightly rub it over the contact pins to clean it off.
[QUOTE=Levelog;46611903]No way to disable it. If you take it out and look at the contact pins, do any look corroded or oxidized at all? If so, take a pencil eraser and lightly rub it over the contact pins to clean it off.[/QUOTE] You can't explicitly disable specific memory addresses, but you can mask off all memory starting before that address and onwards by telling the OS not to use it. Like if you have a 512 MB memory stick and it has a bad region at 496.11 MB, you can tell the OS to not use more than 495 MB and anything above that is ignored. Though this really only works if the bad region in memory is towards the upper limit of the memory map in the memory stick. If you have a stick that has bad regions near the beginning of the memory map on the stick, doing this is pretty much worthless. I've had to do this on a few occasions in situations where getting replacement memory is too cost prohibitive (ie. weird non-standard memory or ECC/Registered/Buffered memory which is far more expensive.) Or in a more strange situation of a bad memory controller. I have a Dell PowerEdge 2550 that has a problem with the memory controller in that the last 2 KB of memory is always bad. It doesn't matter how much memory is installed in the machine, the last 2 KB will always not work properly. Windows 2003 Server doesn't seem to bat an eye to this problem, but Linux absolutely flips out and kernel panics when you try to install pretty much any distro. I figured out that if I mask off the last 1 MB of memory that Linux will run fine and I haven't had issues sense. I could replace the motherboard but that costs time and money which this small software based fix does for free.
[QUOTE=Levelog;46611903]No way to disable it. If you take it out and look at the contact pins, do any look corroded or oxidized at all? If so, take a pencil eraser and lightly rub it over the contact pins to clean it off.[/QUOTE] Nope. Didn't work
Sorry, you need to Log In to post a reply to this thread.