Blue Screen of Death

[xps9000]

Update 1-20-2010, 6:45PM

I just wanted to let everyone know, I did narrow down the problem, and it was a software conflict with a program called Media-monkey, which if you are not familiar with, is a music player.

I wanted to thank everyone for their help.


Hello,

Generally, I would do the research myself, but, my time is cramped being a University Student at this moment. So, my question is, could you guys please help me work out this stupid BSOD error. I switched back from Debian to Windows when I started up College.

Generally, I get very random BSOD's, but, I've noticed a pattern, when I plug my USB Dongle in, and use Truecrypt to decrypt the data, I'll get the blue screen a couple minutes afterwords, also, after unplugging the dongle, I'll get a BSOD, even after I go through MSFT's "Safely remove Hardware" procedural crap.

But, I have noticed, the BSOD will occur even without the Dongle, but, they are so random, sometimes, it won't happen for a day, othertimes, it'll happen three or four times in a day.

Thanks for your help.


*Note, this is an Intel Core i7 Mobile machine*

Here is some system information, as well as a Blue Screen View txt

SYS Info
OS Name   Microsoft Windows 7 Home Premium
Version   6.1.7600 Build 7600
Other OS Description    Not Available
OS Manufacturer   Microsoft Corporation
System Name   DSMIV4-PC
System Manufacturer   Dell Inc.
System Model   Studio 1557
System Type   x64-based PC
Processor   Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz, 1597 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date   Dell Inc. A03, 12/4/2009
SMBIOS Version   2.6
Windows Directory   C:\Windows
System Directory   C:\Windows\system32
Boot Device   \Device\HarddiskVolume1
Locale   United States
Hardware Abstraction Layer   Version = "6.1.7600.16385"
User Name   DSMIV4-PC\DSMIV4
Time Zone   Central Standard Time
Installed Physical Memory (RAM)   4.00 GB
Total Physical Memory   3.99 GB
Available Physical Memory   2.25 GB
Total Virtual Memory   7.98 GB
Available Virtual Memory   5.91 GB
Page File Space   3.99 GB
Page File   C:\pagefile.sys


BLUESCREENVIEW:
==================================================
Dump File         : 011910-14710-01.dmp
Crash Time        : 1/19/2010 5:57:54 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`02a44798
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Computer Name     :
Full Path         : C:\Windows\minidump\011910-14710-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 011910-15054-01.dmp
Crash Time        : 1/19/2010 5:44:03 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`02a52798
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Computer Name     :
Full Path         : C:\Windows\minidump\011910-15054-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 011910-15350-01.dmp
Crash Time        : 1/19/2010 5:36:11 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`02a3f798
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Computer Name     :
Full Path         : C:\Windows\minidump\011910-15350-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 011910-15038-01.dmp
Crash Time        : 1/19/2010 5:20:48 PM
Bug Check String  : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code    : 0x0000007f
Parameter 1       : 00000000`00000008
Parameter 2       : 00000000`80050031
Parameter 3       : 00000000`000006f8
Parameter 4       : fffff800`02a8d798
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Computer Name     :
Full Path         : C:\Windows\minidump\011910-15038-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7600
==================================================
 


UPDATE:
I have confirmed it is not the RAM, after 9 hours of testing, and 12 passes, zero errors were reported. I believe the duration of the scan was long enough to suffice.

[Broni]

I'd try to check RAM....

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[xps9000]

I don't believe it is the RAM, as I did not have memory issues in Debian. And Linux is pretty *censored* about checking everything.

I've ran Memtest for several hours before replying, and it didn't detect anything. In addition, I run memory/CPU intense programs, IE, why I have a quad core laptop, and I've never had this problem. Truth is, the problem only occurred when Faildows was installed on the machine. Not to mention, it's less than two months old. Which......RAM has hardly failed me in the past, not saying, it's not possible, but, highly unlikely.

I believe the issue lies more with some driver conflict causing Windows to go haywired.

As I said before, I can go a day, week, two weeks, without a BSOD, Memory issues just don't do that, in my experience. RAM is either bad or it's not. Benchmarking does not cause the machine to BSOD either, which would in the event memory were an issue.

I'm debating on just windows repairing, or reinstalling.......Or just going back to Debian. I haven't really decided yet, I prefer windows at the University, it makes life a bit simpler, but, it wouldn't be a real imposition just to use VMware, or some other Virtualbox program.

Any more ideas? I'm going to bed now. So, I look forward to more replies in the morning.


Thanks again for all the help


I also wanted to add, I have no performance problems what so ever, everything runs fine. Except.....well, something obviously isn't fine.

**I will run MemTest through the night again to see if it picks up anything, but like I said. I generally try all obvious options before I seek help**

[Broni]

I can go a day, week, two weeks, without a BSOD, Memory issues just don't do that

I must disagree on this, not to say, I'm insisting, it's a RAM problem.
However, when it comes to random time errors, I'd rather suspect RAM, than a driver. Bad driver would give you BSOD every time it's involved in some certain action.
memtest is a software test and thus it's not 100% reliable. If you want real test, go with option A.

[BC_Programmer]

what BSOD codes are we talking about, anyway? And does the BSOD say what file?

even after I go through MSFT's "Safely remove Hardware" procedural crap.

you mean two clicks? left click the icon, and then click the item to remove.

a lot of people have it ingrained that system tray icons need to be right-clicked, for some reason. I was surprised when I found the left click "quick" menu.

[Allan]

It would take you less time to look up the blue screen error yourself than it's taking you to post your problem on this forum.

[xps9000]

It would take you less time to look up the blue screen error yourself than it's taking you to post your problem on this forum.

Alright, then, I'll just find time between reports and figure out what was going on. But, I felt that the problem could be better addressed in the future, if there were a post about it.

Sharing information is critical in any environment.

Thanks for your post, Allan.