Random BLue screens

Nightfox · May 30, 2010

hi guys. im hopeing you can help.

i recently got a new pc.

specs:

intel I5 660
Msi p55 GD-65 mainbored
8 gig geil 1333mhz mem
Msi R5770 hawk vga card
onbored sound
HDD: 2X160 gig 2X 1TB 1X250gig
Powersurply: thurmaltake 875watt.
windows 7 64bit ultamate

after i set up the pc and installed windows i go a few blue screens just befor the loggin screen so i replaced mem as i thought this was the issue, now i can get into windows and the blue screens happen randomly. today i used the pc all day and had no issues till a hour ago then i go 2 blue screens.

so far i have updated all the drivers i can think of and have run mem test for 4 hours with no errors. i even scaned my drives for virus and malware and found nothing.

the error i get is:
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

but i havent got a clue what this means

here are my dump files. i hope someone can assist me.

Regards

usasma · May 30, 2010

7 memory dump files - from 25 May to 30 May 2010 (6 days)
6 different STOP error codes, with 4 different causes blamed.

If you are overclocking, please stop and return the system to default values while we're troubleshooting.

Most likely this is a hardware problem - so let's try this:

HD Diagnostic (read the details at the link)

It's called for in response to the first 2 errors - which point at the storage sub-system.

If that passes, then try these free stress tests:

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Click to expand...

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Click to expand...

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

