I see your bluescreen display and raise you one. Apparently a Saab driving simulator at the Javits Center Auto Show 2008 had a problem with an NVidia display driver.
![]()
08 was a bad year for nvidia drivers
As usual, the blue screen in the OP is caused by a device driver. If I read correctly, the driver that caused this BSOD is pd1usb.sys, a 3rd party driver supplied by Adata.
Device drivers are almost always the weakest link in the chain, and account for the overwhelming majority of bugchecks. Hardware vendors just don't like to spend the money for quality kernel mode driver developers, it is a "cost" that effects profitability along with testing of the driver.
My point is that especially these days, bugchecks (aka BSOD) are not usually the fault of Microsoft code itself. If a driver has a null pointer or does not free its memory, that is on them. Of course it could be argued that Windows handles these faults better. Microsoft has done a ton of work to alleviate this providing class drivers and user mode driver frameworks.
My question is why isn't the Adata USB device using a proprietary driver and not the class driver? A quick googling of pd1usb.sys shows it is for a usb thumb drive.
The fault in the pic is DRIVER_IRQL_NOT_LESS_OR_EQUAL, which is caused by a bad driver 99% of the time.
Windows stop DRIVER_IRQL_NOT_LESS_OR_EQUAL error.
Cause
This error is generated when a driver or part of Windows attempts to access pageable memory using the IRQL kernel process that is invalid.
Bad hardware drivers.
Bad memory or mismatched memory.
Corrupt or bad Virtual Memory page file.
It's funny to sometimes see BSODs on random displays around town.
I saw BSOD on a candy vending machine display. My girlfriend was thought I was stupid for stopping to take a picture. My geek friends though it was awesome.
i850/Williamette had a true analog RNG as did all Intel platforms in the last decade.I wonder what the lottery machines use as their source of random numbers:
A pseudorandom algorithm, or the more expensive solution of genuinely random numbers from the proper hardware?
Side note: It's annoying to get stuck behind someone who spends so much time reading off a list of special or "significant" numbers to be played.
Take the machine's numbers, or just use the same numbers every week, it won't affect the outcome anyway.
Though here's a thought: Wait until the machine blue-screens, then use the memory address as your lottery numbers. :hmm:
How good is it? I've seen things out there like this that can command well over $1000.i850/Williamette had a true analog RNG as did all Intel platforms in the last decade.
Address ranges will have a lot of the same numbers.
I don't play - this particular store is a small convenience store. It has only one line to wait in to pay for anything, whether it be a 2L of soda or a lottery ticket.Funny that you would admit to playing a skill-less game with losing odds while insulting other players' intelligence.![]()
I saw a BSOD at the airport boarding dock once. I was nervous getting on the flight.
