• A Great friend to the HardForum with a great kid that he is trying to get a scholorship to continue his schooling. Please give hime a vote! Only 24 hours left! Thanks.
    If you have an VOTE FOR KEENAN!

BSOD OX 0000003B

B

Baer

Limp Gawd
Joined
Aug 7, 2004
Messages
253
I have been having BSOD’s for the last ten days. Up to that time my rig has been totally stable. I did not load new software or add new hardware when this started. I have done all the normal troubleshooting. All drivers are the latest. I have disabled my RAID and done the WD torture test and HD Tune on my drives, they passed. I have flashed the latest BIOS for my Rampage II Ex and reset to non over clocked, nominal settings. I have prime 95’d and had no problem and with the over clocking not being done my temps are in the 50 C range when running prime 95. I still get random BSOD’s, perhaps 2-3 times a day. Most of the error codes are 0X 0000003B although there are a few others sometimes. I have also been often getting IE8 has stopped responding messages and sometimes Outlook has stopped responding messages. I have even resorted to trying a registry cleaner, which found the usual small number of minor issues and fixed them.
Before I reload Windows, all my apps and network settings Etc., I am looking for suggestions. I wonder if it is just a torked Windows 7 or if it still could be hardware. There is always the chance of it being a HDD issue even though the tests all show good. My memory tests all good, perhaps a PSU issue? Unlikely I think? I have checked all cables but not replaced them, they are however not that old and are all good quality. I have cleaned out my already clean case while checking the cables, I have removed all USB devices Argggg, I am having my computer ego butt kicked. Any ideas?
 
[Testing the RAM]
Download Memtest86+ v4.00 or whatever the latest version is, unzip it, burn the ISO file to a CD, and then boot from it, just like you would do with the XP/Vista install CD. Let Memtest+ run for at least three hours on each stick of RAM separately as well as test the RAM all together. Go for a full 24 hours if you want to be completely sure that the RAM is not a problem. If you start seeing errors, than your RAM is defective or you have incorrect settings for the RAM.

[Testing the PSU]
Buy and use a digital multi-meter to monitor the voltages coming from the PSU. Follow the instructions for "Using a multi-meter to check voltages":
http://www.bfgpower.com/troubleshooting.html#DMM
 
Thanks, I have run both the Windows memory test as well as memtest, all checks out OK. All voltages appear in spec on my PSU.
I have also run sfc /scannow and the log file shows that it found some corrupt files and that it was unable to fix some of them. I am also still getting IE8 not responding issues. I am starting to think that a reloas of Windows may be the way to go.
 
Baer said:
Thanks, I have run both the Windows memory test as well as memtest, all checks out OK. All voltages appear in spec on my PSU.
I have also run sfc /scannow and the log file shows that it found some corrupt files and that it was unable to fix some of them. I am also still getting IE8 not responding issues. I am starting to think that a reloas of Windows may be the way to go.
Click to expand...

How long did you run Memtest for?
Did you actually measure your voltages with a DMM?
 
I ran memtest twice, the longest time about two hours. I also ran the Windows memory test numerious times over the last few days.
Yes on the PSU, all voltages are right on using a DMM as well as a digital PSU tester with an artificial load applied.
The only hardware left to suspect is the MOBO and the CPU. The corrupt files that scannow found as well as the lock ups of IE-8 every hour or so make me tend away from suspecting hardware. Still, with all the installs I have done with WIn 7 I have never had an issue with it. On the hardware side, I usually run memory as well as the cpu overclocked, right now, for troubleshooting, I have everything at stock, this makes me suspect the hardware less.
 
The 0x3B stop code suggest a hardware incompatibility. Did you update any drivers recently? If so, try rolling back.

What are the other error codes?

Also, if you can, run memtest overnight. When running prime, were you running SmallFFTs or blend test?
 
THe other error codes are 0X 0000000A, 0X 00000024, 0X 00000003D, and one internal power error 0X 000000AO but most of them are the 3B.
I have been stable all morning however since running the sfc /scannow, it showed some errors that it could not fix but it did fix a few errors.
I ran memtest all night, no errors. Prime 95 I run a blend.
I also have been getting IE-8 and some Outlook not responding, have to restart errrors but not today so far.
I only updated the keyboard driver and then after this started I updated the NV driver to the one that just came out but the BSOD's started before I did that. Also, after the BSOD's started I flashed the latest BIOS for my RE-II MOBO and I am running at stock speeds, no OC for now untill I get a handle on this. but I was still getting BSOD's.
I am really thinking that I have some corrupted Windows files and if I get anothor BSOD I will probibally rebuild. Perhaps put in a SSD for boot since I will have to reload everything anyway.
 
http://www.aumha.org/a/stop.php
0x000000A0: INTERNAL_POWER_ERROR
0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED

0x00000024: NTFS_FILE_SYSTEM
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
Click to expand...
Still sounds like either a driver/hw incompatibility or power issue. The board may be having issues delivering power to the cpu/chipset. I'd try a clean install first, and if the problem persists, test with another PSU, despite your DMM readings. If it still exists, try another mobo.
 
Thanks,
The dmp file shows that SRTSP64.sys may be at fault, that is Norton Antivirus. This is interesting for a few reasons, first of all, I have been running Norton 2010 on this rig since the RTM of Win 7 last Summer, mainly because it was the only one ready for the 64 bit ver of the Win 7 RTM at the time. I had no issues.
My BSOD's started about a week or so ago. Yesterday my NAV sent me a message that it was out of date, strange as it is set to auto update and it had been doing so normally. In order to get it to update I had to do it manually, telling it to update now. It downloaded about a weeks worth. I also had to reset many of my settings in NAV so it obviously hiccuped. Since I have done that I have not had a BSOD so coincidence? Perhaps or perhaps it was the problem. I have been running normally all day with multi Apps open across both screens, stable so far. I am going to contact Symantic to see if they have been having any such issues that they will admit to.

I have also ordered an SSD :) just because if I have to reload I may as well upgrade. I will post back here new developments.
 
Heh, I'd ditch norton. :p There are much better options out there for less money (in fact, some are free, lol).
 
Money is not the issue, time is and being down takes me away from clients, not good. I only went to Norton as it was the only good choice for Win 7 64 a year ago. I tried AVG free and it had big issues with Win 7 64 then. But, it is starting to look like that was the issue and there are many more choices out there now.
I am going to build aWin 7 install on an SSD and keep my two Raptors untouched so I can swap back and forth. I will not put Norton on the SSD, prob. MS Security Esentials.
 
I think MSSE, despite being beta, was a better choice a year ago than norton, hehe.
 
You must log in or register to reply here.
Back
Top