Alpham164.sys Mon Jul 23 03:57:03 [COLOR=Red]2007[/COLOR][COLOR=Red][COLOR=Black] - [/COLOR][/COLOR]Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham164.sys
Alpham264.sys Tue Mar 20 05:51:03 [COLOR=Red]2007[/COLOR][COLOR=Red][COLOR=Black] - [/COLOR][/COLOR]Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham264.sys
ENTECH64.sys Fri Mar 26 07:44:04 [COLOR=Red]2004[/COLOR][COLOR=Red][COLOR=Black] - [/COLOR][/COLOR]PowerStrip support NT kernel-mode driver - http://www.carrona.org/dvrref.html#ENTECH64.sys
Lachesis.sys Fri Aug 17 03:48:44 [COLOR=Red]2007[COLOR=Black] - Razer Lachesis Mouse driver[/COLOR][/COLOR] - http://www.carrona.org/dvrref.html#Lachesis.sys

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 18:16:25.871 2010 (GMT-4)
System Uptime: 0 days 0:21:53.369
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 08:22:00.595 2010 (GMT-4)
System Uptime: 0 days 0:28:54.719
BugCheck A, {1f04c6f6f48, 2, 0, fffff80002cd90ec}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1cc )
BUGCHECK_STR:  0xA
PROCESS_NAME:  Wow.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 07:49:47.840 2010 (GMT-4)
System Uptime: 0 days 2:40:58.339
BugCheck 1000007E, {ffffffffc0000005, fffff880053a00a4, fffff880025bd788, fffff880025bcff0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 26 12:17:31.571 2010 (GMT-4)
System Uptime: 0 days 0:32:18.695
BugCheck 3B, {c0000005, fffff80002f5ebb9, fffff8800a26ca60, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TrustedInstall
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 25 12:50:44.608 2010 (GMT-4)
System Uptime: 0 days 0:02:11.106
BugCheck 1000007E, {ffffffffc0000005, fffff880047d21d8, fffff88004194658, fffff88004193ec0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+6c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 25 11:40:09.013 2010 (GMT-4)
System Uptime: 0 days 0:04:32.137
BugCheck 50, {fffffa0008431050, 0, fffff8800149e118, 7}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+f118 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 25 11:32:39.919 2010 (GMT-4)
System Uptime: 0 days 0:00:13.043
BugCheck 24, {1904fb, fffff8800358c278, fffff8800358bae0, fffff880018d5795}
Probably caused by : Ntfs.sys ( Ntfs!NtfsMapStream+25 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24

Nightfox · May 31, 2010

thanks for the fast reply usasma

on the drivers that need updating i cant seem to find what driver this one is:
ENTECH64.sys Fri Mar 26 07:44:04 2004 - PowerStrip support NT kernel-mode driver - Driver Reference

as to the rest im downloading everything you recommended and gonna run the tests tonight.

i also ran memtest again over night and had 7 passes with no errors, funny though after i restarted and went into windows i got 2 blue screens trying to read your reply.

anyways will post my results from the scans

thanks again for your help

Nightfox · May 31, 2010

hi usasma

i updated the z-bored and the razor mouse drivers.

i used the HDD test you recomended on my C: for now i have unpluged all other HDD as a means to eliminate any issues.

test for HDD all passed.
mem test for 7 hours no errors
ran FurMark for a hour and the temp was stable at 65. but just after a hour my pc blue screened.

attached are the 3 latest bump files. the last one was the furmark Blue screen

i still need to run Prime95.

thanks again for your assistance

Jonathan_King · May 31, 2010

The dmps blame your graphics card and network card adapter drivers.

Code:

[font=lucida console]
BugCheck 1000007E, {ffffffffc0000005, fffff880047e9577, fffff88002c3d8a8, fffff88002c3d110}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitRenderCommand+15b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff88004740bfe, fffff880083f6860, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiAllocateQueuePacket+162 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {50, 2, 0, fffff88001b0a582}
Probably caused by : Rt64win7.sys ( Rt64win7+14c2d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

Please uninstall both drivers completely in Device Manager, reboot, and let Windows automatically install drivers.

usasma · May 31, 2010

Sorry about the Entech driver - I didn't upload the new links to that webpage yet.
Here's the link to the manufacturer of PowerStrip: http://entechtaiwan.com/util/ps.shtm

If you can't figure out what it is, go to C:\Windows\System32\drivers and locate ENTECH64.sys
Then rename it to ENTECH64.BAK and reboot. Also, you can use this free tool to stop it from loading: Autoruns for Windows

**************************
Was FurMark running when the BSOD occurred?

These BSOD's blamed the video sub-system (2) and your networking driver (1)
Beyond that, you're going to have to start removing/replacing parts to see what stops the BSOD's
Here's some suggestions from an older post of mine:
Hardware Troubleshooting Via System Stripdown

The Ideazon drivers are still old, as are the Razer drivers - please uninstall the software and ensure that the drivers aren't loading. Use the default Windows drivers until we've solved this.
Good luck!

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 18:12:25.654 2010 (GMT-4)
System Uptime: 0 days 5:29:24.153
BugCheck 1000007E, {ffffffffc0000005, fffff880047e9577, fffff88002c3d8a8, fffff88002c3d110}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitRenderCommand+15b )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 02:34:29.343 2010 (GMT-4)
System Uptime: 0 days 0:08:02.467
BugCheck D1, {50, 2, 0, fffff88001b0a582}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+14c2d )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 02:25:11.275 2010 (GMT-4)
System Uptime: 0 days 0:15:27.775
BugCheck 3B, {c0000005, fffff88004740bfe, fffff880083f6860, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiAllocateQueuePacket+162 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe

Nightfox · Jun 1, 2010

Was FurMark running when the BSOD occurred?

yip it ran for about a hour then the BSOD occurred.

now for the Fun part i ran prime95 over night and my system crashed

results for prime 95:

[Tue Jun 01 01:07:20 2010]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
[Tue Jun 01 01:13:08 2010]
FATAL ERROR: Rounding was 0.498046875, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Tue Jun 01 01:23:48 2010]
Self-test 10K passed!
[Tue Jun 01 01:39:36 2010]
Self-test 12K passed!

so i guess this ant looking so good. im starting to wonder if i didnt get a faulty main bored or somthing.

included is the bump file for the prime95 test

Nightfox · Jun 1, 2010

thanks for your help so far, i will uninstall the drivers u mentioned and run the windows standard driver.

what im going to try is remove my ATI drivers and use the standard windows drivers then run furmark again.

This is what iv done so far.

unplugged all devices that are not needed till my box becomes more stable.

so now im running:

PSU- thurmaltake 875watt
CPU- intel I5 660
M/b MSI P55 GD65
ram- 8 gig geil mem ( using all 4 mem banks/ ran mem test for 7 hours and all pass)
HDD-2 X 160gig seagate drives running raid 0 ( hdd test on both drives and all pass)
VGA- MSI R5770 hawlk ati card. ( ran 3dmark vantage with no problems/ ran furmark and got a BSOD after a hour temp was 66 C)
CD-rom- samsung dvd writter

that's the system im using at the moment and tests iv done.

so looking at the hardware and the errors im getting, i need to test the CPU/ mainbored / VGA.

now correct me if im wrong:
Prime95 tests CPU stress and i got errors there.

Furmark tests the VGA for stability and it failed after a hour

so that leads me to think that one of the 3 hardware CPU/MB/VGA are faulty..

Im leaning towards a faulty mainbored. because when i got the hardware, after setting everything up the pc would not boot up and i had to swop out mem banks before it booted. Then with the memory i used the bios would not detect the mem correctly on Auto settings. so i manually set it up and it ran ok till the next BSOD.. after the BSOD i checked the bios and noticed the mem had reset back to AUTO and the setting were wrong. also after a BSOD the main bored seems to take forever to detect drives and get back into windows. some times if freezes while detecting devices/ on post screen till i down the PC and reboot.

any other suggestions anyone might have? :cry:

usasma · Jun 1, 2010

Prime95 primarily tests CPU and memory - BUT, it also stresses the other components indirectly.
I'd first suspect your video card. Do you have another one (that's know to be good) that you can try? Maybe borrow one from a friend or another computer?
If not, purchase one from a store that'll let you return it if it's not needed.

Video is the cheapest and easiest thing to test. Testing the CPU/mobo will be time consuming and expensive!

It could be the mobo - but the MSI P55 board that I had was a bit quirky also and it was still good.
Reset the memory voltages. Check to make sure that the CR2032 CMOS battery is still good (unplug the computer overnight, then check the time in the morning - if the battery is bad, the time will be off)

Nightfox · Jun 1, 2010

thanks for the advice.

i had a chat with the owner where i got my PC and he sent me a loan VGA card. its a Nvidia card so gonna have to get rid of all ATI driver before i install it.

gonna run Furmark and Prime95 again and see what happens. if the VGA card fail's then there is a good chance its the Mainbored.

will post reports any any issues here..

Nightfox · Jun 1, 2010

ok so i installed the new VGA card and installed the newest nvidia drivers after removing the ATI drivers

after a hour and a bit i got another BSOD running Furmark.

so with a new VGA card still got the BSOD

here is the log for it, if you could tell me what was the cause this time.

starting to seem like the mainbored may be at fault after all.
Im gonna test furmark again just to make sure.

usasma · Jun 1, 2010

Well, it's not very clear what's to blame on this one. Please run Driver Verfier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 19:14:08.954 2010 (GMT-4)
System Uptime: 0 days 6:18:15.093
BugCheck 3B, {c0000005, fffff80002cdb497, fffff88008cf8060, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe

Nightfox · Jun 2, 2010

thanks usasma

i will try the Driver Verifier and see what happens.

in the mean time after that BSOD i got, i ran fur mark again and it crashed again and it seems the pc BSOD while idle on the windows logging screen.

here are the last 2 bump files.

thanks again for the assistance

usasma · Jun 2, 2010

I hope that these dump files will contain some useful info, but the Driver Verifier dump files are the one's that are most likely to have the info that we need.

One of the dump files blames your Intel storage drivers - so I'd suggest updating them first.
Â Intel(R) Matrix Storage Manager

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 00:11:39.532 2010 (GMT-4)
System Uptime: 0 days 0:26:46.046
BugCheck BE, {fffff880014919e8, 8000000003a67121, fffff88003b47840, b}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+f163 )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun  1 23:43:49.303 2010 (GMT-4)
System Uptime: 0 days 4:28:42.817
BugCheck 1A, {5003, fffff70001080000, ee, f0000000dc}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b86 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  CurseClient.ex

Nightfox · Jun 3, 2010

hi there

i ran verifier like you suggested.
i got about 7 BSOD but the issue i got the PC rebooted so fast i couldn't see what caused the error. then i went a look for mini bump file and none were created.

i changed my settings on the dump file to not auto restart. and managed to see the one error but again no dump file.

the BSOD happened before the login screen and after a few restarts windows wanted to do a repair and i just told it to start windows like normal. With verifier running i ran Furmark for 7 hours no error (using the NVIDIA card), then i ran Prime95 and 5min in got a error on the cores something about rounding down was 0.4 and should be 0.5 but no BSOD. the BSOD happened 3 times when running 3D mark vantage but again no bump files created.

The place i got the pc from is gonna loan me a new mainbored to test and see what happens. same mainbored as i got now. im thinking of formating and reloading windows 7 64bit when i get the new bored and put in my ATI card again and run some test and hopefully it will be stable and work.

thanks again for your help. pitty no bump files to see what caused the BSOD.

Nightfox · Jun 3, 2010

One of the dump files blames your Intel storage drivers - so I'd suggest updating them first.
Â Intel(R) Matrix Storage Manager

I had a look on MSI web site i downloaded all the drivers for this model mainbored and all the bored drivers are the latest out. so i have been using all the newest drivers out. don't seem to find a newer driver then the one i got.

usasma · Jun 3, 2010

The stuff in RED below will make the system stop so you can read the BSOD:

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

usasma · Jun 3, 2010

You must remove the current iaStor.sys file and replace it with a new one (because of the error).
If you don't, it's likely that the error will keep occurring.
The easiest way is to uninstall the current software and then to install the updated software.

To further complicate things, it appears that they've changed the name to Rapid Storage Technology (RST)
The latest version is at this link: Â Intel(R) Rapid Storage Technology
The previous links don't have the most updated version.

Intel version is 9.6.0.1014 dated 23 Mar 2010
MSI version is 9.5.0.1037 dated 08 Jan 2010

Your call...

Nightfox · Jun 3, 2010

usasma said:
The stuff in RED below will make the system stop so you can read the BSOD:

Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that "Automatically restart" is unchecked
Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Click to expand...

i did that that last night.

the error i got was :IRQL_NOT_LESS_OR_EQUAL
but no bump files so wierd that no bumps are formed. box BSOD about 10min ago and also no bump file, error was the same as above.

The Intel(R) Rapid Storage Technology, reading the intel site its for RAID mostly.
Could it be that im running 2 HDD in raid 0 that causing these problems?

usasma · Jun 3, 2010

1 - check in C:\Windows for a file named MEMORY.dmp Let us know if it's there or not.

2 - The drivers are for the controller - it does RAID and it does non-RAID.

Random BLue screens

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Mr. Cranky Pants

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer